User:Bambers Linden/scratchpad

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.

Describe the purpose of this test
Link to a user story and / or an optional changeset url
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?
Estimated running time

If special set-up is needed, list test environment requirements such as viewer or server versions, operating systems, specific graphics cards and driver versions, etc.

List other requirements needed to execute the test plan here. e.g...
Basic tester account to use as "User B" where specified
Sandbox, or other area where building is allowed
Describe/include tests to 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.)

Test case 1 (you can briefly outline the goal of the test case here)
1. step 1
2. step 2
3. Verify against expected behavior
Test case 2
1. step 1
2. step 2
3. Verify against expected behavior
Test case 3
1. step 1
2. step 2
3. Verify against expected behavior

(Optional) - as new failures are observed, new test cases can be added here to supplement the functional tests in the section above.

Test for bug VWR-xxxx
1. step 1
2. step 2
3. Verify against expected behavior

Passes if
1. e.g. No unexpected behaviors are observed
Fails if
1. e.g. Expected behaviors are broken
2. e.g. A bug is detected that was not accounted for by this test plan