Content deleted Content added
Citation bot (talk | contribs) Altered pages. Add: isbn, volume, series, doi. Removed parameters. Formatted dashes. Upgrade ISBN10 to 13. | Use this bot. Report bugs. | Suggested by Abductive | #UCB_webform 1459/3850 |
Naveenhs14 (talk | contribs) Added point to regression testing Tags: Reverted Visual edit |
||
Line 178:
Common methods of regression testing include re-running previous sets of test cases and checking whether previously fixed faults have re-emerged. The depth of testing depends on the phase in the release process and the [[risk management|risk]] of the added features. They can either be complete, for changes added late in the release or deemed to be risky, or be very shallow, consisting of positive tests on each feature, if the changes are early in the release or deemed to be of low risk.
Regression test cases will usually be [[Test automation|automated]] using various Automation Tools. This helps testing team to quickly run the automated test cases before production deployment of the code, to ensure business functionality works as intended.
=== Acceptance testing ===
| |||