289
edits
Calendar:Tests: Difference between revisions
Add error reporting tests, mvl has a patch for importing speed
(Add error reporting tests, mvl has a patch for importing speed) |
|||
| Line 74: | Line 74: | ||
|- | |- | ||
| 0.2 Migration || You should be able to migrate data created in Sunbird 0.2 to 0.3PR. Choose 'File->Import' and import any calendars you may have created. Events should be successfully imported | | 0.2 Migration || You should be able to migrate data created in Sunbird 0.2 to 0.3PR. Choose 'File->Import' and import any calendars you may have created. Events should be successfully imported | ||
|| | || | ||
|- | |- | ||
| Line 112: | Line 111: | ||
|- | |- | ||
| subscribing || Sunbird should be able to subscribe to a published calendar || | | subscribing || Sunbird should be able to subscribe to a published calendar || | ||
|} | |||
{| border="1" cellpadding="2" | |||
|+Error reporting | |||
|- | |||
! Test !! Description !! Outcome | |||
|- | |||
| Invalid file || Sunbird should report to the user when a file can't be parsed. The calendar should be placed in read-only mode || | |||
|- | |||
| Offline failure || Sunbird should report that a remote calendar cannot be read when internet access in not available. The calendar should be placed in read-only mode || | |||
|- | |||
|Publish failure || Sunbird should report when publishing a calendar fails, for any reason such as insufficient permissions. The calendar should be placed in read-only mode || | |||
|- | |||
| Backup files || Backup files should be made prior to every change to an ICS calendar, and 3 copies should always be kept. || | |||
|} | |} | ||