Confirmation testing is a type of software testing that allows testers to retest a software product to make sure the previously posted bugs are fixed or not in the system.
Usually, testers report a bug when a test fails. Dev Team releases a new version of the software after the defect is fixed. Now the testing team will retest to make sure the reported bug is actually fixed or not. This is known as confirmation testing.
Confirmation testing is also known as re-testing.
Check our detailed guide on re-testing
While retesting, testers need to follow the defect report which was created while posting the bug to reproduce it.
The defect report helps the tester to execute the test by following the same test steps, test data, and run in the same test environment as they executed earlier.
Is Confirmation Testing or Retesting the Same?
Yes, confirmation testing is also known as retesting.
Whenever the dev team did some changes in the build to fix a defect then confirmation testing or retesting is done.
It is done repeatedly on every new agile sprint.
It is performed to make sure the test cases which were failed in the earlier build and defects reported are getting passed in the new build or not.
Testers execute the same test cases (which were failed in the old build) to validate the previously reported bugs that have been remediated in the new build. It makes sure the defects reported earlier have been successfully fixed or not. If those issues are fixed then testers mark those bugs as fixed in the Bug Tracking System.
Is confirmation testing and regression testing the same?
No, confirmation testing and regression testing are not the same.
Check our detailed guide on Regression Testing.
Both confirmation testing and regression testing techniques are performed during the Software Development Life Cycle SDLC but these two are completely different.
Don’t get confused retesting with regression testing.
Regression testing and retesting both are different. Check our detailed guide on the difference between confirmation testing and regression testing here.
When do we perform Confirmation Testing?
Confirmation testing is performed during the Software Testing Life Cycle STLC in the following conditions.
- Whenever the dev team release a build that contains bug fixes
- Before executing the regression testing to verify the bug fix
- Whenever the dev team rejected a bug reported by a tester. Testers do confirmation testing to reproduce the bug.
What are the features of Confirmation Software Testing?
- It is performed to make sure whether the bug is fixed.
- There is no need to create new test cases for confirmation testing. We do execute the same test cases (test cases we executed when we found the bug) to ensure the bug is fixed.
- It can be performed before regression testing.
- What is Regression Testing and when do we do regression testing
- What is Retesting and when do we do retesting
- Defect Triage Process In Software Testing
- What is Defect, Bug, Error, and Failure in Software Testing
- Unit Testing Guide
- Integration Testing Guide
- System Testing
- Acceptance Testing
- Functional Testing Guide
- Non-functional Testing Guide