...
| Note |
|---|
| title | Update existing sites with appropriate provider id, enabling dynamic rosters (**if CourseMgmtProvider enabled**) |
|---|
|
Description = Test the capability of the system to update existing course sites with associated provider ids. This functionality can be done either in the UI or batch, however we want to
test the ability to run this at any time. Category of Testing = unit, integration Prerequisite Steps - Scott will add a list of sites and provider ids (valid or not) to the provider-list.txt file in /var/sakai/ucd-data folder on the server, in the form of site id, TERMYR-TERMCD-CRN for each entry. Use this file use file here
- Scott will que the batch jobs to run, just the provider id que batch run, (5 min time elapse needed)
- Scott will advise programmers that the batch has been run
- Thomas and Scott will monitor server activity while testers are using sakai-dev.
Test Scenario - Jon G. = will look for site xxxxx's providerid and roster, logging in as admin
- Sandra = will look for site yyyyy's providerid and roster, logging in as ssbatchadmin
- Sandra = will look for site zzzzz's providerid and roster, logging in as ssbatchadmin
- Brian = will validate provider ids and rosters
- Thomas = view logs, internal sakai db
- Scott = help Sandra, Jon, and log in as himself searching for site zzzzz's provider idfor manual updates
Manual Process Check (update provider ids for sites manually): - After site xxxxx,yyyyy, and zzzzz's provider ids are validated,
Scott will update site xxxxx with:
providerId =
and.. site yyyyy with:
providerId = - Thomas will check site xxxxx and site yyyyy's provider id and rosters
Test Cleanup - Scott will remove all sites created in this step when all test cases are completed.
|
*Provider Id Update Test Results
...
Would yield an example Summary Test Result of (both batch and manual updates):
Test | User Role | User Acting As | Result | Expected Result | Pass/Fail | colB1 | colB2 | col3 |
|---|
col4Site xxxxx: Provider Id Update Results | samerson | admin | provider id is ....., roster is same as CRN for provider id | provider id updated and seen in site tool under "provider id", roster reflects provider id roster | P |
| Info |
|---|
| borderColor | #ccc |
|---|
| bgColor | efefef |
|---|
| titleBGColor | ffffcc |
|---|
| title | Test Results, Black List |
|---|
| borderStyle | dashed |
|---|
|
Test | User Role | User Acting As | Result | Expected Result | Pass/Fail |
|---|
Site xxxxx: Provider Id Update Results (batch) | ccjon | admin | x | provider id updated and seen in site tool under "provider id", roster reflects provider id roster | P | Site yyyyy: Provider Id Update Results (batch) | smavocet | ssbatchadmin | x | provider id updated and seen in site tool under "provider id", roster reflects provider id roster | P | Site zzzzz: Provider Id Update Results (batch) | smavocet | ssbatchadmin | x | no roster appears because provider id invalid | P | Site xxxxx: Provider Id Update Results (manual) | samerson | samerson | x | provider id updated via realm edit with accurate data, that from provider id of site yyyyy (provider id=) | P | Site yyyyy: Provider Id Update Results (manual) | samerson | samerson | x | provider id updated via realm edit with accurate data, that from provider id of site yyyyy (provider id=) | P |
|
Site Functionality
| Note |
|---|
|
Description = Test the capability of the system to add sites with the correct pages, tools, tabs, and look and feel. Category of Testing = unit, integration, functionality Prerequisite Steps Test Scenario | Panel |
|---|
| borderColor | #ccc |
|---|
| bgColor | F7D6C1 |
|---|
| titleBGColor | #efefef |
|---|
| title | Individual Functionality Tests |
|---|
| borderStyle | dashed |
|---|
| - Look and Feel *
- Pages *
- Tools on each page *
- Click-through on tools *
- Order *
- Tabs *
|
Test Cleanup - Scott will remove all sites created in this step when all test cases are completed.
|
...