Detailed testing techniques can be developed on the basis of test projects. The level of detail for the testing techniques in writing depends on the qualifications and knowledge of people who perform the test run. Do you plan to run the system testing of a software program together with the actors who are little familiar with this product? If this is the case, then they must undergo certain training, and the testing methodology must be clearly formulated so that they can perform the testing correctly. In the case where the testers have detailed knowledge of the software product, the test procedure may be less detailed. It is extremely important for the participants to take decision as to what the level of detail of the testing technique development process should be, since it may turn out that you will waste time describing unnecessary details for the skilled user. On the other hand, it is in vain to spend time teaching untrained testers to conduct tests if the procedure is not clarified in as much detail as possible. Anyway, it is desirable to find a reasonable compromise.
Professionals of performance testing company would like to know if you are satisfied with behavior of your app otherwise they can optimize it.
One special case deserves special consideration. If the test can be automated, it is advisable to allocate time for the preliminary development of a detailed testing methodology, with the help of which an automation engineer can unambiguously formulate the automation task to be solved. The vague testing technique is likely to lead to developing inaccurate or ineffective automated tests. The recommended level of detail in the testing methodology will be clarified after further discussion of the expected results.
There is a wide range of technologies that can be used to test software products. For example, there is a popular black box test design method. Black box testing involves examining the product at the system level, and deals only with “external” aspects of the program. Black box testing does not require any knowledge of the internal functioning of the software product and is carried out using only external interfaces, such as user interfaces or APIs (Application Programming Interface).
The two widely used black box testing technologies are equivalence classes partitioning and boundary value analysis.