CTFL 2.2.3: Distinguish confirmation testing from regression testing
K2Syllabus section 2.2.3
3 original PrepBench practice questions for learning objective 2.2.3 of the CTFL 4.0 syllabus. Try the examples below and check each answer against its syllabus reference.
Practice questions
Question 1
During development, before the system's first release, a defect in the discount calculation is fixed. The tester re-runs the test that originally failed, and then runs tests around related pricing features. Which statement is correct?
- Both activities are confirmation testing
- The first activity is regression testing, the second is confirmation testing
- The first activity is confirmation testing, the second is regression testing
- Both activities are maintenance testing
Show answer
- Both activities are confirmation testingOnly the first re-run is confirmation; testing related features is regression testing.
- The first activity is regression testing, the second is confirmation testingThe roles are reversed: re-running the failing test is confirmation, not regression.
- Correct answer: The first activity is confirmation testing, the second is regression testingRe-running the originally failing test is confirmation; checking related areas is regression.
- Both activities are maintenance testingThe system is not yet operational, so this is not maintenance testing; maintenance can otherwise include confirmation and regression testing.
Confirmation testing re-runs the originally failing test to confirm the defect is fixed. Regression testing checks that the change did not introduce unwanted side effects in related or unchanged areas.
Syllabus section 2.2.3
Question 2
A defect in the discount calculation has been fixed. The team then runs these tests: Test 1: The test that previously failed because of the discount defect. Test 2: A new test written to cover the change that was made in order to fix it. Test 3: The existing checkout tests for the unchanged order flow. Test 4: The existing invoice tests of a connected billing system. Which tests are confirmation testing and which are regression testing?
- Tests 1 and 2 are regression testing; tests 3 and 4 are confirmation testing
- Test 1 is confirmation testing; tests 2, 3 and 4 are regression testing
- Tests 1, 2 and 3 are confirmation testing; test 4 is regression testing
- Tests 1 and 2 are confirmation testing; tests 3 and 4 are regression testing
Show answer
- Tests 1 and 2 are regression testing; tests 3 and 4 are confirmation testingThis reverses the two: re-running the failed test confirms the fix, it does not look for adverse consequences.
- Test 1 is confirmation testing; tests 2, 3 and 4 are regression testingNew tests covering the changes needed to fix the defect are also part of confirmation testing.
- Tests 1, 2 and 3 are confirmation testing; test 4 is regression testingThe unchanged order flow is checked for adverse consequences of the change, so it is regression testing.
- Correct answer: Tests 1 and 2 are confirmation testing; tests 3 and 4 are regression testingTests 1 and 2 confirm the fix; tests 3 and 4 look for adverse consequences of the change.
Confirmation testing confirms that an original defect has been successfully fixed, by executing all tests that previously failed due to the defect and also by adding new tests to cover any changes that were needed to fix it — tests 1 and 2. Regression testing confirms that no adverse consequences have been caused by the change; those consequences could affect the same component, other components in the same system, or even other connected systems — tests 3 and 4.
Syllabus section 2.2.3
Question 3
A change has been made to one component. How far can the adverse consequences that regression testing looks for reach?
- Only the component in which the change was made
- Only the changed component and the components it directly calls
- The changed component, other components in the same system, or even other connected systems
- Only those parts of the system that the automated regression suite already covers
Show answer
- Only the component in which the change was madeThe consequences can reach beyond the component in which the change was made.
- Only the changed component and the components it directly callsThe syllabus does not limit the reach to directly called components.
- Correct answer: The changed component, other components in the same system, or even other connected systemsThe same component, others in the same system, or even other connected systems.
- Only those parts of the system that the automated regression suite already coversExisting automated coverage does not bound where adverse consequences can occur.
Regression testing confirms that no adverse consequences have been caused by a change, including a fix that has already been confirmation tested. These adverse consequences could affect the same component where the change was made, other components in the same system, or even other connected systems. Regression testing may also relate to the environment rather than the test object alone.
Syllabus section 2.2.3
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.