2.1. Documenting Tests

Eventually we all get tired, bored, lazy. Something gets to us

  • test case ID
  • test case description
  • test step or order of execution number
  • related requirement(s)
  • depth
  • test category
  • author
  • check boxes for whether the test can be or has been automated
  • pass/fail
  • remarks