2.2.3 Confirmation Testing and Regression Testing Flashcards
Confirmation testing confirms that an original defect has been …
successfully fixed.
Depending on the risk, one can test the fixed version of the software in several ways:
- executing all tests that previously … due to the …
- adding new tests to cover … that were needed …
- have failed
defect or also by - any changes
to fix the defect.
However, when time or money is short when fixing defects, confirmation testing might be restricted to simply … that should reproduce … and checking that …
exercising the test steps
the failure caused by the defect
the failure doesn’t occur.
Regression testing confirms that no adverse “ “ have been caused by a “ “, including a fix that has already …
consequences
change
been confirmation tested.
These adverse consequences could affect:
- the same component where the …
- other components in the …
- or even other c…
- change was made,
- same system,
- connected systems.
Regression testing may not be restricted to the … but can also be related to the “ “.
test object itself
environment
It is advisable to first perform an … to recognize the “ “ of the …
impact analysis
extent
regression testing.
Impact analysis shows which … could be “ “.
parts of the software
affected.
Regression test suites are run many times and generally the number of … will increase with each … so regression testing is a strong “ “ for “ “.
regression test cases
iteration or release,
candidate
automation.
Test automation should be started “ “ in the “ “.
early
project.
Where CI is used, such as in “ “, it’s good “ “ to also include …
DevOps
practice
automated regression tests.
Depending on the situation, this may include r… on different t…
regression tests
test levels.
Confirmation testing and/or regression testing for the test object are needed on all … if defects are “ “ and/or changes are made on these …
test levels
fixed
test levels.
