Testing and Evaluating Software Solutions Reporting on the Testing Process

Why Report? Documentation and communication of the testing process and its results are vital to any testing program Results of testing need to be evaluated so that problems can be corrected For this to work it requires documentation of the testing process and communication of the results to the development team and to users

CASE Tools Computer-aided Software Engineering tools are used to develop software that is high-quality, defect-free, and maintainable Examples of CASE tools: WinRunner – tests user interface-based applications function as expected LoadRunner – volume (load) testing tool that simulates thousand of users using an application simulataneously DataTech – generates test data records in large quantities with flexible methods of reporting results UsableNet – websites that tests the usability of other websites and formulates a report

Documentation of Testing Test requirements – what needs to be tested? Test plan – how do we implement these tests? Test data and expected results - what are the necessary test inputs and the expected outputs? Test results – do the actual results match the expected results? Recommendations – what needs to be done now?

Communication of Test Results Test results will include problems from all aspects of the system tests. UI inconsistencies, bugs in the code etc. The language used to report the test results back to the users needs to be non-technical Reporting to the client should address any objectives or design specifications that have not been adequately fulfilled

Readings and Activities Read pages of the textbook Begin Part A of the Assessment Task