XS Community Edition/0.3/Testing: Difference between revisions
| Line 2: | Line 2: | ||
This set of test cases represents a quick smoke test that the build should pass. |
This set of test cases represents a quick smoke test that the build should pass. |
||
==Installing== |
|||
Use only the instructions in the [[User:Holt/XS_Community_Edition/0.3/Installing | installing page]] and a fresh OLPC-OS 13.1.0 or Fedora 18 install. |
Use only the instructions in the [[User:Holt/XS_Community_Edition/0.3/Installing | installing page]] and a fresh OLPC-OS 13.1.0 or Fedora 18 install. |
||
Repeat steps below on an XO or commodity x86 machine. |
Repeat steps below on an XO or commodity x86 machine. |
||
==External SD Card== |
|||
Mount should report /dev/mmcblk0p1 on /library |
Mount should report /dev/mmcblk0p1 on /library |
||
==External USB Drive== |
|||
??? |
??? |
||
==Dynamic Host Configuration Protocol (dhcpd)== |
|||
Connect an XO to the XSCE's AP. The XO will get an IP in the 172.18.x.x range. |
Connect an XO to the XSCE's AP. The XO will get an IP in the 172.18.x.x range. |
||
==Network Address Translation/NAT (iptables)== |
|||
??? |
??? |
||
==Internet Domain Name Server (named)== |
|||
??? |
??? |
||
==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. |
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. |
||
==XMPP Server (ejabberd)== |
|||
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: |
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 |
ejabberdctl connected-users |
||
==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 39: | ||
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. |
||
==Apache Web Server (httpd)== |
|||
Go to http://schoolserver and http://schoolserver.local. Both should resolve to the Apache test page. |
Go to http://schoolserver and http://schoolserver.local. Both should resolve to the Apache test page. |
||
==Proxy Caching and Internet Access (squid)== |
|||
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. |
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)== |
|||
??? |
??? |
||
==Activity Server (uses httpd)== |
|||
If http://schoolserver/upload_activity.php resolves, the Activity Server is working. |
If http://schoolserver/upload_activity.php resolves, the Activity Server is working. |
||
| Line 55: | Line 54: | ||
Click on "Choose File", and use the file chooser to indicate which Activity you would like to upload. |
Click on "Choose File", and use the file chooser to indicate which Activity you would like to upload. |
||
==Virtual Private Network (openvpn)== |
|||
???? |
???? |
||
==1-N WebDAV== |
|||
??? |
??? |
||
==Statistics Collection== |
|||
??? |
??? |
||
==Book server(pathagar)== |
|||
??? |
??? |
||
==Internet in Box== |
|||
??? |
??? |
||
Revision as of 18:20, 10 May 2013
XSCE Smoke Test
This set of test cases represents a quick smoke test that the build should pass.
Installing
Use only the instructions in the installing page and a fresh OLPC-OS 13.1.0 or Fedora 18 install.
Repeat steps below on an XO or commodity x86 machine.
External SD Card
Mount should report /dev/mmcblk0p1 on /library
External USB Drive
???
Dynamic Host Configuration Protocol (dhcpd)
Connect an XO to the XSCE's AP. The XO will get an IP in the 172.18.x.x range.
Network Address Translation/NAT (iptables)
???
Internet Domain Name Server (named)
???
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.
XMPP Server (ejabberd)
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
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.
Apache Web Server (httpd)
Go to http://schoolserver and http://schoolserver.local. Both should resolve to the Apache test page.
Proxy Caching and Internet Access (squid)
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)
???
Activity Server (uses httpd)
If http://schoolserver/upload_activity.php resolves, the Activity Server is working.
To upload an Activity to the school server, use a browser to navigate to http://schoolserver.local/upload_activity.php. Click on "Choose File", and use the file chooser to indicate which Activity you would like to upload.
Virtual Private Network (openvpn)
????
1-N WebDAV
???
Statistics Collection
???
Book server(pathagar)
???
Internet in Box
???