Smoke test/11.2.x/1 hour smoke test

This should take less than one hour to do. See smoke test for more.

Useful Links

• Test Config Notes (information on how to configure laptops for different tests)
• Test Network Configuration (detailed information on how to check your network configuration)

• Things to test after updates (These tests should be run when we get to a good candidate release)

Start-up

1. insert battery into laptop,
2. open laptop and tilt screen to operating position,
3. start the laptop by pressing the power button,
4. verify power LED and panel backlight appears, followed by boot animation (XO icon, ring of dots, Fedora remix logo),
5. wait for the laptop to boot to Sugar,
6. verify that the activity ring is displayed,
7. XO-1 only: verify the laptop connects to one of the following (whichever one is highest on the list and available to the laptop); a school server, a preferred access point, an MPP, or a local mesh. If there is a school server present, the laptop MUST be tested against the school server. If it cannot connect to the school server, that is a major failure.
8. XO-1.5 only: verify the laptop will connect to one of the following (whichever is highest on the list and available) a school server, a preferred access point, or an local ad-hoc network.

Try out a few Activities

Test that activities can be opened and closed, that the microphone captures sound, that the speakers emit sound, that the volume control works, that the privacy indicators light, that the camera captures an image, and that the Journal can be used to save and restore previous work.

1. Open Measure activity,
2. verify activity opens,
3. Whistle or sing into the microphone,
4. verify activity shows the sound waves going into the microphone; whistling should create a sine wave, singing may create a more complex wave,
5. Close Measure activity,
6. verify activity closes,
7. Open TamTamJam activity,
8. verify activity opens,
9. Make a few instruments play; press the number corresponding to the one of the displayed loops, or select an instrument and use the alphabetic keys to play different pitch notes,
10. Adjust the volume using the keyboard keys,
11. verify the instruments can be heard,
12. verify the volume can be adjusted,
13. Close TamTamJam activity,
14. verify activity closes,
15. Open Calculate activity,
16. verify activity opens,
17. Use Calculate to perform a simple algebraic calculation
18. verify you get a proper result
19. Use Calculate to make a graph (i.e. "plot(x*x,x=-2..2)")
20. verify the graph appears properly
21. Close Calculate activity,
22. verify activity closes,
23. Open Read activity,
24. verify activity opens,
25. Use Read to open a PDF formatted document
26. verify the PDF formatted document can be read
27. Close Read and reopen it; verify you can read an EPUB formatted document
28. verify the EPUB formatted document can be read
29. Close Read activity,
30. verify activity closes,
31. Open Record activity,
32. verify activity opens,
33. Take a Picture, Audio sample, and Video sample,
34. verify both the microphone and camera lights are on when Record is active,
35. Play or view each sample,
36. verify the samples are intact,
37. Close Record activity,
38. verify activity closes,
39. Open Paint activity,
40. verify activity opens,
41. Draw a few things,
42. Remember what you see,
43. Close Paint activity,
44. verify activity closes,
45. Pick a few other activities to open and try a few things with them.
    • try activities that have had bug fixes, or new features added.
    • verify these fixes have worked, and that everything else seems to work properly.
    • consider a full test of that activity, write up bugs, and update the test to fit the new version.
46. Display the Journal,
47. verify that a Paint entry is in the Journal,
48. verify that audio, video and image files are in the Journal from your use of Record activity,
49. Resume the Paint entry from the Journal,
50. verify Paint activity opens,
51. verify that the Paint image is restored,
52. Close Paint activity,
53. verify activity closes.

Image Transferring and Invite

(you need a second XO to do this test)

1. Open Browse activity
2. verify Browse opens properly.
3. Enter a type of animal in the Google search bar, for example "horse",
4. verify Google search result page is displayed,
5. Click on "Images" at the top of the search result page,
6. Press the top right button on the keyboard. (brings up menu bar)
7. Right-click on one of the images from the Google page, and select Copy,
8. verify an icon appears for a short time on the bottom left of screen,
9. Display the Frame,
10. verify an icon is present in the clipboard area, left edge of screen; it will have eyeball in the middle of the icon,
11. Right-click on the clipboard icon, and select Keep,
12. Display the Journal,
13. verify the icon has been saved in the Journal,
14. Open Write activity
15. verify the Write activity opens,
16. Display the frame,
17. Drag the clipboard icon into the Write document canvas,
18. verify the image has been placed in the document,
19. Click in the image on the document,
20. verify the cursor changes to a positioning cross,
21. Drag the image to another part of the document,
22. verify the image moves,
23. Type a few lines above the image.
24. Go to the Neighbourhood view.
25. Right-click on another XO (one that is also in your possession and running the same build), and click Invite or Invite to Write Activity,
26. On the second XO, click on the Write icon that shows up in the tray, or on the Write icon in the Neighbourhood view,
27. wait for the document to be shared,
28. verify the same image is shown by the Write activity on both XOs,
29. On the second XO, move the image around,
30. Type a few lines on both laptops,
31. verify the changes made on one laptop are shown on the other.

See also http://wiki.sugarlabs.org/go/Smoke_test

Installing an Activity Bundle

From USB Key

Actions

1. On your personal laptop, go to http://activities.sugarlabs.org
2. Download the latest version of the GCompris sudoku activity bundle (sudoku.activity.xo)
3. Copy this to a USB key.
4. Put the USB key into the XO.
5. Go to the Journal and click on the USB key icon.
6. Type "sud" in the search window.
7. Find the sudoku.activity item, and click on it.
8. Click start. (the activity should install and load)
9. Quit the activity.

Don't unmount/unplug the USB stick: you'll be using it in some tests below

Verify

• The USB key icon comes up in the journal.
• Searching for "sud" gets you the sudoku activity bundle (along with anything else on the the key with "sud" in the name)
• Resuming the bundle, installs the activity and runs it.
  • The activity bundle should be unzipped in /home/olpc/Activities (that's what is meant by installed)

From the Web Actions

1. On the XO, go to StarChart
2. Click on the StarChart.xo file. (download it-may take you to a second page where the link shows up toward the top of the page. Clicking here will allow you to see if it downloaded, i.e. "show in journal" or "ok" buttons appear. Click either.)
3. Go to the home view.
4. Find the bundle in new activity in the tray.
5. Start the activity and try a few things.
6. Quit the activity.

Verify

• The file downloads from the browser.
• The activity is installed, and its icon shows up in the tray.
• The activity loads.

Installing a library bundle

online

Actions

1. On your XO, go to Collections.
2. Click on the "Web design" download link under "Books" [Web_design-3.xol file] and download this file to the XO.
3. On the Journal page, click on Web_design-3.xol link (should download and install in /home/olpc/Library).
4. Click on another randomly selected file from the library grid.
5. Close and reopen the browser.
6. Check through the index on the left under books, and find the bible and second bundle that you just downloaded.
7. Open it.

Verify

• The XO can get to the Collections page.
• When you click on the .xol bundle it is downloaded to the clipboard + journal, and it is installed in /home/olpc/Library
• The file is accessible in the browser index.
• You are able to open and view the bible.

offline

Actions

1. On your XO, click on "science" under the lefthand index on the browse page, then "biology".
2. Click on Phyla [PDF].
3. Click on "OK" after download is completed.

• Do the following until #6166 is fixed. --Chihyu 11:47, 25 January 2008 (EST)

1. Go to the journal, and locate the .pdf file and resume it.

Verify

• The XO can get to the "biology" menu.
• When you click on the Phyla [PDF] link, the .pdf file is downloaded to the journal, and is opened by Read automatically. (This requires #6166 to be fixed. --Chihyu 11:47, 25 January 2008 (EST))

Playing an .ogg file in Browse

Actions

1. Open the browser activity and type "ogg samples" in the google search bar.
2. Click on the first link.
3. Scroll down to the sample files, and click on one of the .ogg files.

Verify

• The browser opens the totem-player.
• The file is played.

Transfer files to USB stick

Actions

1. Go to the journal
2. Drag and drop each of these items from the journal onto the usb stick
   • The write activity
   • The Clipboard object: Image.
   • The Paint activity.
   • The {animal} Google Image Search session of the Browse activity.
   • The Video created by record.
3. Click on the USB stick Icon.
4. Mouse over the USB icon, and unmount the USB stick
5. Put the USB stick in the second XO.
6. Resume each item.

Verify

• Each of the items dragged onto the USB stick show up as items on it.
• The usb stick unmounts, and the journal view no longer contains a bottom bar with journal and usb icons.
• Each item transferred to the usb stick resumes on the second XO.

Collaboration with Chat

Actions

1. On both XO's click on the same AP in each of their mesh views. (wait for them to connect to it)
   • (why? should we be using an infrastructure AP, a mesh, or what? -DanielDrake 10:27, 9 January 2008 (EST))
2. Open chat with one XO.
3. Share the activity with the neighborhood.
4. Go to the Mesh view of that XO.
5. Go to the Mesh view of the second XO.
6. In the mesh view of the second XO click on the chat activity that the first one just shared.
7. Type a few lines in the chat activity on each XO.
8. Close the chat activity on both XO's
9. Follow the same steps, but starting with the second XO. (see that it works both ways)

Verify

• The shared chat activity shows up in the mesh view of both laptops.
• Whatever one laptop types in the chat window after both are connected is seen by both laptops.
• Chat works both ways.

Collaboration with Distance

Actions

1. On both XO's click on the same AP in each of their mesh views. (wait for them to connect to it)
2. Open Distance with one XO.
3. Share the activity with the neighborhood.
4. Go to the Mesh view of that XO.
5. Go to the Mesh view of the second XO.
6. In the mesh view of the second XO click on the distance activity that the first one just shared.
7. On the first XO, press the check key on the game pad to start measuring the distance.
8. Close the Distance activity.
9. Follow the same steps, but starting with the second XO. (see that it works both ways)

Verify

• The shared Distance activity shows up in the mesh view of both laptops.
• The tiny circle with a check on the screen of both XOs should turn green.
• The first XO should make sounds after the check key is pressed.
• Both XOs should show the distance between each other on the screen.
• Distance works both ways.

Trying different Connection Types

School Server

(this requires being in a location close enough to a school server)

Actions

1. The laptop should boot up and connect to the school server by default if you are near one.
2. If you don't want to reboot to connect, click on the Mesh Network Channel, which the school server is on, in the mesh view.
3. Wait for the inner part of the circle to stop blinking, and the outer part to start connecting (testing 8.2 just hover your cursor to ensure connection).
   • This means it has connected to that portal point.
   1. To check your connection, go to terminal one. (ctrl alt mesh)
   2. At the login, type "root", and then type olpc-netstatus. (for newer build, type "olpc" instead of "root")
   3. Note whether the result of Telepathy is salut or gabble.
4. Go to the mesh view (ctrl alt home and then mesh)
5. Note the XO's you see. Are they laptops around you, or ones most likely beyond the reach of the laptops wi-fi.
6. Do the same with a second or third laptop to ensure that it's in the same configuration.

Verify

• The laptop connects to the school server by default after reboot.
• (alternatively) The laptop connects to the school server if you click on its portal point in the mesh view.
• The result of running olpc-netstatus is:
  • IP msh0 :
    • 172.x.x.x(172.18.x.x when connected to the School server in OLPC offices)
    • 192.168.x.x
    • 10.x.x.x
  • Config : School server
  • Telepathy :
    • salut (means failure to connect to a jabber server
    • gabble (then the result of Jabber is : {name of jabber server you're connected to}
• If you're running salut, you only see laptops that are around you and also connected to the same server.
• If you're running gabble, you see laptops connected to the same jabber server.
• NOTE: laptops running gabble cannot see laptops running salut and vise-versa.

Filling up the Journal

(OPTIONAL: can take a long time. Once a script is written to fill up the journal, this test will be easier to do)

Actions

1. Take many pictures with the Record Activity.
2. Add the picture that's on the clipboard many times to the journal.
3. Open other activities, do one thing, and close them.
   • Do these things until you have 200 items in the Journal.
   • To count the number of items, go to the terminal, and type: ls /home/olpc/.sugar/default/datastore/store/ | wc -l
4. Reboot the laptop.

Verify

1. • The Journal does not crash (give a blank screen)
   • The laptop does not slow down significantly.
   • Booting into X does not take much longer than normal.

Suspend/Resume due to Cover close

NOTE: should only be done on laptops with production ECO or MP build

Actions

1. Close the laptop almost fully. (just to the point where the screen goes blank)
   • Another way of achieving the same result is pressing the power button. Pressing the power button again will bring the machine out of suspend
   • Open and close the laptop; it should not automatically wake up from suspend until the power button is pressed.
   • Repeat the above several times, waiting for the laptop to come out of suspend each time before closing it again.
   • The laptop should not come out of suspend on open, or due to touching the keyboard and/or mouse pad unless this has explicitly been enabled. Only the power button by default should be able to wake up the laptop from suspend after it has been closed or the power button has been pressed.

Verify

• The laptop comes out of each suspend successfully.
• The laptop never hangs in suspend or reboots itself when coming out of suspend.