Decision to separate or combine Test Procedure and Test Case documentation



  • Background: Combining separate Test Procedure and Test Case documentation has advantages, but so does leaving them separate. IEEE std. 829 mentions system level of complexity as a contributing factor to the decision to combine. From experience, it seems the tradeoff in terms of complexity is whether including test procedures makes the suite too cumbersome to navigate. Reused test procedures that are lengthy may slow down the tester when they could instead repeat a procedure from memory. On the other hand, switching between documents can be slow. Has anyone reached a more concrete point of view on the tradeoffs of these approaches and a method for deciding between them?



  • Since you have said it yourself that having separate documents may add to tester's time, wouldn't it make sense to have a checklist instead of such vast and mostly not so easy to read documents. The checklist can be used for testing and whatever information is gathered during testing can be properly formatted in a document so that the intended stakeholder can easily read and understand it!



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2