Test cases 8.2.0

Create New Test Cases

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

• Use /Tests/<category>/<sub-category/ as the name of the new test case
• Try to use categories and sub-categories that already exist before creating new ones.

Top level categories: Boot, Network, Upgrades, Journal, SugarUI, SugarControlPanel, Peripherals, Activity, XS (school server)

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

Test Cases

Test cases should use Template:Test case so they can be queried and reported automatically.

Here is a test query that lists all the test cases. Edit this page to see the syntax. We want to ask for all test cases that apply to 8.2.0. There is a Property:Build stream, so let's ask for all Category:Test cases that are in the Joyride or Any streams.

{{#ask: |any

 | ?Short name
 | ?Test objective
 | default=No articles found in Category:Test cases with Property:Stream of joyride or any?

}}

Comments at Semantic MediaWiki#Suggestions_for_test_cases; details of queries at http://semantic-mediawiki.org/wiki/Help:Inline_queries

For other examples of queries, see Testcase Query Examples

Test results

This is a little tricky. Currently each test page has many test results embedded in it, which means each test case has many values for build number, pass/fail, etc. and these values are probably not tied to each other. See Semantic MediaWiki for alternative approaches.

Anyway,

{{#ask:

 PassFail::Fail
 | ?PassFail
 | ?Build number
 | ? Trac bug number
 | default = No tests failing??

}}