Tests/XS/RestoreDS/Write: Difference between revisions
(New page: {{Test case |testcase_name=Restore Data from Write Activity from XS to XO |testcase_category=XS |testcase_stream=Any |testcase_feature=[[XS_Blueprints:Datastore_Simple_Backup_and_Restore#T...) |
Eighty-nine (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
{{Test case |
<nowiki>{{Test case |
||
|testcase_name=Restore Data from Write Activity from XS to XO |
|testcase_name=Restore Data from Write Activity from XS to XO |
||
|testcase_category=XS |
|testcase_category=XS |
||
Line 39: | Line 39: | ||
|testresult_date=2008/10/31 |
|testresult_date=2008/10/31 |
||
}} |
}} |
||
{{Test results end}} |
{{Test results end}}</nowiki> |
Revision as of 08:54, 23 October 2010
{{Test case |testcase_name=Restore Data from Write Activity from XS to XO |testcase_category=XS |testcase_stream=Any |testcase_feature=[[XS_Blueprints:Datastore_Simple_Backup_and_Restore#Test_plans_and_user_walkthrough]] |testcase_objective=XOs automatically save Write activity data to a schoolserver where they are registered. This test case is ensure that a laptop can restore files from the school server. |testcase_tools=Latest XS software, Write activity and access point. |testcase_setup=<br> # Get Schoolserver up and running # Access point connection # Open [[Write]] activity and type a sentence or two. # Go to Activity tab and rename your activity something like "testWrite". #* NOTE that we will be erasing the entry to confirm that the restore works. Please don't do some extraordinary work that will make you cry if lost (back it up onto a USB if needbe). # Confirm that the Journal has an entry called "testWrite". # Make sure you are still connected to the school server for daily backup. #* Backup to school server happens every 24 hours, if you'd like to speed this up, read in Procedure how to get backup taken within 30 mins. |testcase_procedure=On the XO, ensure you are hooked up to the School Server network. # Wait until the backup run happens - it will be triggered once a day. How to recognize that it has happened? #* On the XO in the Terminal Activity, be root and run `stat /home/olpc/.sugar/default/ds-backup-done` and look for the 'modified' time, which shows the last time it ran successfully. Check that the XO clock is set to GMT, and might be off-track. Try `TZ=America/New_York stat /home/olpc/.sugar/default/ds-backup-done` to see it in local time. #* To run the script asap, rm /home/olpc/.sugar/default/ds-backup-done -- the script should start within 30 minutes. '''Note''' that the script has a large random delay of up to 30 minutes! #** If you don't want the first "within 30 minutes" wait, just run <tt>/usr/bin/ds-backup.sh</tt> from a Terminal activity (as the olpc user). You will still have to face the large random delay of up to 30 minutes. # Erase the "testWrite" from your Journal and then reboot your machine. # Open Browse after you've connected back to the school server. # Follow the link to the Schoolserver # Add "ds-restore" to the URL in the url bar, so that it reads http://schoolserver/ds-restore # Click on the serial number of your XO #* You can find the serial number of your XO by going into the Control Panel and looking in "About My XO" # You will see a listing of the documents available for that date, pick a document # Clicking on that document will download it, and it will appear in the Journal (and it may auto-open - need to check that ;-) ) |testcase_expectedresults=The data from the school server should be restored to the XO. }} {{Test results begin}} {{Test results |testresult_release=8.2.0 (767) |testresult_stream=8.2 |testresult_build=767 |testresult_passfail=Pass |testresult_comments=all restored fine |testresult_date=2008/10/31 }} {{Test results end}}