User:Bambers Linden/scratchpad - Revision history

Bambers Linden: /* Scope */

2010-08-24T23:25:44Z

Scope

← Older revision		Revision as of 16:25, 24 August 2010
Line 12:		Line 12:
	== Scope ==		== Scope ==
	* Describe the purpose of this test		* 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 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?		* List any security implications -- does this feature give access to something it should not?

Bambers Linden at 23:00, 24 August 2010

2010-08-24T23:00:56Z

@@ Line 24: / Line 24: @@
 * Basic tester account to use as "User B" where specified
 * Sandbox, or other area where building is allowed
 == Test Steps ==
@@ Line 60: / Line 64: @@
 == Tear Down ==
 * List what must be done to revert the tester's environment to a neutral state

Bambers Linden: /* Regression Tests */

2010-08-24T22:59:03Z

Regression Tests

← Older revision		Revision as of 15:59, 24 August 2010
Line 43:		Line 43:
	=== Regression Tests ===		=== Regression Tests ===
	(Optional) - as new failures are observed, new test cases can be added here to supplement the functional tests in the section above.		(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		# '''Test for bug VWR-xxxx'''
	## step 1		## step 1
	## step 2		## step 2
Line 50:		Line 50:

	----		----

	== Pass/Fail Criteria ==		== Pass/Fail Criteria ==
	# Passes if		# Passes if

Bambers Linden at 22:58, 24 August 2010

2010-08-24T22:58:43Z

← Older revision		Revision as of 15:58, 24 August 2010
Line 27:		Line 27:
	== Test Steps ==		== Test Steps ==
	=== Functional Tests ===		=== Functional Tests ===
	# Test case 1 (you can briefly outline the goal of the test case here)		# '''Test case 1''' (you can briefly outline the goal of the test case here)
	## step 1		## step 1
	## step 2		## step 2
	## '''Verify''' against expected behavior		## '''Verify''' against expected behavior
	# Test case 2		# '''Test case 2'''
	## step 1		## step 1
	## step 2		## step 2
	## '''Verify''' against expected behavior		## '''Verify''' against expected behavior
	# Test case 3		# '''Test case 3'''
	## step 1		## step 1
	## step 2		## step 2

Bambers Linden at 22:57, 24 August 2010

2010-08-24T22:57:54Z

← Older revision		Revision as of 15:57, 24 August 2010
Line 17:		Line 17:

	== Set-up ==		== Set-up ==
	=== Environment: ===		=== 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.		* 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: ===		=== Other ===
	* List other requirements needed to execute the test plan here. e.g...		* List other requirements needed to execute the test plan here. e.g...
	* Basic tester account to use as "User B" where specified		* Basic tester account to use as "User B" where specified

Bambers Linden at 22:57, 24 August 2010

2010-08-24T22:57:25Z

← Older revision		Revision as of 15:57, 24 August 2010
Line 1:		Line 1:
	= ~~New~~ test ~~plan 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.

			----


	== Scope ==		== Scope ==
	* ~~This~~ test ~~walks through...~~		* Describe the purpose of this test
	* ~~The purpose is to...~~		* List any dependencies the new code may have -- what other systems may be affected?
	* ~~Est. Release Date~~		* List any security implications -- does this feature give access to something it should not?
	* ~~Est. Running~~ time		* Estimated running time

	== Set-up ==		== Set-up ==
	=== Environment: ===		=== Environment: ===
	* ~~List~~ test environment requirements such as ~~production~~ or ~~non-production grid~~, ~~platforms~~, ~~minimum Viewer~~ and ~~Server~~ versions, etc.		* 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: ===		=== Other: ===
Line 17:		Line 26:

	== Test Steps ==		== Test Steps ==
			=== Functional Tests ===
			# Test case 1 (you can briefly outline the goal of the test case here)
			## step 1
			## step 2
			## '''Verify''' against expected behavior
			# Test case 2
			## step 1
			## step 2
			## '''Verify''' against expected behavior
			# Test case 3
			## step 1
			## step 2
			## '''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.
			# Test for bug VWR-xxxx
			## step 1
			## step 2
			## '''Verify''' against expected behavior

	~~=== Example Blurb ===~~
	~~This section tests the Viewer's behavior when...~~
	~~# Run Second Life~~
	~~## '''Verify''' the SL app starts and the correct login screen and image are displayed~~
	~~## '''Verify''' the version number is correct (using Help > About... menu item)~~
	~~# '''Verify''' the Dev Grids menu is called using Ctrl-Shift-G key combo~~
	~~## '''Verify''' the Viewer successfully logs into an online dev grid~~
	~~## '''Verify''' the top menu bar is colored <span style="color:red">'''RED'''</span> to indicate the current grid is a development grid~~
	~~# Quit Second Life~~

	----		----
	== Pass/Fail Criteria ==		== Pass/Fail Criteria ==
	# Passes if		# Passes if
			## e.g. No unexpected behaviors are observed
	# Fails if		# Fails if
			## e.g. Expected behaviors are broken
			## e.g. A bug is detected that was not accounted for by this test plan

	== Tear Down ==		== Tear Down ==

Oskar Linden: /* Scope */

2010-08-24T21:05:51Z

Scope

← Older revision		Revision as of 14:05, 24 August 2010
Line 4:		Line 4:
	* This test walks through...		* This test walks through...
	* The purpose is to...		* The purpose is to...
	*		* Est. Release Date
	* Est. Running time		* Est. Running time

Bambers Linden at 20:59, 24 August 2010

2010-08-24T20:59:24Z

← Older revision		Revision as of 13:59, 24 August 2010
Line 2:		Line 2:

	== Scope ==		== Scope ==
	This test walks through...		* This test walks through...
	The purpose is to...		* The purpose is to...
			*
			* Est. Running time

	== Set-up ==		== Set-up ==

Bambers Linden: Created page with '= New test plan template = == Scope == This test walks through... The purpose is to... == Set-up == === Environment: === * List test environment requirements such as product...'

2010-08-24T20:49:53Z

Created page with '= New test plan template = == Scope == This test walks through... The purpose is to... == Set-up == === Environment: === * List test environment requirements such as product...'

New page

= New test plan template =

== Scope ==
This test walks through...
The purpose is to...

== Set-up ==
=== Environment: ===
* List test environment requirements such as production or non-production grid, platforms, minimum Viewer and Server 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

== Test Steps ==

=== Example Blurb ===
This section tests the Viewer's behavior when...
# Run Second Life
## '''Verify''' the SL app starts and the correct login screen and image are displayed
## '''Verify''' the version number is correct (using Help > About... menu item)
# '''Verify''' the Dev Grids menu is called using Ctrl-Shift-G key combo
## '''Verify''' the Viewer successfully logs into an online dev grid
## '''Verify''' the top menu bar is colored <span style="color:red">'''RED'''</span> to indicate the current grid is a development grid
# Quit Second Life

----
== Pass/Fail Criteria ==
# Passes if
# Fails if

== Tear Down ==
* 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.)