liveBook · Manning

Manual test script

As explained in Effective Behavior-Driven Development

A written sequence of instructions for a person to execute a software test manually.

A manual test script gives a tester detailed steps for exercising software. Its purpose differs from an illustrative scenario: scripts aim to use a tester’s time efficiently by covering many behaviors, while illustrative scenarios aim to be readable, focused, and quick to run. section 11.3.1

A script may preserve valuable knowledge about a product, but its detailed steps can make its intent hard to understand. It is rarely useful to convert scripts directly into automated illustrative scenarios or Gherkin documentation: doing so can create maintenance work without clear, valuable documentation. section 11.3.1 section 11.4

When working with legacy scripts:

  • Assess each script before reusing it; if its purpose is clear, it may inform an automated illustrative scenario. section 11.3.3
  • Use scripts as clues to areas needing investigation, rather than treating them as finished journey scenarios. Create a journey scenario only when it contributes to the overall flow. section 11.3.2
  • Ask testers and other people familiar with the product about uncertain requirements. Example Mapping can help clarify behavior and recover knowledge. section 11.3.4
  • If using AI to help analyze a script, check suggested scenarios for errors and overlap before keeping them. section 11.3.4

Script versus journey scenario

A script may take a tester through many behaviors while examining each in fine detail. A journey scenario instead focuses on the overall flow, leaving detailed behavior to illustrative scenarios. section 11.3.2

How Effective Behavior-Driven Development covers it

How deep it goes
Distinguishes script goals from illustrative and journey scenarios, and recommends assessment without prescribing a detailed analysis procedure.
Examples
Contrasts detailed scripts that cover many behaviors with focused illustrative scenarios and journey-level flows.
What you can do after
Evaluate legacy scripts for useful intent, then identify when to create illustrative scenarios or seek further knowledge.
How it connects
Connects manual scripts with illustrative scenarios, journey scenarios, Example Mapping, Gherkin, and BDD.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Behavior-Driven Development. The section links point to the parts of the book it draws on.