Revision as of 11:59, 18 July 2024 edit Naveenhs14 (talk \| contribs) 4 edits Added point to regression testing Tags: Reverted Visual edit ← Previous edit		Revision as of 12:06, 18 July 2024 edit undo Alexeyevitch (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 37,921 edits rv, unsourced Tag: Undo Next 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 ===

Software testing: Difference between revisions