When a software tester is assigned the task to sequentially perform some tests on a particular build, he must follow the step-by-step testing technique specified in the test case, and record the test results. Almost any test case document has a special place wherein the tester records the results of each step, as well as the outcome of the test (passed, failed). In addition, there is also a place for the identifier given to a defect which is detected during the tests. One way to log the results of a test run is to use a test case template.
Another way consists in using the test log which is shown in the below table. This test log is useful for consolidating the results of all tests that one testing specialist performs on a single software build. It also has a place for registering the overall result in the test such as “passed / failed / was not run”, and also for the identifier assigned to any defect detected during the test run. There is also a place for comments – usually this document logs information that can later be useful in reproducing the problem or for understanding the conditions in which the problem was observed.
Outsourcing testing to Ukraine means only one thing – the cost effective possibility to ensure the best quality of developed software products.
Regardless of which method will be used to record test results, it is very important that the result of each test be registered and stored in a secure archive. Archived test results may later be needed for various reasons: confirm that intended tests have been executed, enable support to reproduce problems, or chronological records that justify the effort required to develop a software product.
The templates for lists of tests run on a single software build, test cases and test logs can be given in the form of text documents; nevertheless, they can be implemented as part of a Web-based data entry system or test management tools. Using automated tools to save test cases, run tests and generate test reports can significantly contribute to developing an effective system testing strategy.