Testing to Inform Evaluation

• “Testing to Inform Evaluation” primarily refers to the process where specific features and functionality of a programme are verified to ensure they work as intended.

• These tests should assess both the individual components (unit testing) and overall system or programme (integration testing).

• With systematic testing, problematic areas can be identified, pinpointed, and rectified, facilitating an appropriate evaluation of the software or programme.

• Black-box testing involves testing the functionality without any knowledge of internal workings. In contrast, white-box testing carries out tests based on knowledge of the internal logic of an entity’s code.

• Exploratory testing, also known as ad-hoc testing, involves concurrent test design and test execution against an application. This aids in identifying unique bugs not captured in scripted testing.

• It’s crucial to document all tests carried out thoroughly since this documentation will form a vital part of the final evaluation.

• The evaluation should be informed by the performance of the software during these tests.

• Evaluation will entail examining how well the software meets the required specifications and the extent to which it fulfils the user’s requirements.

• It’s essential to consider the robustness of the programme in the face of unexpected inputs or conditions (also known as edge cases).

• Usability of the programme, such as the design of the user interface and the user experience, should be evaluated from the tests.

• Response time, output quality, and memory usage - all these elements should be evaluated during the testing phase.

• Lastly, testing aids in pulling together recommendations for future improvements, which is a critical part of evaluation. Insights gathered during testing can provide an understanding of what could be enhanced in the next iterations.