...
Note |
---|
|
Description = Test the capability of the system to not add course sites that are listed in a file. Courses in this list will never be batch created. Category of Testing = unit, integration Prerequisite Steps - Note: The application does not need to be stopped for this test to occur
- Scott will add a list of CRNs (valid or not) to the white-list.txt file in /var/sakai/ucd-data folder on the server, in the form of TERMYR-TERMCD-CRN for each entry. This list will be different than that used for the White List Test Scenario. Use this white list
- Scott will add a list of CRNs (valid or not) to the black-list.txt file in /var/sakai/ucd-data folder on the server, in the form of TERMYR-TERMCD-CRN for each entry. Use this black list file file to use here
- Scott will que the batch jobs to run, first Black List, then White List, (5 min time elapse needed)
- Scott will advise programmers that the batches have been run
- Thomas and Scott will monitor server activity while testers are using sakai-dev.
Test Scenario
- Jon G. = will look for CRN xxxxx, yyyyy, zzzzz as user ....... These CRNs will be listed in the Black List
- Brian = will look for CRN aaaaa that is listed both in the white-list.txt and black-list.txt files
- Thomas = view logs, internal sakai db
- Scott = help Jon
Test Cleanup - Scott will remove all sites created in this step when all test cases are completed.
|
Black List Test Results
Would yield an example Summary Test Result of:
...
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 Test Scenario Test Cleanup - Scott will remove all sites created in this step when all test cases are completed.
|
Provider Id Update Results
...
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.
|
Panel |
---|
borderColor | #ccc |
---|
bgColor | white |
---|
titleBGColor | efefef |
---|
title | Site Functionality Test Results |
---|
borderStyle | dashed |
---|
|
Action | Result | Expected Result | Pass/Fail |
---|
colB1 | colB2 | col3 | col4 |
|
...
Note |
---|
title | Course Management data present |
---|
|
Description = Test the course management content displayed in admin tools. Category of Testing = unit, integration, functionality Prerequisite Steps Panel |
---|
borderColor | #ccc |
---|
bgColor | white |
---|
titleBGColor | efefef |
---|
title | Test Scenario |
---|
borderStyle | dashed |
---|
| - Site navigation *
- WorkSite Setup navigation *
- Site Info tool *
|
Test Cleanup - Scott will remove all sites created in this step when all test cases are completed.
|
Panel |
---|
borderColor | #ccc |
---|
bgColor | white |
---|
titleBGColor | #efefef |
---|
title | Course Management Test Results |
---|
borderStyle | dashed |
---|
|
Action | Result | Expected Result | Pass/Fail |
---|
colB1 | colB2 | col3 | col4 |
|
...