Test cases 8.2.0

From OLPC

(Redirected from TestCases 8.2.0)
Jump to: navigation, search

Contents

[edit] 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)

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

[edit] Test cases

Query for all Category:Test cases that are in the Joyride or Any streams.


Test case Short name Test objective Add test
Tests/Activity/Browse/No Visualization Browse test of totem plugin Confirm that the totem plugin's audio visualization is disabled, as this is a waste of power and CPU. +
Tests/Activity/Chat/Private chat Private Chat Verify that users can start and participate in a private (invite-only) chat. +
Tests/Activity/Chat/Public chat Public Chat Verify that users can start and participate in a public (visible to the neighborhood) chat. +
Tests/Activity/Read/Private sharing Private Sharing of a PDF Verify that users can share a PDF file privately. +
Tests/Activity/Read/Public sharing Public Sharing of a PDF Verify that users can share a PDF file publicly with the Neighborhood. +
Tests/Activity/Record/Private photo sharing Private Photo Sharing Verify that users can take and share photos using Record privately. +
Tests/Activity/Record/Public photo sharing Public Photo Sharing Verify that users can take and share photos with their neighborhood. +
Tests/Activity/Write/Private sharing Private Collaboration in Write Verify that several users can collaborate privately with Write. +
Tests/Activity/Write/Public sharing Public Collaboration in Write Verify that several users can collaborate publicly with Write. +
Tests/Boot/Cleaninstall Use USB stick and cleaninstall the image; secure and not secured Ensure that a cleaninstall of a build image works properly from a USB key. Both on secure laptop (with a signed build) and an unsecured laptop (unsigned build). +
Tests/Boot/Security-Disabled Un-secured boot Ensure the laptop can boot after 'disable security' has been issued +
Tests/Browse/Sharing bookmarks Sharing bookmarks Verify that users collaborating with Browse can share links. +
Tests/Connectivity/Collaboration Collaboration: mixed environment Environment with AP and simple mesh and active antenna +
Tests/Journal/Nand-full Nand-full Fill up the Nand memory to >88%; Ensure on the next boot that some files will be deleted automatically to allow booting. +
Tests/Network/XO/SimpleMesh Test XOs in Simple Mesh +
Tests/Network/XO/WEP WEP Access Point connection Ensure that the XO can connect to a WEP AP and browse the internet. +
Tests/Network/XO/WPA WPA Access Point Connection +
Tests/Network/XS/AP/20XOs 20 laptops connect to XS through AP This test is meant to ensure that 20 laptops can connect to a school server through an infrastructure AP; and browse the web. +
Tests/Peripherals/SD SD card read, write, boot Ensure that the SD card functions properly for reading, writing, and booting under normal running conditions which includes suspend and resume. +
Tests/SugarUI/Frame/Devices/Wireless/IPAddressVisibleTest IPAddressVisible Verify the eth0 device's IP address is visible in the wireless connection's Frame icon +
Tests/Sugar Control Panel/About Me/Color Change Color Change Verify that a user can change the colors for his/her XO's icons. +
Tests/Sugar Control Panel/About Me/Name Change Name Change Verify that a user can change the nickname that is used by the XO. +
Tests/Sugar Control Panel/About my XO Checking XO Information Verify that the About my XO pane in the graphical Sugar Control Panel displays the correct information. +
Tests/Sugar Control Panel/Date & Time Change Timezone Verify that the user can change their XO's timezone from the default UTC setting. +
Tests/Sugar Control Panel/Frame/Corner Activation Corner Activation Verify that a user can change the delay before the frame appears when the cursor is moved into the corner of the screen. +
Tests/Sugar Control Panel/Frame/Edge Activation Edge Activation Verify that a user can change the delay before the frame appears when the cursor is moved to an edge of the screen. +
Tests/Sugar Control Panel/Language Change Default Language Verify that the user can change the default language the XO uses. +
Tests/Sugar Control Panel/Network/Radio Activation Radio Activation Verify that a user can deactivate/reactivate the wireless radio. +
Tests/Upgrades/Activities/Default Activity updater Ensure that the XO upgrades to the latest default activities +
Tests/XS/RestoreDS Restore Data from XS to XO XOs automatically save data to a schoolserver where they are registered. This test case is ensure that a laptop can restore files from the school server. +
Tests/XS/backupDS XO Backup to XS Ensure that the XO, after registration to a school server, backs up its data automatically at least once/day. +

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.

[edit] 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.

PassFail Build number Trac bug number
Tests/Activity/Write/Private sharing Pass
Fail		 757757 82818,281
Tests/Activity/Write/Public sharing Fail 757757 82258,225
8,226
8,227
Tests/Sugar/Copy to Clipboard Fail 757757 82878,287
Tests/Sugar Control Panel/Date & Time Fail 22002,200
2,263		 76377,637
Trying to break Fail
Pass		 22002,200
3		 1212


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.

[edit] 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.

Retrieved from "http://wiki.laptop.org/go/Test_cases_8.2.0"
Personal tools
  • Log in / create account
About OLPC
About the XO
Projects
OLPC wiki
Toolbox