Interface Testing
Testing conducted to evaluate whether systems or components pass data and control correctly to one another. Contrast with testing, unit; testing, system.
Mutation Testing
A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations.
Operational Testing
Testing conducted to evaluate a system or component in its operational environment. Contrast with testing, development; testing, acceptance;
Parallel Testing
Testing a new or an altered data processing system with the same source data that is used in another system. The other system is considered as the standard of comparison.
Interface Testing
Testing conducted to evaluate whether systems or components pass data and control correctly to one another. Contrast with testing, unit; testing, system.
Mutation Testing
A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations.
Operational Testing
Testing conducted to evaluate a system or component in its operational environment. Contrast with testing, development; testing, acceptance;
Parallel Testing
Testing a new or an altered data processing system with the same source data that is used in another system. The other system is considered as the standard of comparison.
What are the parameters of performance testing?
The term "performance testing" is often used synonymously with stress testing, load testing, reliability testing, and volume testing. Performance testing is part of system testing, but it's also a distinct level of testing. Performance testing verifies loads, volumes, and response times, as defined by requirements.
Qualification Testing
Formal testing, usually conducted by the developer for the consumer, to demonstrate that the software meets its specified requirements.
Statement Testing
Testing to satisfy the criterion that each statement in a program be executed at least once during program testing.
Storage Testing
This is a determination of whether or not certain processing conditions use more storage [memory] than estimated.
Regression Testing
1. Rerunning test cases which a program has previously executed correctly in order to detect errors spawned by changes or corrections made during software development and maintenance.
2. The objective of regression testing is to ensure the software remains intact. A baseline set of data and scripts is maintained and executed to verify changes introduced during the release have not "undone" any previous code. Expected results from the baseline are compared to results of the software under test. All discrepancies are highlighted and accounted for, before testing proceeds to the next level.
No comments:
Post a Comment