Smoke test - Revision history

Dfarning: update link

2009-08-30T20:12:52Z

update link

← Older revision		Revision as of 16:12, 30 August 2009
Line 3:		Line 3:
	== Introduction ==		== Introduction ==

	Smoke testing is the first quick round of simple tests run on a new software build to verify that it starts and does not catastrophically crash. It is a preliminary to further testing, and is also a fast way to verify the basic integrity of a new development environment, as well as a good tour of basic functionality. The instructions below are for smoke-testing core Sugar using Activities included in Glucose (though it does not test the Activities themselves). To learn how to create smoke tests for other software (such as Activities), see [[~~creating~~ a ~~smoke test~~]].		Smoke testing is the first quick round of simple tests run on a new software build to verify that it starts and does not catastrophically crash. It is a preliminary to further testing, and is also a fast way to verify the basic integrity of a new development environment, as well as a good tour of basic functionality. The instructions below are for smoke-testing core Sugar using Activities included in Glucose (though it does not test the Activities themselves). To learn how to create smoke tests for other software (such as Activities), see [[Release Team/Creating a Smoke Test]].

	== How to smoke test ==		== How to smoke test ==

FGrose: /* How to smoke test */

2009-04-25T03:34:38Z

How to smoke test

← Older revision		Revision as of 23:34, 24 April 2009
Line 11:		Line 11:
	* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.		* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.
	* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.		* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.
	* Summarize your results to help other testers at [[Sugar on a Stick/~~GettingInvolved~~]]. Please help structure the test results pages. (Needed: a way to report smoke test results for builds.)		* Summarize your results to help other testers at [[Sugar on a Stick/Getting Involved]]. Please help structure the test results pages. (Needed: a way to report smoke test results for builds.)

	== Image under test ==		== Image under test ==

FGrose: /* How to smoke test */

2009-04-25T03:34:15Z

How to smoke test

← Older revision		Revision as of 23:34, 24 April 2009
Line 8:		Line 8:

	* [[#Installation and setup\|Install]] the current [[#Image under test\|Sugar image under test]]. All smoke test cases assume you begin with a clean install of Sugar in Home view with no Activities running.		* [[#Installation and setup\|Install]] the current [[#Image under test\|Sugar image under test]]. All smoke test cases assume you begin with a clean install of Sugar in Home view with no Activities running.
	* Review [[Sugar on a Stick/~~GettingInvolved~~]] for known problems with your build.		* Review [[Sugar on a Stick/Getting Involved]] for known problems with your build.
	* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.		* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.
	* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.		* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.

FGrose: /* How to smoke test */

2009-03-28T04:02:03Z

How to smoke test

← Older revision		Revision as of 00:02, 28 March 2009
Line 11:		Line 11:
	* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.		* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.
	* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.		* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.
	* Summarize your results to help other testers at [[Sugar on a Stick/GettingInvolved]]. ~~Pleas~~ help structure the test results pages. (Needed: a way to report smoke test results for builds.)		* Summarize your results to help other testers at [[Sugar on a Stick/GettingInvolved]]. Please help structure the test results pages. (Needed: a way to report smoke test results for builds.)

	== Image under test ==		== Image under test ==

FGrose: /* How to smoke test */

2009-03-28T04:01:39Z

How to smoke test

← Older revision		Revision as of 00:01, 28 March 2009
Line 8:		Line 8:

	* [[#Installation and setup\|Install]] the current [[#Image under test\|Sugar image under test]]. All smoke test cases assume you begin with a clean install of Sugar in Home view with no Activities running.		* [[#Installation and setup\|Install]] the current [[#Image under test\|Sugar image under test]]. All smoke test cases assume you begin with a clean install of Sugar in Home view with no Activities running.
			* Review [[Sugar on a Stick/GettingInvolved]] for known problems with your build.
	* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.		* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.
	* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.		* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.
	* (Needed: a way to report smoke test results for builds.)		* Summarize your results to help other testers at [[Sugar on a Stick/GettingInvolved]]. Pleas help structure the test results pages. (Needed: a way to report smoke test results for builds.)

	== Image under test ==		== Image under test ==

FGrose: /* Installation and setup */

2009-03-28T03:56:38Z

Installation and setup

← Older revision		Revision as of 23:56, 27 March 2009
Line 18:		Line 18:
	== Installation and setup ==		== Installation and setup ==

	~~'''Coming soon~~.~~'''~~		See [[Sugar on a Stick]].

	== Test cases ==		== Test cases ==

CarolineM: /* Features tested */

2009-02-24T18:33:05Z

Features tested

← Older revision		Revision as of 14:33, 24 February 2009
Line 117:		Line 117:

	=== Frame appears/disappears ===		=== Frame appears/disappears ===

			=== Connects to School Server ===

			=== Sugar on a Stick Additional Tests ===
			* Can make a stick
			* Stick can boot a computer
			* All activities on the stick open and run

	* [[#Collaborating, reflecting, and exploring with Activities]]		* [[#Collaborating, reflecting, and exploring with Activities]]

Mchua: /* How to smoke test */

2009-02-24T18:29:55Z

How to smoke test

← Older revision		Revision as of 14:29, 24 February 2009
Line 7:		Line 7:
	== How to smoke test ==		== How to smoke test ==

	* Install Sugar. All smoke test cases assume you begin with a clean install of Sugar in Home view with no Activities running.		* [[#Installation and setup\|Install]] the current [[#Image under test\|Sugar image under test]]. All smoke test cases assume you begin with a clean install of Sugar in Home view with no Activities running.
	* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.		* Execute the smoke test cases below. Test cases are listed in priority order, so if you have limited time, go through them sequentially.
	* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.		* If a smoke test fails, [http://dev.sugarlabs.org file a bug in Trac] noting the failure with as much detail and reproduction steps as possible.
	* (Needed: a way to report smoke test results for builds.)		* (Needed: a way to report smoke test results for builds.)

			== Image under test ==

			For the 0.84 release, we are using Fedora-based [[Sugar on a Stick]] as our common test image.

			== Installation and setup ==

			'''Coming soon.'''

	== Test cases ==		== Test cases ==

Garycmartin: Added naming dialogue (assume this is for 8.3.x testing)

2009-02-23T05:09:31Z

Added naming dialogue (assume this is for 8.3.x testing)

← Older revision		Revision as of 01:09, 23 February 2009
Line 40:		Line 40:
	# Switch to the Chat Activity.		# Switch to the Chat Activity.
	# '''Verify:''' You are able to access the currently running session of Chat. (Tests: [[#Multiple Activities can run simultaneously]])		# '''Verify:''' You are able to access the currently running session of Chat. (Tests: [[#Multiple Activities can run simultaneously]])
	# ~~Close~~ the Chat Activity.		# Stop the Chat Activity.
	# '''Verify:''' The Chat Activity ~~closes~~. (Tests: [[#Activities stop]]		# '''Verify:''' That the Naming Dialogue appears, allowing you to enter a new title, a text description, and tags.
			# Press enter or click the tick icon to dismiss the Naming Dialogue and accept the defaults.
			# '''Verify:''' The Chat Activity stops. (Tests: [[#Activities stop]]
	# Hide the Frame.		# Hide the Frame.
	# '''Verify:''' The Frame hides. (Tests: [[#Frame appears/disappears]])		# '''Verify:''' The Frame hides. (Tests: [[#Frame appears/disappears]])
	# Switch to the Write Activity.		# Switch to the Write Activity.
	# ~~Close~~ the Write Activity.		# Stop the Write Activity.
	# '''Verify:''' The Write Activity ~~closes~~. (Tests: [[#Activities stop]]		# '''Verify:''' The Write Activity stops. (Tests: [[#Activities stop]]
	# Switch to Journal view.		# Switch to Journal view.
	# Resume the Write session you just closed.		# Resume the Write session you just closed.

Garycmartin: /* Activity sessions can be renamed */

2009-02-23T04:56:54Z

Activity sessions can be renamed

← Older revision		Revision as of 00:56, 23 February 2009
Line 122:		Line 122:
	* [[#Collaborating, reflecting, and exploring with Activities]]		* [[#Collaborating, reflecting, and exploring with Activities]]

	=== Activity ~~sessions~~ can be renamed ===		=== Activity titles can be renamed ===

	* [[#Collaborating, reflecting, and exploring with Activities]]		* [[#Collaborating, reflecting, and exploring with Activities]]