LITTER BUG

From Test Automation Patterns
Revision as of 15:33, 4 May 2018 by Seretta (talk | contribs) (Topic titles in capital letters)
Jump to navigation Jump to search
.................................................................................................................Main Page / Back to Execution Issues / Back to Test Automation Issues

Issue Summary

Tests leave spurious data in databases, history etc. that slows performance or hinders further tests

Category

Execution

Examples

  1. A test changes the database so that it cannot run again with the same initial conditions
  2. If a test fails, it leaves the System under Test in such a condition that no more tests can run
  3. A test writes so much stuff that the next tests either cannot execute or are much slower

Questions
Are your tests Independent from each other?
What happens when the system crashes?

Resolving Patterns

FAIL GRACEFULLY: If a test fails it should restore the system and the environment so that the successive tests are not affected


.................................................................................................................Main Page / Back to Execution Issues / Back to Test Automation Issues