Test cases 8.2.0
From OLPC
Contents |
[edit] Create new test cases
Now 8.2.0 is complete this section should be its own page "Creating new test cases".
First review the set of test cases that already exist below. Some of them are stubs to be filled out and others include procedures. Also review the category and sub-categories that determine part of your test case name.
[edit] Naming a test case
- Use /Tests/TestCategory/SubCategory(as needed)/TestName as the name of the new test case, for example Tests/Network/XO/SimpleMesh.
- Use the following categories (see Property:Test category):
- Tests/Boot/, Tests/Network/, Tests/Upgrades/, Tests/Journal/, Tests/SugarUI/, Tests/SugarControlPanel/, Tests/Power/, Tests/Peripherals/, Tests/Activity/, Tests/XS/ (school server), Tests/I18N/, Test/SmokeTest/
- Use Test/Activity/TheActivityName as sub-category for an activity, for example Tests/Activity/Record/Private photo sharing.
[edit] Form information
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.
[edit] Adding the test case
To add a new test case, go to Form:Test case and give it your new name.
[edit] Add test results
The test case form has a test result form within it that you can fill in, and you can add additional test results by clicking on the [Add another] button under the test case form.
The tables below have a shortcut: just click the '+' sign next to a test case to edit it in the form, then click the [Add another] button.
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.
- Today's Date
- When did you run the testcase? The month and year will be filled in for you automatically.
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] Test cases
[edit] Activities
If you are creating test cases for an activity, please include the base functionality that is important for all activities; then you can include other functional testing as well.
Base Activity Testing:
- Activity installs from download (if not part of default installation) from website or USB key
- Activity starts up
- You can re-name the activity
- User specific data can be created
- You can force a save
- Activity closes properly from inside the activity
- You can resume the activity from the Journal
- You see the user specific data after resume
- You can close the activity from the Sugar frame
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| Tests/Activity/Analyze | Analyze Activity | basic functional test | |
| Tests/Activity/Browse | Browse activity testing | Basic testing of activity | |
| 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/Calculate | Calculate Activity | basic activity testing | |
| 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/Clock | Clock Activity | Standard activity testing | |
| Tests/Activity/Distance | Distance Activity | basic functional testing | |
| Tests/Activity/Gcompris-Chess | Gcompris Chess | Basic Functionality test | |
| Tests/Activity/Gcompris-Sudoku | Gcompris Sudoku | Basic functionality test | |
| Tests/Activity/Help | Help Activity | standard activity testing | |
| Tests/Activity/Implode | Implode Activity Test | Basic Functional Test | |
| Tests/Activity/License/Clean startup | License Activity - Clean startup | On first run | |
| Tests/Activity/License/Comic enables step 3 | License Activity - Comic enables step 3 | When you go through the comic (after completing the "Read disclaimer" == Step 1), | |
| Tests/Activity/License/License chooser loads | License Activity - License chooser loads | Verify that the license chooser, which relies on a bundled shared object (liblicense.so), loads a working license chooser. | |
| Tests/Activity/Log | Log Activity test | basic functional test | |
| Tests/Activity/Manual download | Manual downloading of activity | Activities can be manually downloaded from OLPC's wiki. | |
| Tests/Activity/Maze | Maze Activity | Basic Functionality Test | |
| Tests/Activity/Measure | Measure Activity | basic functional testing | |
| Tests/Activity/Memorize | Memorize Activity | basic functional test | |
| Tests/Activity/Moon | Moon Activity | Basic functionality test | |
| Tests/Activity/Paint | Paint Activity test | basic functional testing | |
| Tests/Activity/Pippy | Pippy Activity testing | basic functional testing | |
| Tests/Activity/Read | Read Activity | basic activity testing for Read | |
| 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 | Record basic activity test | basic functional test | |
| 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/Ruler | Ruler Activity Test | Basic Functionality test | |
| Tests/Activity/Scratch | Scratch Activity Test | Basic functionality test | |
| Tests/Activity/Speak | Speak Activity Test | Basic functionality test | |
| Tests/Activity/TamTamEdit | TamTam Edit activity test | basic functional testing | |
| Tests/Activity/TamTamJam | TamTam Jam activity basic test | basic functional test | |
| Tests/Activity/TamTamMini | TamTam Mini activity test | basic functional testing | |
| Tests/Activity/TamTamSynth | TamTam Synth Lab activity | basic functional test | |
| Tests/Activity/Terminal | Terminal Activity | basic functional test | |
| Tests/Activity/TurtleArt | TurtleArt Activity | basic functional testing | |
| Tests/Activity/TuxPaint | TuxPaint activity | Basic functional test of TuxPaint sugar api | |
| Tests/Activity/WikipediaEN | WikipediaEN (aka Wikibrowse) | Basic functionality test | |
| Tests/Activity/Write | Write activity | basic functional activity testing | |
| 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/Activity/eToys | eToys activity test | basic functional testing | |
| Tests/Activity/x2o | x2o basic test | Make sure x2o works on 8.2 | |
| Tests/Browse/Sharing bookmarks | Sharing bookmarks | Verify that users collaborating with Browse can share links. |
[edit] Boot
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| Tests/Boot/Activation | Activation during Boot | This test ensures that activation works on secure, non-activated laptops | |
| 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).
(see http://wiki.laptop.org/go/Clean-install_procedure for reference) | |
| Tests/Boot/Security-Disabled | Un-secured boot | Ensure the laptop can boot after 'disable security' has been issued | |
| Tests/Boot/USBUpgrade | USB Upgrade | After using the XO, perform upgrade with USB to preserve journal items | |
| Tests/Boot/olpc-update | olpc-update | From the terminal upgrade your XO using the olpc-update feature. |
[edit] Journal
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| 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/Journal/ResumeImages | Resuming docs with shared images | Ensure that images and tex saved in a shared doc can be resumed properly. |
[edit] Network
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| Tests/Connectivity/Collaboration | Collaboration: access point environment | Laptops can collaborate with each other while connected to an access point. | |
| Tests/Network/100XO/Collaboration | 100 XO, 2 AP collaboration | To verify collaboration working with a 100 XO, 2 AP testbed. | |
| Tests/Network/50XO/Collaboration | 50 XO, 1 AP collaboration | To verify collaboration working with a 50 XO, 1 AP testbed. | |
| Tests/Network/XO/SimpleMesh | Test XOs in Simple Mesh | 10 Laptops connect and collaborate 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 | Ensure laptops can connect to WPA AP, and browse the internet | |
| Tests/Network/XO/WPA2 | XO connection to WPA2 | Ensure the XO can connect to the WPA2 in the garden. | |
| Tests/Network/XS | Test/Network/XS/Dual access points | Find out behavior of laptops trying to connect to the school server with two access points attached. Specifically, whether the laptops switch from one access point to another automatically, and whether they prefer one access point to another. | |
| Tests/Network/XS/20XOPersistence | 20 XOs connected to XS maintain extended collaboration | This test determines whether large numbers of XOs (20) can collaborate on various Activities (here we used Chat, Browse, and Write) for an extended length of time. | |
| 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. |
[edit] Peripherals
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| 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. |
[edit] SugarUI
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| Tests/Sugar/Copy to Clipboard | Copy screenshot to clipboard | Copy to clipboard should work. | |
| Tests/SugarUI/Frame/Devices/Wireless/IPAddressVisibleTest | IPAddressVisible | Verify the eth0 device's IP address is visible in the wireless connection's Frame icon |
[edit] Sugar Control Panel
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| 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. |
[edit] Upgrades
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| Tests/Upgrades/Activities/Default | Activity updater | Ensure that the XO upgrades to the latest default activities | |
| Tests/Upgrades/DataIntegrity | Upgrades from older release | Use case is that someone has been using the major or minor release that is currently in the field. They upgrade to the new release and should be able to get to their journal entries and data from before the upgrade. |
[edit] School Server, XS
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| Tests/XS/Restore/TurtleArt | Restore Data of TurtleArt Activity from XS to XO | XOs automatically save TurtleArt activity 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/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/RestoreDS/Paint | Restore Data of Record Activity from XS to XO | XOs automatically save Paint activity 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/RestoreDS/Record | Restore Data of Record Activity from XS to XO | XOs automatically save record activity 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/RestoreDS/TamTamJam | Restore Data of TamTamJam Activity from XS to XO | XOs automatically save TamTamJam activity 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/RestoreDS/Write | Restore Data from Write Activity from XS to XO | XOs automatically save Write activity 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/RestoreDS/WritewithImages | Restore Data from Write Activity with an image in the document from XS to XO | XOs automatically save Write activity with images in the document 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] Internationalization (I18N)
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| Tests/I18N/keyboards/Arabic | Keyboard test for Arabic | Ensure that a new release booted up on an Arabic keyboard will boot properly, and the characters of the keyboard will be properly represented on the screen. | |
| Tests/I18N/keyboards/Dari | Keyboard test for Dari | Ensure that a new release booted up on an Arabic keyboard will boot properly, and the characters of the keyboard will be properly represented on the screen. | |
| Tests/I18N/keyboards/Kreyol | Keyboard test for Kreyol | Ensure that a new release booted up on an Kreyol keyboard will boot properly, and the characters of the keyboard will be properly represented on the screen. | |
| Tests/I18N/keyboards/Mongolian | Keyboard test for Mongolian | Ensure that a new release booted up on an Mongolian keyboard will boot properly, and the characters of the keyboard will be properly represented on the screen. | |
| Tests/I18N/keyboards/Portuguese | Keyboard test for Portuguese | Ensure that a new release booted up on a Portuguese keyboard will boot properly, and the characters of the keyboard will be properly represented on the screen. | |
| Tests/I18N/keyboards/Thai | Keyboard test for Thai | Ensure that a new release booted up on an Thai keyboard will boot properly, and the characters of the keyboard will be properly represented on the screen. | |
| Tests/I18N/keyboards/US | Keyboard test for US/Eng | Ensure that a new release booted up on a US/Eng keyboard will boot properly, and all characters of the keyboard will be properly represented on the screen. | |
| Tests/I18N/keyboards/amharic | Keyboard test for Amharic | Ensure that a new release booted up on an Amharic keyboard will boot properly, and the characters of the keyboard will be properly represented on the screen. |
[edit] Smoke Test
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| Tests/SmokeTest/.oggFiles | Playing an .ogg File in Browse | Go online in the XO and play an .ogg file to confirm totem-player works | |
| Tests/SmokeTest/Activities | Activities | Open and perform various activities on the XO unit and then close them. | |
| Tests/SmokeTest/Chat | Collaboration with Chat | Initiate a chat within your neighborhood | |
| Tests/SmokeTest/Distance | Distance | Get 2 XOs running the distance activity | |
| Tests/SmokeTest/ImageTransferringandInvite | Image Transferring and Invite | You will open browse, do a search, incorporate that search into a write doc and then invite someone within the mesh to view and comment. | |
| Tests/SmokeTest/InstallingaLibraryBundle | Installing a Library Bundle | Go to the Collections wiki on the XO unit and download some reference materials | |
| Tests/SmokeTest/InstallinganActivityBundle | Installing an Activity Bundle | On a separate computer download an activity bundle to a USB stick then install it on the XO unit. | |
| Tests/SmokeTest/JournalFill | Filling up the journal | Get to the point where the journal has 200+ items to determine how it effects the XO unit | |
| Tests/SmokeTest/NetworkConnections | Trying different connection types | Connect with a school server and confirm in terminal; connect to WPA, WPA2, WEP | |
| Tests/SmokeTest/StartUp | Start Up | Boot up your XO unit in secure and/or non secure mode. You can only boot in secure mode if you are testing a signed release. | |
| Tests/SmokeTest/SuspendResume | Suspend/Resume due to closed unit | Practically close the XO unit (but not fully) to see how the unit reacts | |
| Tests/SmokeTest/USBfiletransfer | Transfer files to a USB stick | Take files either in the journal or in the journal from the activities smoke test (http://wiki.laptop.org/go/Tests/SmokeTest/Activities) |
[edit] Other Test Cases
| Test case | Short name | Test objective | Add test result |
|---|---|---|---|
| Tests/Acquiring a developer key | Acquiring a Developer Key | Verify that a secured XO can be made unsecured by obtaining a developer key online and performing the procedure to turn a secured XO into an unsecured one according to the XO's provided instructions. | |
| Tests/other/Battery | Battery life logging | Check how long the battery lasts for a given build running given sets of Activities; also checks that the build has the ability to monitor battery life through olpc-pwr-log. |
[edit] Other queries
(Edit a section to see its query's syntax.)
For other examples of queries, see Other TestCase Queries, Testcase Query Examples, and comments at Semantic MediaWiki#Suggestions_for_test_cases.
[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.
- 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
- Testing matrix
- many of the pages in Category:Test Plans, e.g. those named Tests/Activity Name
