Difference between revisions of "Quality Assurance Testing Format"
Line 4: | Line 4: | ||
'''[URL]''' http://www.yoururl.com/testname The URL of the test. | '''[URL]''' http://www.yoururl.com/testname The URL of the test. | ||
'''[TEST GROUP]''' Test Group | |||
'''[TAGS]''' Tag1 Tag2 Tag3 | |||
'''[VERSION] 0.1''' This is the version number for this test script. | '''[VERSION] 0.1''' This is the version number for this test script. | ||
Line 11: | Line 15: | ||
'''[TESTERS] 1''' Number of testers required to run the test. | '''[TESTERS] 1''' Number of testers required to run the test. | ||
'''[OVERVIEW]''' The overview of the test. | '''[OVERVIEW / GOAL]''' The overview of the test. | ||
'''[SETUP]''' Instructions and other requirements for the test. | '''[SETUP]''' Instructions and other requirements for the test. | ||
Line 21: | Line 25: | ||
'''[INV]''' Place the name of any inventory items that are needed for the test here. It will be added to your test and rezzed when needed. | '''[INV]''' Place the name of any inventory items that are needed for the test here. It will be added to your test and rezzed when needed. | ||
'''[SCRIPT]''' This is where LSL code will be for the test. | '''[LSL SCRIPT]''' This is where LSL code will be for the test. | ||
'''[CASE NAME]''' You'll see this below. Sections within our tests often have headings, which contain the case name. They will be contained in braces as seen here. | '''[CASE NAME]''' You'll see this below. Sections within our tests often have headings, which contain the case name. They will be contained in braces as seen here. | ||
'''[ | '''[EXPECTED OUTCOME]''' The results that are expected from this test | ||
===Reserved Words and Symbols=== | ===Reserved Words and Symbols=== |
Revision as of 06:03, 24 March 2008
Test Script Formatting
[PHYSICSTEST] The name of the test.
[URL] http://www.yoururl.com/testname The URL of the test.
[TEST GROUP] Test Group
[TAGS] Tag1 Tag2 Tag3
[VERSION] 0.1 This is the version number for this test script.
[DURATION] 00:15 Time to execute the test. This will be adjusted during Preview as metrics come in.
[TESTERS] 1 Number of testers required to run the test.
[OVERVIEW / GOAL] The overview of the test.
[SETUP] Instructions and other requirements for the test.
[TEST DATA] Data for the test.
[NOTE] Any other information related to the test, will be expressed at test time with the step that it follows.
[INV] Place the name of any inventory items that are needed for the test here. It will be added to your test and rezzed when needed.
[LSL SCRIPT] This is where LSL code will be for the test.
[CASE NAME] You'll see this below. Sections within our tests often have headings, which contain the case name. They will be contained in braces as seen here.
[EXPECTED OUTCOME] The results that are expected from this test
Reserved Words and Symbols
[DURATION]
[NOTE]
[OVERVIEW]
[SETUP]
[TESTERS]
[INV]
[SCRIPT]
[*]
As long as the case number is enclosed in braces, it can be parsed. In the future we want to support further sub-casing, up to say, 4 levels. Each sub-case level will be able to sustain up to 9999 parts.
The entire script will be parsed at initialization time, and steps (cases) will be indexed.
Here is a sample test script, properly formatted: Quality Assurance Example Script