Regression Testing
Need to complete information management regression testing and want practical suggestions to ensure rapid project delivery?
What is quality assurance testing?
The
objectives of the quality assurance testing phase is to ensure that all software components meet requirements and are ready to transition to
production. This includes ensuring that new software does not introduce errors into existing code.
What is regression testing?
The objectives of this test cycle is to ensure that the new software does not cause
problems with existing software.
This usually involves executing a set of repeatable tests to ensure
that the new software produces the same set of results as the original
test.
Checklist
 Should be based on an approved test plan.
Should be
performed by an independent quality assurance test team in a test environment that
"mirrors" the production environment.
Should test every requirement
and all system, user and production
support documentation.
Test cases, test data and test
results should be defined as
configuration items and handed over to the production support team as
part of the release package.
A small set of data should be used, preferably a sub-set of production data that has been augmented to test new features.
Test
data should be base-lined and backed-up e.g. the same set of data that
was used to conduct the original test should be available for the
regression test.
Expected test results should be documented and attached to the test cases.
Actual test results from the original test should be documented and attached to the original test.
The test environment should be restored to the same condition as the original test.
The same test data that was used for the original test should be re-run as part of the new test.
Changes to test data required to test new data requirements should be documented
Prepare a test plan
to identify script execution schedule and roles and responsibilities.
Review
test plan with QA test team that may be
required to migrate code and/or execute scripts in the test environment.
Migrate all test
objects to the test environment.
Execute work streams that comprise the
test.
Validate test results. If issues are
discovered:
- Document defects in the defect tracking tool;
- Assign defect severity;
- Assign defect to appropriate team for resolution;
- Resolve defect;
- Update unit test data and test results if needed;
- Re-run system and/or integration test if appropriate;
- Place updated unit, system and integration test data
and test results in project documentation repository;
- Check code into code repository;
- Restore test environment test data;
- Create new version of object migration plan to
identify changed objects;
- Migrate modified objects to test
environment;
- Execute work streams that comprise the test;
- Confirm that the test achieves test objectives; and
- Close appropriate defects.
Document test
results.
Place test data and
test results in project documentation repository.
Testing
strategies
Should be
performed by an independent test team in a test environment that
"mirrors" the production environment.
Should test every requirement
and all system, user and production
support documentation.
Should include reconciliation
tests to manually confirm the validity of data.
Should use a sub-set of production
data to reduce time lost to lengthy load processes.
Summary...
The
objectives of the quality assurance testing phase is to ensure that all
software components meet requirements and are ready to transition to
production.
The objective of regression testing is to ensure that the new software does not cause
problems with existing software.
|
