Key Features of Functional Test Tools

Tools for functional test automation (such as QuickTest Pro from Mercury Interactive or e-Tester from Empirix) provide features that allow you create and run functional test scripts. These features include:

Software Testing Terms and Meaning - Part 4

  • Data flow Testing
    Testing in which test cases are designed based on variable usage within the code.
  • Data integrity and Database integrity Testing
    Data integrity and database integrity test techniques verify that data is being stored by the system in a manner where the data is not compromised by updating, restoration, or retrieval processing
  • Data-Driven Testing

Software Testing Terms and Meaning - Part 3

Computer Aided Software Testing
Code Coverage
An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.
Compatibility Testing
Testing whether the system is compatible with other systems with which it should communicate.
Component Testing
The testing of individual software components.

Software Testing Terms and Meaning - Part 2

Back-to-back testing Testing in which two or more variants of a component or system are executed with the same inputs, the outputs compared, and analyzed in cases of discrepancies Basis Path Testing A white box test case design technique that uses the algorithmic flow of the program to design tests Benchmark Testing Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration Beta Testing / Field Testin

Software Testing Terms and Meaning - Part 1

Acceptance criteria The expected results or performance characteristics that define whether the test case passed or failed. Acceptance Testing / User Acceptance Testing An acceptance test is a test that a user/sponsor and manufacturer/producer jointly perform on a finished, engineered product/system through black-box testing (i.e., the user or tester need not know anything about the internal workings of the system).