help me learn.
Step 1: Perform an Initial System Test
Run the software system you created last week. Follow the testing procedures that you described in your test plan. As you work through each one, document the results in a test incident report. Do not attempt to correct the defects at this point. You will do that next. For now, just report what you find.
The following is a highly generalized template for test reporting derived from IEEE Standard 829. Complete at least one test report for every test case. If a test uncovered more than one defect, complete a report for every individual defect that you discover. Put them all into a single document—a Test Report Summary.
Test Report Template
- Test Report ID: A unique identifier for this report
- Test Case ID: The ID of the test case with which this report is associated
- Summary: Summarize the results of the test.
- Assessment: Explain whether the test passed or failed and what factors led to that decision.
- Incident Description: If the test revealed any possible defects, provide a full explanation of the defect, including the following.
- Expected results
- Actual results
- Any unexpected anomalies that may have happened during the test
- Which step of the test case procedure revealed the defect
- Any other information that you feel is important to understanding or correcting the defect
- Impact: If a defect was discovered, describe the damage caused by the defect. This is usually communicated with two pieces of information.
- Severity: How much impact will this defect have on the system?
- Priority: Does this defect need to be corrected immediately, can it wait, or could it possibly just be left in the system?
When you have finished executing all of the test cases, save your test report summary document. To keep this version separate from the next one you will create, make sure the file name contains the words test report and initial.
Step 2: Correct Defects
Using the test reports you created in Step 1, apply your programming and debugging skills to correct the defects that you discovered in the program.
Step 3: Repeat the Testing Procedures
First, make a copy of your initial test report file and rename it by replacing the word initial with the word updated.
Now that you have attempted to correct the defects, repeat the tests again. Be sure to repeat all of the tests, not just the ones that failed. It is extremely important to make sure that the code you changed to fix one problem does not cause other problems.
Retesting the entire system after a change has been made is called regression testing. The more complex a software system is, the more likely it is that a change may have unexpected side effects on things that seem unrelated. Regression testing helps to make sure everything continues to work even after changes have been made.
If any defects are encountered, document them in your updated test report document.
Step 4: Update Project Documents
Make whatever updates are necessary to the project plan, business problem scenario, or test plan.
Step 5: Submit Deliverables
Create a zipped archive containing the following files.
- Initial test report
- Updated source code
- Updated test report
- Updated project documents as needed
- Individual team member cumulative time sheet