Test cases 8.2.0

Create New Test Cases

First review the set of test cases that already exist Test_cases_8.2.0#Test_cases. Some of them are stubs to be filled out and others include procedures. Also review the category and sub-categories being used to choose your test case name.

• Use /Tests/category/sub-category(as needed)/testname as the name of the new test case
• Use the following categories:
  • Tests/Boot/, Tests/Network/, Tests/Upgrades/, Tests/Journal/, Tests/SugarUI/, Tests/SugarControlPanel/, Tests/Power/, Tests/Peripherals/, Tests/Activity/, Tests/XS/ (school server), Tests/I18N/

The form has several fields for you to fill in. Here is what they are used for:

• Name of the test case: Short description of the test case.
• Category: The category this test case falls under. Select the value you used for the <category> part of the name for the new test case.
• Sub-category: The sub-category this test case falls under. Select the value you used for the <sub-category> part of the name for the new test case.
• Stream: What stream of builds does this test belong to? Is it specific to Joyride? Update.1? Any stream?
• Build: If this test is for a specific stream, what is the earliest build number that it applies to? (optional field)
• Component being tested: What is the activity or feature of the XO that this test case is for?
• Wiki link to the feature: Text field.
• Summary: A brief description describing what functionality the test case is intended to verify.
• Tools: Do you need any special tools for the test? In most cases, the answer will be no.
• Setup: Do you need the laptops to have specific builds or activities? Do the laptops explicitly need to be registered (or not) with a schoolserver?
• Procedure: The steps the tester must take to finish the test case.
• Expected results: What should happen if everything is working as expected? What must happen for a run-through of this test case to be considered a pass?
• Notes: Anything else that doesn't fit in the other fields.

To add a new test case, click here: New Test Case

Add Test Results

When creating a test case with the form, you can also add test results if you're running through the test case as you write it into the form by clicking on the "add another" button under the test case form. Here are what the fields are for:

Tested Release

What release build was this? 8.1.1? 7.1.0? A Release Candidate?

Tested Stream

What build stream was used? Joyride? Update.1?

Tested Build

What is the build number that was used?

Pass/Fail

Did the test pass or fail?

Associated trac tickets

List the trac tickets associated with this test if any were filed.

Comments

How did the test fail? A short description of what went wrong.

You can also go to the test case's page and click the "edit with form" tab and add results for the test case using the same method.

Test cases

To add a test result, click the '+' sign next to a test case to edit it in a form, then click the [Add another] button on the form.

Activities

{{#ask: Test category::Activity

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

Boot

{{#ask: Test category::Boot

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

Journal

{{#ask: Test category::Journal

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

Network

{{#ask: Test category::Network

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

Peripherals

{{#ask: Test category::Peripherals

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

SugarUI

{{#ask: Test category::SugarUI

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

Sugar Control Panel

{{#ask: Test category::SugarControlPanel

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

Upgrades

Test category::Upgrades

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases}}

School Server, XS

{{#ask: Test category::XS

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

Internationalization (I18N)

{{#ask: Test category::I18N

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

Other Test Cases

{{#ask: Test category::other

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases }}

Other TestCase_Queries

(Edit this section to see the query's syntax.) For other examples of queries, see Testcase Query Examples Comments at Semantic MediaWiki#Suggestions_for_test_cases.

General (older) Test Cases

This is a list of test cases that existed before the test case template. Once these have been moved into the template, this section can go away.

• Tests/Home_view
• Tests/100_laptops - update chat, read, and add write, browse, and record
• Battery_Results - need new battery life tests for 8.2
• Use_Cases
• many of the pages in Category:Test Plans, e.g. those named Tests/Activity Name