Smoke test: Difference between revisions

(One intermediate revision by one other user 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 ==

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.

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

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