...
- to ensure that current UCDavis modifications to the "plain vanilla" Sakai version 2.3 are merged properly and produce the desired results/functionality,
- to ensure that new fixes features and functionality introduced to in version 2.3 are merged properly functional and produce the desired results/functionality,
- to identify new issues or changes to functionality that may influence UCD's decision to upgrade and/or require notification of faculty and other users.
...
Upgrade Tests - UCD-specific Functional Modifications
These tests which specifically address UCD modifications listed under SAK-214: Upgrade our SmartSite version to Sakai 2.3
...
Jira | Description | Test plan | Test Results/Date |
---|---|---|---|
Support and Training link should be automatically inserted on all newly created project and course sites. | |||
Add a link to the logo image | |||
When adding a participant with their email ID, if the radio button is clicked for "Assign each participant a role individually" the person will not be added. | Follow test plan steps as described in SAK-342 Comments by James Renfro 21/Dec/06 | ||
1) Enable Database Ordering of Site Tools and 2) allow for required tools which cannot be removed by Site Info and are automatically added to a new site | Follow test steps located at UCD v2.3 Upgrade Tests#Enable Database Ordering of Site Tools | ||
Define contributor role and define message center roles | |||
Refactor Gradebook 2.1.x mod's for 2.3 | |||
Upgrade providers and distauth code from 2.2 to work in 2.3 | |||
Configure webdav in Sakai 2.3 | |||
Configure melete in Sakai 2.3 | |||
Upgrade 2-1-x melete in prod to latest melete release | |||
Configure the FCKEditor to spellcheck and to include Greek fonts | |||
Develop a tool and user interface for site creation in 2.3 | |||
Re-define complex id in course objs (hibernate) to be of pattern TERMCODE-CRN, instead of TERMYR-TERMCODE-CRN | |||
n feedback for multiple choice questions, students should only see the selection level feedback for the choice that they made. |
Other Issues:
Jira | Description |
---|---|
Course batching functionality (Course Batching, White List, Course Set Provider Id) | |
loggedOutUrl modifications | |
Link to different gateway site | |
API calls for latest authZGroup info ought to return up-to-date provider information |
For test results, indicate Pass , Fail , or Alert . Alert is used if new issues are raised, if the test is faulty or for any other issue which requires review.
Upgrade Tests - Sakai v2.3 Enhancements
Jira | Description | Test plan | Test Results/Date |
---|
For test results, indicate Pass , Fail , or Alert . Alert is used if new issues are raised, if the test is faulty or for any other issue which requires review.
Upgrade Tests - UCD-specific Look 'n' Feel
This series of tests require visual review for validation. Conduct these tests in multiple OS/browser combinations and note any issues in the Jira specified in the first column.
Jira | Description | Test plan | Test Results/Date |
---|---|---|---|
Allow to replace the help tool's main page with custom content. | To test, view the screen shot graphic at SAK-173 and verify that the Help tool defaults to this page when you select Help from the site menu. | ||
Remove Powered by Sakai image from the portal footer | |||
The Guest Email Address function is misleading in that it impies that access to Sakai/SmartSite can be provided to someone without a UC Davis kerberos login ID. | |||
Reskin the Sakai 2.2/2.3 version with our SmartSite skinSAK |
Post-
...
Course batching functionality (Course Batching, White List, Course Set Provider Id)
Other Issues:
Jira | Description |
---|---|
loggedOutUrl modifications | |
Link to different gateway site | |
API calls for latest authZGroup info ought to return up-to-date provider information |
Post-upgrade Implementationsupgrade Implementations
These tests are for code modifications introduced after the v2.3 upgrade is completed on production.
Jira | Description | Test plan | Test Results/Date |
---|---|---|---|
Checkbox in site info tool that allows admin to remove non-provided users shows for provided users and also if the admin choosed to delete the user, she doesn't ultimately succeed. | |||
Site Application Registration Form | |||
Need to implement preferredRole() in groupprovider |
...