XS Community Edition/0.3/Testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
(155 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{TOCright}}
==XSCE Services Testing Checklist==
=XSCE Smoke Test=
This set of test cases represents a quick smoke test that a build should pass. Please [[http://wiki.laptop.org/go/Submit_bugs file bugs]] in our tracker.


Ideally tests will run against our reference hardware, XO-1.75. Over time, the test will run against more variations in hardware.
Using only the instructions in the [[User:Holt/XS_Community_Edition/0.2/Hacking#Installing | Hacking page]] and a fresh Fedora 17 install.


Please see [[User:Holt/XS_Community_Edition/0.3/Testing/Results | results]] for a summary of smoke test results.
Then repeat all below on XO-1.75 and "big iron" generic/commodity x86.


=Installation=
===Registration (idmgr)===
Register the XSCE (yes, you're actually registering it to itself). You should get a message informing you that registration was successful. Registration also creates a directory named the XO's serial number in /library/users.


Purpose.
===Dynamic Host Configuration Protocol (dhcpd)===
#Verify the installation process works correctly.
Connect an XO to the XSCE's AP. The XO will get an IP in the 172.18.x.x range.


Prerequisites.
===XMPP Server (ejabberd)===
#None
Now that a client XO is connected to the XSCE, register it. 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.


Steps.
===Proxy Caching and Internet Access (squid)===
#Install using the the [[User:Holt/XS_Community_Edition/0.3/Installing | instructions]] and a fresh OLPC-OS 13.1.0 or Fedora 18 install.
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.


Results.
===Apache Web Server (httpd)===
#The install should complete without errors.
Go to http://schoolserver and http://schoolserver.local. Both should resolve to the Apache test page.


=Hardware=
===Activity Server (uses httpd)===
The XSCE can detect and utilize several types of hardware.
If http://schoolserver/upload_activity.php resolves, the Activity Server is working.


=Core Service=
To upload an Activity to the school server, use a browser to navigate to http://schoolserver.local/upload_activity.php.
Core services should be tested using a School Server and a 'client' XO running 13.1.0.
Click on "Choose File", and use the file chooser to indicate which Activity you would like to upload.


==Dynamic Host Configuration (dhcpd)==
===External SD Card for /library===
Purpose
Mount should report /dev/mmcblk0p1 on /library
#Verify the dynamic host configuration is functional.


Prerequisites.
===Ejabberd Web Interface===
#None


Steps
#Go to my neighborhood.
#Click on the name of your Access Point.

Result:
#After a few seconds the connections status will change to "Connected."

Steps
#Open Terminal Activity
#Type the command: service dhcpd status

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

==Network Address Translation/NAT (iptables)==
Purpose.
#Verify network address translation is functional.

Prerequisites
#XO should be connected to XSCE

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

Results
#Site should open correctly

==Registration (idmgr)==
Purpose.
#Verify XO registration is functional.

Prerequisites
#XO should be connected to XSCE.

Steps
# Register the XSCE.

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

==XMPP Server (ejabberd)==
Purpose.
#Verify that the XMPP server is functional.

Prerequisites.
# XO should be registered.

Steps.
# 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.
# Log on as root (su at the command line)
# To verify that ejabberd is managing collaboration and not the LAN, issue this in a root terminal: "ejabberdctl connected-users schoolserver.local"

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

==XMPP based collaboration (ejabberd)==
Purpose.
#Verify that the XMPP based collaboration is functional.

Prerequisites.
# 2 client XOs.

Steps.
#On both XO's click on the same XSCE network
#Confirm that both units are on the same network
#Open chat with one XO
#Share the activity with the neighborhood
#Go to the Network view of that XO
#Go to the Network view of the second XO
#In the network 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 XOs
#Follow the same steps, but starting with the second XO. (see that it works both ways)

Results.
#The shared chat activity shows up in the network 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 and on all three networks

=Extended Service=

==Apache Web Server (httpd)==
Purpose.
#Verify the web server is functional.

Prerequisites.
#XO should be connected to XSCE.

Steps.
#Go to http://schoolserver and http://schoolserver.local.

Results.
#Both should resolve to the XSCE homepage.

==Proxy Caching(squid)==
Purpose.
#Verify Proxy caching is functional.

Prerequisites.
#XO should be connected to XSCE.

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

Results.
#Cache size should increase

==Postgress==
Purpose.
#Verify VPN is functional.

Prerequisites.
#????

Steps.
#???

Results.
#???

==Virtual Private Network (openvpn)==
Purpose.
#Verify VPN is functional.

Prerequisites.
#????

Steps.
#???

Results.
#???

==Moodle==
Purpose.
#Verify Moodle is functional.

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

Steps.
# Open the Browse Activity on the client XO
# browse to "schoolserver.local/moodle

Results.
# 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.
#Verify OLPC-back is functional.

Prerequisites.
#XO should be connected to XSCE.
#XO should be registered.

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

Results.
#On XO /home/olpc/.sugar/default/ds-backup-done should exist
#On XSCE each successful backup run creates the following directories under `/library/users/<Serial Number>/`: datastore-current, documents, and power-logs.

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

==Activity Server==
Purpose.
#Verify That the XSCE can distribute new or updated Activities to classroom XO's.

Prerequisites.
# Build an import USB key as per instructions at http://dev.laptop.org/git/users/martin/xs-activity-server/tree/README
##Create a folder at the root level of a USB key called "xs-activity-server"
##Put a few activity bundles in that directory (suffix=.xo)
##Run "sha1sum *.xo > manifest.sh1

# methods for uploading activities to the server:
##Put that USB key into the XSCE server (the activities should automatically be loaded)
##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.

Results.
# Browse to http://schoolserver/activites and verify that the ones you installed are now available

=Other Tests=

==Internal Gateway==

From the XSCE terminal, do ifconfig and find the IP of the WAN interface. (For example, most home networks will give the XSCE's WAN an IP in the 192.168.x.x range.) From a computer on that IP range, as in your regular home computer, ping the XSCE's IP. Once you get a response, test ssh.

<pre>ssh admin@schoolserver.local
password: 12admin </pre>

If schoolserver.local doesn't resolve, try to ssh in at admin@<ip address>

You can also try to resolve http://schoolserver and/or http://schoolserver.local from a web browser from the desktop on the WAN.

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


Line 40: Line 247:
The username is admin@schoolserver.local and the password is whatever you set above.
The username is admin@schoolserver.local and the password is whatever you set above.


==Using Pidgin to Monitor Ejabberd==
===Internet Domain Name Server (named)===
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.
===Network Address Translation/NAT (iptables)===

===Virtual Private Network (openvpn) [FOR EXPERIMENTATION]===
In the Buddy List window, go to Accounts -> Manage Accounts. Click Add.
===OLPC-update (rsync) [NOT YET SUPPORTED]===

In the Basic tab under Login Options, enter the following values:
<pre>Protocol: XMPP
Username: yourname
Domain: schoolserver.local
Resource: pidgin
Password: yourpassword</pre>

Check "Remember password"

In the Advanced tab, enter the following values:
<pre>Connection security: Use old-style SSL
Connect port: 5223
Connect server: schoolserver.local</pre>

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.

Latest revision as of 23:49, 8 August 2013

XSCE Smoke Test

This set of test cases represents a quick smoke test that a build should pass. Please [file bugs] in our 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.

Core Service

Core services 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)

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 the following directories under `/library/users/<Serial Number>/`: datastore-current, documents, and power-logs.

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

Activity Server

Purpose.

  1. Verify That the XSCE can distribute new or updated Activities to classroom XO's.

Prerequisites.

  1. Build an import USB key as per instructions at http://dev.laptop.org/git/users/martin/xs-activity-server/tree/README
    1. Create a folder at the root level of a USB key called "xs-activity-server"
    2. Put a few activity bundles in that directory (suffix=.xo)
    3. Run "sha1sum *.xo > manifest.sh1
  1. methods for uploading activities to the server:
    1. Put that USB key into the XSCE server (the activities should automatically be loaded)
    2. Upload an Activity to the school server by using a browser to navigate to http://schoolserver.local/upload_activity.php.
      1. Click on "Choose File"
      2. Use the file chooser to indicate which Activity you would like to upload.

Results.

  1. Browse to http://schoolserver/activites and verify that the ones you installed are now available

Other Tests

Internal Gateway

From the XSCE terminal, do ifconfig and find the IP of the WAN interface. (For example, most home networks will give the XSCE's WAN an IP in the 192.168.x.x range.) From a computer on that IP range, as in your regular home computer, ping the XSCE's IP. Once you get a response, test ssh. 

ssh admin@schoolserver.local
password: 12admin

If schoolserver.local doesn't resolve, try to ssh in at admin@<ip address>

You can also try to resolve http://schoolserver and/or http://schoolserver.local from a web browser from the desktop on the WAN.

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.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=XS_Community_Edition/0.3/Testing&oldid=291161"