A number of things really;

  1. summary

  • a logical and clear test name

  • Summarise what you aim to test

  • environment details

  • Pre requisites

  • any test data ( sometimes in the test, sometimes kept separate)

  • test pass / test fail criteria (optional imo)

  1. The test

  • numbered steps

  • maximum of 3 clickable actions per step

  • test data (if put in test)

  • steps are the right level for person executing (low level vs high level)

  • proof read your test

  • prototype screens attached where available



Source link https://www.reddit.com/r//comments/9d8zhp/how_do_you__a__of__a__test/

LEAVE A REPLY

Please enter your comment!
Please enter your name here