Regression Test
The objective of this assignment is to give you experience running regression tests.
After your development team has fixed the bugs reported during System Test, two important questions need to be answered:
1) Did they actually fix the bugs?
2) Did they introduce new bugs while fixing the old ones?
The purpose of regression testing is to answer these questions.
Obtain a current copy of your development team’s FCS implementation and install it. After doing so, re-execute your system test plan to verify their bug fixes and check for new bugs.
To verify the bug fixes, you should rerun the test cases from your System Test Plan that originally uncovered the bugs. Theoretically, these test cases should now succeed, but you should run the tests again to make sure. If the bug has been fixed, change the bug’s status to “Closed” in the bug tracking system. If the bug has not been fixed, change the bug’s status to “Reopened” and provide comments explaining why the bug has been reopened.
The second part is to verify that features that used to work are still working (i.e., to look for new bugs that were introduced by the bug fixes). Rerun all of the tests in your plan that used to work to ensure that they still work. For new bugs that you discover, enter reports into the bug tracking system.
Document your test results in a Regression Test Report. This should be similar to the System Test Report.
One hard copy of your Regression Test Report
Updated reports in the bug tracking system for all old bugs that should have been fixed
New reports in the bug tracking system for all new bugs that were discovered
Were sufficient tests run to verify bug fixes and check for new bugs?
Were the results properly documented in a Regression Test Report?
Were bug reports updated and created appropriately?