Test Script Template

Goals to strive for when writing a test script

• Easy to understand and follow.
• Short enough to be run in 30 minutes or less. If it's too long, break it down into smaller tests.
• Clear description of requirements needed to run the test. Number of users, parcels, etc.

---

• Requirements (ie. # of users, a god account, land, objects needed for the test)

• Est. Running time

• Variables to test (ie. different types of things that generate test permutations)

• Describe the expected behavior and purpose of the new code. (or link to the Design Document)
• List any dependencies the new code may have -- what other systems may be affected?
• List any security implications -- does this feature give access to something it should not?
• Detailed plan(s) for testing new functionality, including success and failure cases if possible.

• Test Setup

• Feature Rule to check
  1. Step
  2. Step

• Corner case to rule
  1. Step
  2. Step

• Detailed plan(s) for testing dependent code, including success and failure cases if possible.

• Compare Performance, if applicable
  • Requirements for gathering data on existing feature being modified.
  • Follow this with requirements for gathering data on new feature in new format, etc.
  • Explain how to compare data to ensure new feature is not worse (i.e. lower framerate, higher bandwidth, more db queries, etc.)