Test cases 8.2.0

From OLPC
Revision as of 21:12, 28 August 2008 by 18.85.46.223 (talk)
Jump to navigation Jump to search

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/Peripherals, Tests/Activity, Tests/XS (school server)

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

  • Name of the test case: What's the overall idea behind the test?
  • 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


Test cases

Query 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?

}}

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.

Test results

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

Anyway, here's a query for any page with a Fail that also displaying some other values.

{{#ask:

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

}}

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.

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.