XS Community Edition/0.3/Testing

XSCE Smoke Test

This set of test cases represents a quick smoke test that a build should pass. Please file bugs in the bug tracker .

Ideally tests will run against our reference hardware , XO-1.75. Over time, the test will run against more variations in hardware.

Please see results for a summary of smoke test results.

Installation

Purpose.

1. Verify the installation process works correctly.

Prerequisites.

1. None

Steps.

1. Install using the the instructions and a fresh OLPC-OS 13.1.0 or Fedora 18 install.

Results.

1. The install should complete without errors.

Hardware

The XSCE can detect and utilize several types of hardware.

External SD Card

Purpose.

1. Verify the External SD card used for additional storage is functional.

Prerequisites.

1. SD card inserted into XO.

Steps.

1. Mount /dev/mmcblk0p1

Results.

1. Should report on /library

Core Service

Core service should be tested using a School Server and a 'client' XO running 13.1.0.

Dynamic Host Configuration (dhcpd)

Purpose

1. Verify the dynamic host configuration is functional.

Prerequisites.

1. None

Steps

1. Go to my neighborhood.
2. Click on the name of your Access Point.

Result:

1. After a few seconds the connections status will change to "Connected."

Steps

1. Open Terminal Activity
2. Type the command: service dhcpd status

Result: The output should show the following words: Active: active (running)

Network Address Translation/NAT (iptables)

Purpose.

1. Verify network address translation is functional.

Prerequisites

1. XO should be connected to XSCE

Steps.

1. In a browser, go to https://mail.google.com # any site with HTTPS

Results

1. Site should open correctly

Registration (idmgr)

Purpose.

1. Verify XO registration is functional.

Prerequisites

1. XO should be connected to XSCE.

Steps

1. Register the XSCE.

Results.

1. Receive a message that registration was successful.
2. Registration creates a directory named the XO's serial number in /library/users.

XMPP Server (ejabberd)

Purpose.

1. Verify that the XMPP server is functional.

Prerequisites.

1. XO should be registered.

Steps.

1. If you get a message that registration failed, go to the Sugar Control Panel and in Network, clear out the collaboration server field. Upon successful registration, both XOs will appear in Network Neighborhood.
2. Log on as root (su at the command line)
3. To verify that ejabberd is managing collaboration and not the LAN, issue this in a root terminal: "ejabberdctl connected-users schoolserver.local"

Results.

1. a list of all the serial numbers of machines that have been registered to the server

XMPP based collaboration (ejabberd)

Purpose.

1. Verify that the XMPP based collaboration is functional.

Prerequisites.

1. 2 client XOs.

Steps.

1. On both XO's click on the same XSCE network
2. Confirm that both units are on the same network
3. Open chat with one XO
4. Share the activity with the neighborhood
5. Go to the Network view of that XO
6. Go to the Network view of the second XO
7. In the network view of the second XO click on the chat activity that the first one just shared
8. Type a few lines in the chat activity on each XO
9. Close the chat activity on both XOs
10. Follow the same steps, but starting with the second XO. (see that it works both ways)

Results.

1. The shared chat activity shows up in the network view of both laptops
2. Whatever one laptop types in the chat window after both are connected is seen by both laptops
3. Chat works both ways and on all three networks

Extended Service

Apache Web Server (httpd)

Purpose.

1. Verify the web server is functional.

Prerequisites.

1. XO should be connected to XSCE.

Steps.

1. Go to http://schoolserver and http://schoolserver.local.

Results.

1. Both should resolve to the XSCE homepage.

Proxy Caching(squid)

Purpose.

1. Verify Proxy caching is functional.

Prerequisites.

1. XO should be connected to XSCE.

Steps.

1. On XSCE Check the initial size of the squid cache directory: du -sk /library/cache.
2. On XO open Browse Activity and surf the internet.
3. On XSCE Check the squid cache directory size again

Results.

1. Cache size should increase

Postgress

Purpose.

1. Verify VPN is functional.

Prerequisites.

1. ????

Steps.

1. ???

Results.

1. ???

Virtual Private Network (openvpn)- Pending Santi/Ruben setting up a OpenVPN server for testing

Purpose.

1. Verify VPN is functional.

Prerequisites.

1. ????

Steps.

1. ???

Results.

1. ???

Moodle

Purpose.

1. Verify Moodle is functional.

Prerequisites.

1. On a client XO, go to the network neighborhood, and connect to the schoolserver under test
2. register the client with the schoolserver

Steps.

1. Open the Browse Activity on the client XO
2. browse to "schoolserver.local/moodle

Results.

1. You should see the Moodle Administrative page which will display the button labeled "Add a Course".

OLPC-backup

PLEASE NOTE: ds-backup is broken client side in 13.1.0 due to problem with ping being prevented. Please test against a client running 13.2.0

Purpose.

1. Verify OLPC-back is functional.

Prerequisites.

1. XO should be connected to XSCE.
2. XO should be registered.

Steps.

1. rm /home/olpc/.sugar/default/ds-backup-done #delete the ds-backup-done if it exists.
2. /usr/bin/ds-backup.sh nosleep# run backup with the nosleep argument.

Results.

1. On XO /home/olpc/.sugar/default/ds-backup-done should exist
2. On XSCE each successful backup run creates a new directory under `/library/users/<Serial Number>/datastore`.

Please see http://wiki.laptop.org/go/XS_Blueprints:Datastore_Simple_Backup_and_Restore for more information

Activity Server (uses httpd)- Not ready for 0.3 alpha

Purpose.

1. Verify http://schoolserver/activities resolves.

Prerequisites.

1. ???

Steps.

1. Upload an Activity to the school server by using a browser to navigate to http://schoolserver.local/upload_activity.php.
2. Click on "Choose File"
3. Use the file chooser to indicate which Activity you would like to upload.

Results.

1. ???

Ejabberd Web Interface ???

This isn't necessary for testing, but is fun to poke around in:

Register the admin user: ejabberdctl register admin schoolserver.local <password>

In a browser, go to http://schoolserver.local:5280/admin

The username is admin@schoolserver.local and the password is whatever you set above.

Using Pidgin to Monitor Ejabberd

When testing the XSCE, it can be helpful to see at a glance which XO clients have successfully connected to the ejabberd server. Pidgin is a cross platform XMPP client you can use to connect to the schoolserver's ejabberd server from any Windows/Linux/Mac computer. Connected XO clients will appear in the Buddy List.

In the Buddy List window, go to Accounts -> Manage Accounts. Click Add.

In the Basic tab under Login Options, enter the following values:

Protocol:  XMPP
Username:  yourname
Domain: schoolserver.local
Resource: pidgin
Password: yourpassword

Check "Remember password"

In the Advanced tab, enter the following values:

Connection security: Use old-style SSL
Connect port: 5223
Connect server: schoolserver.local

At the very bottom of the "Modify Account" window, check "Create this new account on the server." Click Add, then a registration box will pop up. Click Register, then you should get a pop up box that registration was successful. Click close. In the Accounts box, click the tick box in the "Enabled" column next to your username. If a box pops up for the server certificate, click Accept.

Now in the Buddy List, you should see the XOs that are currently connected to the XSCE's ejabberd server.