You are here: Development Standards > Quality Assurance > Design Phase > Test Evaluation

# Test Evaluation

While you enter data and print reports for a test or checklist, watch the screen for errors or problems, appearance, functional consistencies and user-friendliness. Make sure that the software is working according to its specification and the standards in this document.

As you execute tests, you will print reports and screens. Check the printouts carefully for errors. To retain the integrity of the testing, check the printouts in the order of the test steps, usually from an input worksheet to a print screen (of data entry) to a report and from one or more reports to another. Always check from the correct documents; for example, always check a report or print screen with a report or print screen that you have already traced for accuracy.

Every time you execute a step in the test plan, mark it as completed. You can use a special mark in the test plan and on the accommodating printouts if necessary. This helps you keep the test results organized.

As you encounter problems, try to duplicate the problem before completing a QATR form. When filling out the QATR form, provide as much information as necessary to re-create it. Attach copies of test printouts to QATRs if you are using a handwritten form, or mark the QATR number on the test output when applicable to illustrate or document problems for the programmer. No error or problem is too small to report.