Tests/XS/backupDS: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (try to fix Stream problem with lowercase "joyride")
No edit summary
 
(11 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Test case
{{Test case
|testcase_name=XO Backup to XS
|testcase_name=XO Backup to XS
|testcase_category=XS
⚫
|testcase_stream=joyride
|testcase_subcategory=backup
⚫
|testcase_stream=joyride, 8.2, Any
|testcase_component=Schoolserver
|testcase_component=Schoolserver
|testcase_feature=[[XS_Blueprints:Datastore_Simple_Backup_and_Restore#Test_plans_and_user_walkthrough]]
|testcase_feature=[[XS_Blueprints:Datastore_Simple_Backup_and_Restore#Test_plans_and_user_walkthrough]]
|testcase_objective=Ensure that the XO, after registration to a school server, backs up its data automatically at least once/day.
|testcase_objective=Ensure that the XO, after registration to a school server, backs up its data automatically at least once/day.
⚫
|testcase_tools=Lastest XS software up and running, Access Point or Active Antenna connection is working.

Ensure that the XO can restore its data from the XS on demand.
⚫
|testcase_tools=Lastest XS software up and running, Access Point or Active Antenna connection is working.

|testcase_setup=<br>
|testcase_setup=<br>
# Setup schoolserver
# Setup schoolserver
# Set up access point
# Set up access point
# To unregister an XO, go to the linux shell, and edit the file (using text editor nano) /home/olpc/.sugar/default/config.

# Delete the two lines [Server] and backup1. Reboot.
|testcase_procedure=<br>
|testcase_procedure=<br>
# Start with an unregistered XO, register it with the XS - either over an Active Antenna mesh connection, or a regular AP wifi connection.
# Start with an unregistered XO, register it with the XS - either over an Active Antenna mesh connection, or a regular AP wifi connection.
Line 18: Line 18:
# Create some documents on the XO - or have them created before registration.
# Create some documents on the XO - or have them created before registration.
# 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?
#* You can push the backup to happen faster than the normal 24 hour wait by:
⚫
#* On the XO, run `stat /home/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/sugar/.default/ds_backup-done` to see it in local time.
- go into Terminal Activity
- type "rm /home/olpc/.sugar/default/ds-backup-done"
- then type "ds-backup.sh" to force the backup
⚫
#* 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 XS, a successful registration will have created a directory `/library/users/<Serial Number>` - and each successful backup run creates a new directory under `/library/users/<Serial Number>/datastore`. The directories have a datestamp, and when the backup run completes successfully, a symlink is updated to point to the latest one (called "datastore-latest").
#* On the XS, a successful registration will have created a directory `/library/users/<Serial Number>` - and each successful backup run creates a new directory under `/library/users/<Serial Number>/datastore`. The directories have a datestamp, and when the backup run completes successfully, a symlink is updated to point to the latest one (called "datastore-latest").

|testcase_expectedresults=The data will show up on the XS in the /library/SN for the XO you are testing.
|testcase_expectedresults=The data will show up on the XS in the /library/SN for the XO you are testing.
}}
}}
{{Test results begin}}
{{Test results
|testresult_release=Candidate
|testresult_stream=8.2
|testresult_build=763
|testresult_passfail=Pass
|testresult_comments=Registered against XS.4 Server.
Restarted.
Open Terminal.
Ran ds-backup.sh
}}
{{Test results
|testresult_release=Candidate
|testresult_stream=8.2
|testresult_build=766
|testresult_passfail=Pass
|testresult_comments=Registered against XS.4 Server.
Restarted.
Open Terminal.
Ran ds-backup.sh
}}
{{Test results
|testresult_release=Candidate
|testresult_stream=8.2
|testresult_build=767
|testresult_passfail=Pass
|testresult_comments=Registered against XS.4 Server.
Restarted.
Open Terminal.
Ran ds-backup.sh
}}
{{Test results
|testresult_release=Candidate
|testresult_stream=8.2
|testresult_build=767
|testresult_passfail=Pass
}}
{{Test results end}}

Latest revision as of 21:33, 10 November 2008

Test case: Short name::XO Backup to XS
How to report results

Stream ,|x|Build stream::x}}
Category Test category::XS Sub-category Test subcategory::backup
Component System component::Schoolserver
Feature [[System feature::XS_Blueprints:Datastore_Simple_Backup_and_Restore#Test_plans_and_user_walkthrough]]
Objective Test objective::Ensure that the XO, after registration to a school server, backs up its data automatically at least once/day.
Tools Test tools::Lastest XS software up and running, Access Point or Active Antenna connection is working.
Setup [[Test setup::
  1. Setup schoolserver
  2. Set up access point
  3. To unregister an XO, go to the linux shell, and edit the file (using text editor nano) /home/olpc/.sugar/default/config.
  4. Delete the two lines [Server] and backup1. Reboot.]]
Procedure [[Test procedure::
  1. Start with an unregistered XO, register it with the XS - either over an Active Antenna mesh connection, or a regular AP wifi connection.
  2. After registration, you need to restart the XO (this is part of the XO side of the registration process as of build 708 / joyride 2121, might not be needed in later builds).
  3. Create some documents on the XO - or have them created before registration.
  4. Wait until the backup run happens - it will be triggered once a day. How to recognize that it has happened?
    • You can push the backup to happen faster than the normal 24 hour wait by:
  - go into Terminal Activity
  - type "rm /home/olpc/.sugar/default/ds-backup-done"
  - then type "ds-backup.sh" to force the backup
    • 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 XS, a successful registration will have created a directory `/library/users/<Serial Number>` - and each successful backup run creates a new directory under `/library/users/<Serial Number>/datastore`. The directories have a datestamp, and when the backup run completes successfully, a symlink is updated to point to the latest one (called "datastore-latest").]]
Expected Results
and Pass Criteria 		Pass criteria::The data will show up on the XS in the /library/SN for the XO you are testing.
Comments More notes::
Release Stream Build Pass/Fail Trac Ticket(s) Comment(s) Date of Test
Software release::Candidate Build stream::8.2 Build number::763 PassFail::Pass ,|x| #x}} [[Comments::Registered against XS.4 Server.

Restarted. Open Terminal. Ran ds-backup.sh]]

Created::


Software release::Candidate Build stream::8.2 Build number::766 PassFail::Pass ,|x| #x}} [[Comments::Registered against XS.4 Server.

Restarted. Open Terminal. Ran ds-backup.sh]]

Created::


Software release::Candidate Build stream::8.2 Build number::767 PassFail::Pass ,|x| #x}} [[Comments::Registered against XS.4 Server.

Restarted. Open Terminal. Ran ds-backup.sh]]

Created::


Software release::Candidate Build stream::8.2 Build number::767 PassFail::Pass ,|x| #x}} Comments:: Created::


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