Tests/XS/RestoreDS/Record: Difference between revisions

From OLPC
Jump to navigation Jump to search
(New page: {{Test case |testcase_name=Restore Data of Record Activity from XS to XO |testcase_category=XS |testcase_stream=8.2 |testcase_component=Schoolserver |testcase_feature=kup_and_Restore#Test_...)
 
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 4: Line 4:
|testcase_stream=8.2
|testcase_stream=8.2
|testcase_component=Schoolserver
|testcase_component=Schoolserver
|testcase_feature=kup_and_Restore#Test_plans_and_user_walkthrough]]
|testcase_feature=[[XS_Blueprints:Datastore_Simple_Backup_and_Restore#Test_plans_and_user_walkthrough]]
|testcase_objective=XOs automatically save record 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_objective=XOs automatically save record 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, Record activity and access point.
|testcase_tools=Latest XS software, Record activity and access point.
Line 13: Line 13:
# Make sure to go and look/listen to each file after its been saved to save it to the Journal.
# Make sure to go and look/listen to each file after its been saved to save it to the Journal.
# Confirm that the Journal has entries that read "Photo by [xo-name]", "Video by [xo-name]" and "Audio by [xo-name]" to ensure they backup properly
# Confirm that the Journal has entries that read "Photo by [xo-name]", "Video by [xo-name]" and "Audio by [xo-name]" to ensure they backup properly
#* 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).
#* Items called "Record Activity" in the Journal are not the specific files you created, just a log of that you used Record Activity.
#* Items called "Record Activity" in the Journal are not the specific files you created, just a log of that you used Record Activity.
# Make sure you are still connected to the school server for daily backup (which happens every 24 hours).
# 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.
|testcase_procedure=On the XO, ensure you are hooked up to the School Server network.
<br>
# Wait until the backup run happens - it will be triggered once a day. How to recognize that it has happened?
# Wait until the backup run happens - it will be triggered once a day. How to recognize that it has happened?
#* On the XO, 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.
#* 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!
#* 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.
#** 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 photo/video/audio files from your Journal and reboot your machine.
# Open Browse
# Open Browse after you've connected to the school server.
# Follow the link to the Schoolserver
# Follow the link to the Schoolserver
# Add "ds-restore" to the URL in the url bar, so that it reads http://schoolserver/ds-restore
# Add "ds-restore" to the URL in the url bar, so that it reads http://schoolserver/ds-restore
Line 28: Line 30:
# You will see a listing of the documents available for that date, pick a document
# 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 ;-) )
# 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 begin}}
{{Test results
|testresult_release=8.2.0 (767)
|testresult_stream=8.2
|testresult_build=767
|testresult_passfail=Pass
|testresult_tickets=http://dev.laptop.org/ticket/8912
|testresult_comments=On all 10 XOs each of the files restored great except two XOs did restore the photo correctly but a url address in place of the photo. Tickets attached.
|testresult_date=2008/10/30
}}
{{Test results end}}
{{Test results end}}

Latest revision as of 21:42, 30 October 2008

Test case: Short name::Restore Data of Record Activity from XS to XO
How to report results

Stream ,|x|Build stream::x}}
Category Test category::XS Sub-category [[Test subcategory::{{{testcase_subcategory}}}]]
Component System component::Schoolserver
Feature [[System feature::XS_Blueprints:Datastore_Simple_Backup_and_Restore#Test_plans_and_user_walkthrough]]
Objective Test objective::XOs automatically save record activity data to a schoolserver where they are registered. This test case is ensure that a laptop can restore files from the school server.
Tools Test tools::Latest XS software, Record activity and access point.
Setup [[Test setup::
  1. Get Schoolserver up and running.
  2. Access point connection
  3. Open Record activity and take a picture, video and audio file.
  4. Make sure to go and look/listen to each file after its been saved to save it to the Journal.
  5. Confirm that the Journal has entries that read "Photo by [xo-name]", "Video by [xo-name]" and "Audio by [xo-name]" to ensure they backup properly
    • 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).
    • Items called "Record Activity" in the Journal are not the specific files you created, just a log of that you used Record Activity.
  6. 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.]]
Procedure [[Test procedure::On the XO, ensure you are hooked up to the School Server network.
  1. 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 /usr/bin/ds-backup.sh from a Terminal activity (as the olpc user). You will still have to face the large random delay of up to 30 minutes.
  2. Erase the photo/video/audio files from your Journal and reboot your machine.
  3. Open Browse after you've connected to the school server.
  4. Follow the link to the Schoolserver
  5. Add "ds-restore" to the URL in the url bar, so that it reads http://schoolserver/ds-restore
  6. 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"
  7. You will see a listing of the documents available for that date, pick a document
  8. Clicking on that document will download it, and it will appear in the Journal (and it may auto-open - need to check that ;-) )]]
Expected Results
and Pass Criteria 		Pass criteria::The data from the school server should be restored to the XO.
Comments More notes::
Release Stream Build Pass/Fail Trac Ticket(s) Comment(s) Date of Test
Software release::8.2.0 (767) Build stream::8.2 Build number::767 PassFail::Pass ,|x| #x}} Comments::On all 10 XOs each of the files restored great except two XOs did restore the photo correctly but a url address in place of the photo. Tickets attached. Created::2008/10/30


Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Tests/XS/RestoreDS/Record&oldid=177844"