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