1 hour smoke test: Difference between revisions
Jump to navigation
Jump to search
Line 94: | Line 94: | ||
''Actions'' |
''Actions'' |
||
# |
# On your personal laptop, go to [[GCompris]] |
||
# Download the sudoku activity bundle (sudoku.activity.xo) |
# Download the sudoku activity bundle (sudoku.activity.xo) |
||
# Copy this to a USB key. |
# Copy this to a USB key. |
Revision as of 21:50, 5 December 2007
Should take less than one hour to do.
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)
Start-up
Actions
- Boot the laptop
Verify
- If in secure mode: the laptop shows pretty boot
- The laptop boots into sugar
- The journal loads
- 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 AP
- An MPP
- A local mesh
Try out a few Activities
Actions
- Open measure
- Whistle into the microphone. (or just make some noise into the mic)
- Close measure
- Open TamTam Jam
- Make a few instruments play.
- Close TamTam
- If The intruments in TamTam didn't play...
- Open pippy
- Click on the "sequence" sample under sound.
- Click "Run!"
- Close pippy
- Open record
- Take a Picture, Audio sample, and Video sample.
- Play back/view each sample.
- Open Paint
- Draw a few things.
- Close paint
- Pick a few other activities to open and try a few things with them.
- preferably, try activities that have had bug fixes, or new features added.
- make sure that these fixes have indeed worked, and that everything else seems to work properly.
- Would probably be good to go through the full test of that activity, write up bugs, and update the test to fit the new version.
- Resume the paint activity from before.
Verify
- Measure shows the sound waves going into the microphone. (whistling should create a sine wave)
- In TamTam Jam, there is volume, and the instruments play.
- If there is no sound in TamTam Jam, there is in Pippy.
- Report this bug!
- Both the microphone and camera lights are on when Record is the active activity.
- All activities open and close properly
- The journal is able to resume the paint entry.
Image Transferring and Invite
Actions
- Open Browse
- Type some type of animal in the google search bar.
- Click on "Images" at the top of the page.
- Press the top right button on the keyboard. (brings up menu bar)
- Drag one of the images from the google page onto the clipboard. (the left side bar)
- Go to the home view.
- Mouse over the image file on the clipboard, and add it to the journal.
- Go to the journal, find the clipboard image, and then return to the home view.
- Open write
- Press the menu bar button again, and drag the image on the toolbar onto the canvas of the write document.
- Hover over the corner of the image, and resize it to make it smaller than the screen.
- Move the image to the center of the page.
- Type a few lines above the image.
- Go to the mesh view.
- Hover over another XO (one that is also in your possession and running the same build), and click Invite.
- On the second XO, click on the write Icon that shows up in the tray.
- On the second XO, move the image around.
- Type a few lines on both laptops.
Verify
- Browse opens properly.
- The index bar comes up on the left of the page.
- You are able to browse the web for pictures.
- this is not true if you are on link local
- hover over the connection circle in home view to see what type of connection you have.
- Pressing the upper right button toggles the menu bar visible/not visible.
- The image copies to the clipboard and has an eyeball in the middle of the file symbol (means it's recognized as an image file)
- The clipboard object is added to the journal.
- Write opens properly.
- Dragging the image from the clipboard to the write document places a copy of the image in the document.
- You are able to move and resize the document.
- When you invite another XO in the mesh view, an icon of the shared activity shows up in that XO's tray.
- The write document is shared properly.
- Whatever one laptop does to the document, both laptops see the changes.
Installing an Activity Bundle
From USB Key
Actions
- On your personal laptop, go to GCompris
- Download the sudoku activity bundle (sudoku.activity.xo)
- Copy this to a USB key.
- Put the USB key into the XO.
- Go to the Journal and click on the USB key icon.
- Type "sud" in the search window.
- Find the sudoku.activity item, and click on it.
- Click resume. (the activity should install and load)
- Quit the activity.
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
- On the XO, go to Implode
- Click on the Implode.xo file. (download it)
- Go to the home view.
- Find the bundle in new activity in the tray.
- Start the activity and try a few things.
- 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
Actions
- On your XO, go to Library grid
- Click on the download link.
- Click on the bible-en.xol file. (should download to clipboard and journal and install in /home/olpc/Library)
- Go to the journal, and locate the .xol file.
- Close and reopen the browser.
- Check through the index, and find the bible that you just downloaded.
- Open it.
Verify
- The XO can get to the Library grid 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.
Playing an .ogg file in Browse
Actions
- Open the browser activity and type ogg samples in the google search bar.
- Click on the first link.
- 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
- Go to the journal
- 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.
- Click on the USB stick Icon.
- Mouse over the USB icon, and unmount the USB stick
- Put the USB stick in the second XO.
- 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
- On both XO's click on the same AP in each of their mesh views. (wait for them to connect to it)
- Open chat with one XO.
- Share the activity with the neighborhood.
- Go to the Mesh view of that XO.
- Go to the Mesh view of the second XO.
- In the mesh view of the second XO click on the chat activity that the first one just shared.
- Type a few lines in the chat activity on each XO.
- Close the chat activity on both XO's
- 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.
Trying different Connection Types
School Server
(this requires being in a location close enough to a school server)
Actions
- The laptop should boot up and connect to the school server by default if you are near one.
- 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.
- Wait for the inner part of the circle to stop blinking, and the outer part to start connecting.
- This means it has connected to that portal point.
- To check your connection, go to terminal one. (ctrl alt mesh)
- At the login, type "root", and then type olpc-netstatus.
- Note whether the result of Telepathy is salut or gabble.
- Go to the mesh view (ctrl alt home and then mesh)
- Note the XO's you see. Are they laptops around you, or ones most likely beyond the reach of the laptops wi-fi.
- 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}
- IP msh0 :
- 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
- Take many pictures with the Record Activity.
- Add the picture that's on the clipboard many times to the journal.
- 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
- Reboot the laptop.
Verify
- 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
Actions
- Close the laptop almost fully. (just to the point where the screen goes blank)
- Open and close the laptop repeatedly
- Maybe five or six times
- Wait for the laptop to come out of suspend each time before closing it again.
- If the laptop does not come out of suspend on open, try pushing a few buttons and/or touching the mouse pad.
Verify
- The laptop comes out of each suspend successfully.
- The laptop never hangs in suspend or reboots itself when coming out of suspend.