Smoke test: Difference between revisions

(8 intermediate revisions by 4 users not shown)

Line 3:

== 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 ==

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

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

* 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/Getting Involved]]. Please help structure the test results pages. (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 ==

See [[Sugar on a Stick]].

== Test cases ==

Line 40:

Line 49:

# Switch to the Chat Activity.

# '''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.

# '''Verify:''' The Frame hides. (Tests: [[#Frame appears/disappears]])

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

# Resume the Write session you just closed.

Line 107:

Line 118:

=== 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]]

@@ Line 3: / Line 3: @@
 == 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 ==
-* 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.
+* 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.
 * 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/Getting Involved]].  Please help structure the test results pages. (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 ==
+See [[Sugar on a Stick]].
 == Test cases ==
@@ Line 40: / Line 49: @@
 # Switch to the Chat Activity.
 # '''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.
 # '''Verify:''' The Frame hides. (Tests: [[#Frame appears/disappears]])
 # 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.
 # Resume the Write session you just closed.
@@ Line 107: / Line 118: @@
 === 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]]