2.2.3 Confirmation Testing and Regression Testing Flashcards
Why changes are typically made to a component or system?
to Enhance by adding a new feature or fix it by removing a defect.
What should testing include?
Confirmation testing and regression testing.
What does confirmation testing confirm?
Original defect has been successfully fixed.
What can one do depending on risk?
Test fixed version of software in several ways.
What ways to test the fixed version of the software are included?
Executing all tests previously failed due to defect or adding new tests to cover changes needed.
When might confirmation testing be restricted?
When time or money is short when fixing defects.
To what might confirmation testing be restricted?
Simply exercising test steps reproducing failure caused by defect and checking failure does not occur.
What does regression testing confirm?
No adverse consequences caused by change including fix already confirmation tested.
What could adverse consequences affect?
Same component where change was made, other components in same system, or even other connected systems.
To what may regression testing not be restricted?
Test object itself but can also be related to environment.
For What is advisable to recognize extent of regression testing?
Perform impact analysis .
What does impact analysis show?
Parts of software could be affected.
How often are regression test suites run?
Many times.
What happens with each iteration or release?
Number of regression test cases will increase.
What is regression testing a strong candidate for?
Automation.
When should test automation start?
Early in project.
Where CI is used, what is good practice?
in DevOps / Include automated regression tests.
Depending on situation, what may automated regression tests include?
Regression tests on different test levels.
When are confirmation and/or regression needed?
On all test levels if defects are fixed and/or changes are made.
