Difference between revisions of "User:Bambers Linden/scratchpad"

From Second Life Wiki
Jump to navigation Jump to search
Line 24: Line 24:
* Basic tester account to use as "User B" where specified
* Basic tester account to use as "User B" where specified
* Sandbox, or other area where building is allowed
* 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 Steps ==
== Test Steps ==
Line 60: Line 64:
== Tear Down ==
== Tear Down ==
* List what must be done to revert the tester's environment to a neutral state
* List what must be done to revert the tester's environment to a neutral state
-------------------
= Old test script template =
{{OSWikiLearnBox}}
[[Category:Test Scripts]]
==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.
----
==Test script contents==
* 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
*# Step
*# Step
* Corner case to rule
*# Step
*# 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.)

Revision as of 15:00, 24 August 2010

Open Source Portal

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.


Scope

  • Describe the purpose of this test
  • 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

Set-up

Environment

  • 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.

Other

  • 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 Steps

Functional Tests

  1. 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
  2. Test case 2
    1. step 1
    2. step 2
    3. Verify against expected behavior
  3. Test case 3
    1. step 1
    2. step 2
    3. Verify against expected behavior

Regression Tests

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

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


Pass/Fail Criteria

  1. Passes if
    1. e.g. No unexpected behaviors are observed
  2. 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

Tear Down

  • List what must be done to revert the tester's environment to a neutral state
Retrieved from "https://wiki.secondlife.com/w/index.php?title=User:Bambers_Linden/scratchpad&oldid=1016342"