Test execution tools
Test execution tools
Test execution tools execute test objects using automated test scripts.
This type of tool often requires significant effort in order to achieve significant benefits.
Capturing tests by recording the actions of a manual tester seems attractive, but this approach does not scale to large numbers of test scripts.
A captured script is a linear representation with specific data and actions as part of each script.
This type of script may be unstable when unexpected events occur.
The latest generation of these tools, which takes advantage of “smart” image capturing technology, has increased the usefulness of this class of tools, although the generated scripts still require ongoing maintenance as the system’s user interface evolves over time.
A data-driven testing approach separates out the test inputs and expected results, usually into a spreadsheet, and uses a more generic test script that can read the input data and execute the same test script with different data.
Testers who are not familiar with the scripting language can then create new test data for these predefined scripts.
In a keyword-driven testing approach, a generic script process keywords describing the actions to be taken (also called action words), which then calls keyword scripts to process the associated test data.
Testers (even if they are not familiar with the scripting language) can then define tests using the keywords and associated data, which can be tailored to the application being tested.
The above approaches require someone to have expertise in the scripting language (testers, developers or specialists in test automation).
Regardless of the scripting technique used, the expected results for each test need to be compared to actual results from the test, either dynamically (while the test is running) or stored for later (post-execution) comparison.
Model-Based Testing (MBT) tools enable a functional specification to be captured in the form of a model, such as an activity diagram. This task is generally performed by a system designer. The MBT tool interprets the model in order to create test case specifications which can then be saved in a test management tool and/or executed by a test execution tool.