Example usage
A team automates its checkout tests. Each test script contains the steps of a test procedure — opening the cart, filling the shipping form, paying with a test card, verifying the confirmation page — written in a form the automation tool can execute. The scripts are data-driven where possible: the same script runs against different test data sets, making the suite cheap to maintain and extend.
FAQ
Is a test script the same as a test scenario? They overlap: the official definition of test scenario lists test script as an alternative name. In practice, test script is commonly used for the automated procedure, while test scenario denotes the manual action sequence.
What is the difference between a test script and a test procedure specification? A test procedure specification is the documented sequence of actions for executing a test. A test script is commonly used to refer to that same procedure, especially when it is automated.
Do test scripts need test data? Usually yes — data-driven scripts separate the scripted steps from the data, so the same script can be executed with many data sets, which increases coverage per script.
Who writes test scripts? Testers and test automation engineers. Good scripts follow the same review and versioning discipline as any testware.
Related terms
- test scenario — the manual counterpart or alternative name
- test procedure — the documented sequence of actions
- test automation — the practice of executing scripts automatically
- test data — the inputs scripts consume
- test tool — the software that executes scripts
- keyword-driven testing — a script design approach separating keywords from implementation
