...
The following is a summary of the testing results, and description of any modification(s) to the test plan followed.Note:
Technical details
Refresh times for materialized views were determined to be approximately 3 minutes around 15 past the hour. For example, for the first view to refresh it started around 1.5 minutes before the top of the hour, and the last view to refresh happened 1.5 minutes after the top of the hour.
Time Start/Stop
Time Testing Started:
10:39
Time Testing Ended:
11:16, last refresh
11:30, time stopped
...
No modifications were made to the test plan, however this scenario uncovered a funcationality issue with Sakai.
Issue: Thomas and Sandra noticed that both "The Staff" and the substituted instructor still appeared in the roster information for the course site. After posting a question on the Sakai collab site, I found that this is a functionality issue with the Sakai framework. The changes that should be propogated from an external source (mViews) to the grants (e.g. providers/authZGroupService) are reflected upon login change or a explicit update of the Realm in question. Due to this current functionality, we may have to list this as a known issue until the community can resolve it.
Changes noticed in Sakai at approx 11:02
...
The prerequisite from Banner is that there is an instructor listed, so Libby and I changed PIDM 170453 as the instructor for the course, to 999999, or the staff.
Changes were reflected in Sakai at approx 11:16
Test Outcome
Overall, the testing went very well. The only hiccup in the testing was Scenario 3, where both "The Staff" and the instructor name appeared in the roster via the Site Info tool in Sakai.