Reporting on the testing process
documentation of the test data and output produced and the use of CASE tools
A test specification or plan is often created before testing. Testers can then follow these steps to ensure all aspects have been well tested and documented:
define procedures
plan procedures
implement tests
report tests
review procedures
Rather than randomly selecting values to test, a test data table should be created to show the test data, the result, and the reason for testing it.
A desk check table is used to document used test data, actual results from using it, and the expected results for comparison.
The use of CASE tools in testing and test documentation such as:
test data generators
data dictionary creators
source code analysers
simulators to mimic the roles of hardware or software that interact with the program
test management software that provide a framework for testing and to track results
communication with those for whom the solution has been developed, including:
The testing process should never be carried out in isolation. Independent testers are less likely to approach the program with preconceptions, helping them test things that may not normally be tested.
The software solution has been developed to meet the needs of a user; it is therefore essential to provide them with the opportunity to evaluate the solution.
Test results should be summarised for the user, enabling them to evaluate and discuss the functionality of the new system. If it does not meet the expected results, it may need to be redesigned. Test result should detail positive and negative results, such as:
problems identified during testing
limitations
useful properties
A comparison with the original design specifications should address which parts meet original design specifications, and which do not. For the latter, the client should be advised why certain criteria have not been met. Alpha and beta testing (collectively called acceptance testing), allows the users to use the program and provide feedback, and hopefully approve it once testing concludes.