Tests/XS/RestoreDS/Record: Difference between revisions
< Tests | XS/RestoreDS
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(2 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= |
|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 |
# 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. |
||
# 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? |
||
Line 20: | Line 22: | ||
#* 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 27: | 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}} |
Latest revision as of 21:42, 30 October 2008
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::
| ||
Procedure | [[Test procedure::On the XO, ensure you are hooked up to the School Server network.
| ||
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
|