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 at https://sugardextrose.org/projects/xsce/issues .

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

For more complete tests, please see https://sugardextrose.org/testlink/index.php .

Installation

Purpose

1. Verify the installation process works correctly.

Steps.

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

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.

Steps

1. Mount /dev/mmcblk0p1

Results

1. Should report on /library

External USB Drive

Verify the External USB hard drive used for additional storage is functional.

1. ???

Core Service

Dynamic Host Configuration (dhcpd)

Verify the dynamic host configuration is functional.

1. Connect an XO to the XSCE's AP.

Result -- The XO will get an IP in the 172.18.x.x range.

Network Address Translation/NAT (iptables)

Verify network address translation is functional.

1. ???

Internet Domain Name Server (named)

Verify the domain name server is functional.

1. ???

Registration (idmgr)

Verify XO registration is functional.

1. Register the XSCE.

Result -- Receive a message that registration was successful.

Result -- Registration creates a directory named the XO's serial number in /library/users.

XMPP Server (ejabberd)

Verify that the XMPP server is functional.

Prerequisites:

1. XO should be registered.

Testing 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. To verify that ejabberd is managing collaboration and not the LAN, issue this in a root terminal:
3. ejabberdctl connected-users

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.

Extended Service

Apache Web Server (httpd)

Verify the web sever is functional.

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

Result -- Both should resolve to the Apache test page.

Proxy Caching(squid)

Verify Proxy caching is functional.

1. Check the initial size of the squid cache directory: du -sh /library/cache.
2. From the client XO's Browse Activity, surf the internet.
3. Check the cache directory size again and it should be larger.

OLPC-update (rsync)

Verify OLPC-update is functional.

1. ???

Activity Server (uses httpd)

Verify http://schoolserver/activities resolves.

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.

Virtual Private Network (openvpn)

Verify VPN is functional.

1. ????

WebDAV

Verify WebDev is functional.

1. ???

Statistics Collection

Verify Statistics collection is functional.

1. ???

Book server(pathagar)

Verify book server is functional.

1. ???

Internet in Box

Verify Internet in Box is functional.

1. ???