XS Community Edition/0.3/Testing: Difference between revisions
Line 55: | Line 55: | ||
==XMPP Server (ejabberd)== |
==XMPP Server (ejabberd)== |
||
Verify that the XMPP server is functional. |
|||
⚫ | |||
⚫ | |||
Prerequisites: |
|||
# XO should be registered. |
|||
⚫ | |||
# To verify that ejabberd is managing collaboration and not the LAN, issue this in a root terminal: |
|||
⚫ | |||
==Ejabberd Web Interface== |
==Ejabberd Web Interface== |
Revision as of 19:52, 10 May 2013
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
Verify the installation process works correctly.
- 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
Verify the External SD card used for additional storage is functional.
- Mount /dev/mmcblk0p1
Results -- Should report on /library
External USB Drive
Verify the External USB hard drive used for additional storage is functional.
- ???
Core Service
Dynamic Host Configuration (dhcpd)
Verify the dynamic host configuration is functional.
- 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.
- ???
Internet Domain Name Server (named)
Verify the domain name server is functional.
- ???
Registration (idmgr)
Verify XO registration is functional.
- 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:
- XO should be registered.
- 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.
- To verify that ejabberd is managing collaboration and not the LAN, issue this in a root terminal:
- 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.
- 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.
- Check the initial size of the squid cache directory: du -sh /library/cache.
- From the client XO's Browse Activity, surf the internet.
- Check the cache directory size again and it should be larger.
OLPC-update (rsync)
Verify OLPC-update is functional.
- ???
Activity Server (uses httpd)
Verify http://schoolserver/activities resolves.
- Upload an Activity to the school server by using a browser to navigate to http://schoolserver.local/upload_activity.php.
- Click on "Choose File"
- Use the file chooser to indicate which Activity you would like to upload.
Virtual Private Network (openvpn)
Verify VPN is functional.
- ????
WebDAV
Verify WebDev is functional.
- ???
Statistics Collection
Verify Statistics collection is functional.
- ???
Book server(pathagar)
Verify book server is functional.
- ???
Internet in Box
Verify Internet in Box is functional.
- ???