...
| Note |
|---|
| title | Case 2a, Group Provider Tabs test |
|---|
|
Description = Test the capability of the GroupProvider to provide tabs for a user based on their enrollment/membership in sites Category of Testing = functionality,regression Prerequisite Steps - Site user is a member of must be already created prior to test (via Batch? via manually?)
- User must be a member of the sites in order to see the tab
- If user is an externally provided one, then they must be in either the external database (Banner) or already in the internal SmartSite database
Test Scenario 2a, Tabs - Log in as in Case 0d, but become the user and don't log out
- Log in instructor for a given site site (see test data attachment)
- View tabs presented for sites available, and only those that you are a member of and have been created will appear
- Stay logged in for case 2b
Additional step for programmers (Case 2ai), verify that data presented in tabs matches server log data - Data to Be Used:
QA determines
Test Cleanup
None |
Test Results Case 2b2a, Tab functionality
Would yield an example Summary Test Result of:
...
results: Recorded in Jira http://jira.ucdavis.edu:8080/jira/browse/SAK-156
| Note |
|---|
| title | Case 2a, Group Provider Tabs test |
|---|
|
Description = Test the capability of the GroupProvider to provide tabs for a user based on their enrollment/membership in sites Category of Testing = functionality,regression Prerequisite Steps - Site user is a member of must be already created prior to test (via Batch? via manually?)
- User must be a member of the sites in order to see the tab
- If user is an externally provided one, then they must be in either the external database (Banner) or already in the internal SmartSite database
Test Scenario 2b, Realms refreshing - Staying as user from Case 2a, record the site tab that is highlighted
- Brian Donnelly will add a user to this given site, through the external db (by adding a user this way, the 15 minute refresh doesn't have to occur to see the end results)
- Scott will notify Pat Kava of what user has been added to the course externally
- Pat will verify that by hitting the browser refresh after 5 minutes elapsed since update, that the user added appears as a member in the site
Additional step for programmers (Case 2bi), verify that authz refresh is happening via the log output, and at what intervals - Data to Be Used:
QA determines
Test Cleanup
None |
Test Results Case 2b, Realm refresh functionality
Would yield an example Summary Test Result of:
Test | User | User Acting As | Result | Expected Result | Pass/Fail |
|---|
Authz check | Pat Kava | fzolupon? | user xxxxx seen in roster? | user xxxx seen in SmartSite, site yyyyy roster after 5 minutes | P |
results: Recorded in Jira http://jira.ucdavis.edu:8080/jira/browse/SAK-132
Recording Results
The test results will be recorded in Jira by QA testers. They can be of table form or text form.
...