liveBook · Manning

Supplementary testing

As explained in Effective Behavior-Driven Development

Testing activities that complement scenario-based automated checks, including manual and other specialized forms of evaluation.

Passing automated scenarios does not guarantee that the application meets expectations: the tests may not faithfully represent the business intent. Supplementary testing adds human and specialized checks alongside scenario automation. section 4.5

This work can include scripted, manual, exploratory, performance, security, or other testing. Testers usually coordinate it, with other team members helping where appropriate. section 4.1

In a BDD workflow:

  • Start testing as soon as a scenario is complete; preparation can begin earlier. section 4.1
  • Use supplementary testing even when all scenarios pass; it can help restore confidence that automated checks alone may not provide. section 4.5 section 4.8

How Effective Behavior-Driven Development covers it

How deep it goes
Specifies testing forms, coordination, and timing, but leaves detailed procedures to the testing strategy.
Examples
Includes scripted, manual, exploratory, performance, and security testing.
What it assumes
Begins when a scenario is complete, while test preparation can begin earlier.
What you can do after
Perform additional testing that contributes to a high-quality working application and helps complete the story.
How it connects
Connects BDD scenario automation with exploratory testing and test-driven development.

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.