Parallel testing is used to determine that the results of the new application are consistent with the processing of the previous application or version of the application.
What are the objectives of parallel testing ?
Parallel testing requires that the same input data be run through two versions of the same application. Parallel testing can be done with the entire application or with a segment of the application.
Sometimes a particular segment, such as the day-to-day interest calculation on a savings account, is so complex and important that an effective method of testing is to run the new logic in parallel with the old logic.
If the new application changes data formats, then the input data will have to be modified before it can be run through the new application. This also makes it difficult to automatically check the results of processing through a tape or disk file compare.
The more difficulty encountered in verifying results or preparing common input, the less attractive the parallel testing technique becomes.
What are the Parallel Test Examples ?
Parallel testing should be used when there is uncertainty regarding the correctness of processing of the new application, and the old and new versions of the application are similar.
In applications like payroll, banking, and other heavily financial applications where the results of processing are similar, even though the methods may change significantly – for example, going from batch to online banking – parallel testing is one of the more effective methods of ensuring the integrity of the new application.
Related Posts
Control software testing technique
TESTING CONSTRAINTS PART TWO
LIFE CYCLE TESTING
TEST METRICS
Independent Software Testing
Test Process
Testing verification and validation
Functional and structural testing
Static and dynamic testing
V model testing
Eleven steps of V model testing
Structural testing
Execution testing technique
Recovery Testing technique
Operation testing technique
Compliance software testing technique
Security testing technique
What are the objectives of parallel testing ?
- Conduct redundant processing to ensure that the new version or application performs correctly.
- Demonstrate consistency and inconsistency between two versions of the same application system.
Parallel testing requires that the same input data be run through two versions of the same application. Parallel testing can be done with the entire application or with a segment of the application.
Sometimes a particular segment, such as the day-to-day interest calculation on a savings account, is so complex and important that an effective method of testing is to run the new logic in parallel with the old logic.
If the new application changes data formats, then the input data will have to be modified before it can be run through the new application. This also makes it difficult to automatically check the results of processing through a tape or disk file compare.
The more difficulty encountered in verifying results or preparing common input, the less attractive the parallel testing technique becomes.
What are the Parallel Test Examples ?
- • Operate a new and old version of a payroll system to determine that the paychecks from both systems are reconcilable.
- • Run the old version of the application system to ensure that the operational status of the old system has been maintained in the event that problems are encountered in the new application.
Parallel testing should be used when there is uncertainty regarding the correctness of processing of the new application, and the old and new versions of the application are similar.
In applications like payroll, banking, and other heavily financial applications where the results of processing are similar, even though the methods may change significantly – for example, going from batch to online banking – parallel testing is one of the more effective methods of ensuring the integrity of the new application.
Related Posts
Control software testing technique
TESTING CONSTRAINTS PART TWO
LIFE CYCLE TESTING
TEST METRICS
Independent Software Testing
Test Process
Testing verification and validation
Functional and structural testing
Static and dynamic testing
V model testing
Eleven steps of V model testing
Structural testing
Execution testing technique
Recovery Testing technique
Operation testing technique
Compliance software testing technique
Security testing technique
No comments:
Post a Comment