A Test Process Recipe Experiment


  1. Review story requirements: make sure they make sense, answer what problem each story is solving if they are unclear
  2. Create examples for each story (specification-by-example, given-where-then)
  3. Define a test map for each story based on risks/value (Mindmup)
  4. Create a test dashboard (RST)
  5. Run and record short bursts of exploratory tests (Screencastify)
  6. Create record-and-play automated end-to-end checks if possible (Ghost Inspector)
  7. Regularly update the test dashboard
  8. Update WebDriver automated checks when new features are stable in testing environment


  • Better visibility of: a) testing process, b) confidence in software quality, and c) encountered testing issues
  • More critical thinking spent about the problem and the suggested solution in the beginning of each project, less dependency on written specifications
  • Better running documentation

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.