...
| title | DRAFT |
|---|
...
JIRA Ticket(s) relating to this story:
| Info | ||
|---|---|---|
| ||
In order to test the bug fix that went in with SAK-259, it's necessary to have at least one user assigned to the template project or course. It will also be necessary to verify that the "Next" and "Back" buttons work correctly in all cases, and that the paging of 5,10,20,etc... training sites works in the Manage Sites view. For more details on all of this, look for Bug Fix! annotations in the test plan below. |
...
Setup Prerequisites
- The following new realms need to be created:
- Create realm !user.template.trainer with auth permissions checked for:
- site.add.training-course
- site.del.training-course
- site.add.training-project
- site.del.training-project
- site.upd.site.mbrshp
- ...and any other 'read' permissions for which we want to copy content
- Copy realm !site.template.course to !site.template.training-course
- Copy realm !site.template to !site.template.training-project
- Create realm !user.template.trainer with auth permissions checked for:
- A new user needs to be created for each tester, of type trainer, and the login/password combo need to be made available to that tester
- Add the tool "Training Sites" to each user's My Workspace
- A course training template of type "training-course" needs to be created with all the necessary tools and content and each tester's user needs to be granted Instructor permission on it.
- A project training template of type "training-project" needs to be created with all the necessary tools and content and each tester's user needs to be granted maintain permission on it.
Acceptance Tests
Goal: Basically, the goal here is to add one or more sites of a given template (project or course) to the SmartSite instance, using a user's kerberos id or ucdavis email address as the key. The user should then be able to login and access the course or project normally as 'maintain' or 'instructor' role. Also, the trainer should have the same role on that site.
...
Component Name(s): ucd-training-admin-tool
...
...
...
...
...
...
...
...
| Info | ||
|---|---|---|
| ||
|
...
Functional Area: Site Creation Tool for Trainers
...
...
...
...
...
...
...
...
...
...
...
|
1.0 Functional Verification
- Login as trainer1
- Navigate to "Training Sites" in left-hand column
- This should present a view called "Training Sites" with the title "Manage Training Sites"
- Initially, the list of training sites may be empty
- There are three choices of action here
- Add Training Sites
- This will take you to the first screen of a four-step process
- Simply type kerberos ids or ucdavis email addresses into the text box, one-per-line, and click "Next"
- A table of users should now be displayed, showing the identifier you passed, the full name of the user, their kerberos, email, possibly some notes, and a checkbox marked "Ignore"
- If you click the checkbox to the right of a user, no site will be created in the following steps for that user
- If the kerberos or email address passed was incorrect or could not be found, then no data will appear for that identifier and the "Notes" field should indicate that the user was not found
- A list of potential template sites should be displayed in a dropdown box, choose the one you wish to copy
- Click Next
- Now you should be prompted to select the tools you wish to copy from the template site – by default, every tool is selected. If you do not want to copy a tool over, simply uncheck the checkbox
- Click Next
- Now you should be promtped to select any available content to copy over from the template site. Note that only a subset of the tool content can be copied. Just as in the step above, all content will be copied by default.
- Click "Create Sites"
- You should now see the Sites appear in the "Manager Training Sites" view. If you click on one of the tabs at the top of your SmartSite navigator, you should now see a site for every user appear.
- Add Sites from File
- The process is almost identical to the one above, except that the first step will prompt you for a file on your local machine.
- The file should be just simple text, saved as a .txt, and should contain a single kerberos id or ucdavis email address per line.
- Delete Selected
- From the "Manage Training Sites" view, just click on the checkbox to the right of the training site you wish to remove, then click "Delete Selected"
- The site(s) should disappear. If you refresh the view at the top of your SmartSite navigator, those tabs should also disappear.
- Add Training Sites
To check if dropbox bug is fixed - BUG FIX!
- Add a user as a participant of either the course or project template site, verify that a dropbox is created in that site for that participant. Then go through the steps above to add a new training site (owned by a different user).
- Check that the new training site includes the dropbox with the name of the user transferred.
- Check that the same user exists under SiteInfo for the training site
| Gallery | ||||
|---|---|---|---|---|
|
| Warning | ||
|---|---|---|
| ||
Added some new functionality as per suggestions made during the demo meeting 10/5.
|
Functional Area: Site Creation Tool for Trainers |
|
|
|
| |||||||||||||||||||
Component Name(s): ucd-training-admin-tool |
|
|
|
| |||||||||||||||||||
|
|
|
|
| |||||||||||||||||||
| # | FDS Trace1 | TS Trace2 | Test Condition | Expected Result | | Comment | Variable 1 | Variable 2 | Variable 3 | Variable 4 | Variable 5 | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
1.0 Functional Verification |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
1.01 |
|
| Add course for a single user by typing kerberos id | Site is created with correct tools & content |
| , and is accessible to user |
|
|
|
|
| ||||||||||||
1.02 |
| Add courses projects for multiple users by typing kerberos ids and email addresses with reduced content | Sites are created with correct tools & content |
|
|
|
| reduced content |
|
| |||||||||||||
1.03 |
| Add course project for a single user by file upload with reduced tool set | Site is created with correct reduced tools & content |
|
|
|
| normal content, and is accessible to user |
|
| |||||||||||||
1.04 |
|
| Add courses for multiple users by file upload with some invalid ids and clicking on ignore for at least one user | Sites are created for all valid, non-ignored users with correct tools & content |
|
|
|
|
|
|
| ||||||||||||
1.05 |
|
| Add project for a single user by typing email address | Site is created with correct tools & content |
|
|
| Delete one or more sites created by tester | Site should be removed in the tool and no longer available to user |
|
|
| |||||||||||
1.06 |
|
| Add projects for multiple users by typing kerberos ids | Sites are created with correct tools & content |
|
|
|
|
|
|
| 1.07 |
|
| Add project for single user by file upload course for a single user by typing kerberos id and unchecked the "Allow trainer access to training sites" checkbox | Site is created with correct tools & content |
|
|
|
|
|
|
|
1.08 |
|
| Add projects for multiple users by file upload | Sites are created with correct tools & content |
|
|
|
|
|
|
| ||||||||||||
1.09 |
|
| Add course using reduced tool set | Site is created with the unchecked tools missing |
|
|
|
|
|
|
| ||||||||||||
1.1 |
|
| Add course using reduced content set | Site is created with the unchecked content missing |
|
|
|
|
|
|
| ||||||||||||
1.2 |
|
| Add site for multiple users, ignoring one or more | Valid users' sites that are not ignored are created |
|
|
|
|
|
|
| ||||||||||||
, and is NOT accessible to trainer, but IS accessible to the user it was created for | |||||||||||||||||||||||
| |||||||||||||||||||||||
2.0 User Interface Element Verification |
|
|
|
|
|
|
|
|
|
| |||||||||||||
2.01 |
|
| Verify abc having: X when Y is true. | The ABC record successfully updates. |
| Verify template list | Only courses and projects accessible to the trainer should be visible |
|
|
|
|
| |||||||||||
2.02 |
| Verify abc having: X when Y is false. | The ABC record successfully updates. Verify training site list | Only courses and projects created by the testers should be visible |
|
|
|
|
|
|
| ||||||||||||
2.03 |
|
| Verify abc having: X when Y is null. | The ABC record returns error: 'You are not allowed to do X when Y is null.' With at least 11 sites in the Manage Sites window, try paging back and forth, delete pages | State should be correctly maintained, listing of which sites are being viewed should be correct |
|
|
|
|
|
|
| |||||||||||
2.04 |
|
| Add TCs for myriad detailed conditions. |
|
|
|
|
|
|
|
| ||||||||||||
2.05 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
2.06 |
|
|
|
|
|
|
| Make extensive use of "Back" and "Next" buttons | State should be maintained, with no unexpected jumps |
|
| ||||||||||||
|
| 2.07 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||
2.08 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
2.09 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
2.1 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3.0 Error Handling-Presentation Layer (i.e. UI) |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3.01 |
|
| Attempt to add site by typing in user with non-existence kerberos id | On 'verify users' screen, no info provided |
|
|
|
|
|
|
| ||||||||||||
3.02 |
|
| Attempt to add site(s) by file upload for users with non-existence UC Davis email addresses | On 'verify users' screen, no info provided for invalid email addresses |
|
|
|
| |||||||||||||||
|
|
| 3.03 |
|
|
|
|
|
|
|
|
|
|
| |||||||||
3.04 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3.05 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3.06 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3.07 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3.08 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3.09 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3.1 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
4.0 Error Handling-Log Verification |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
4.01 |
|
| Verify errors generated from Worksite Setup Training Site Creation tests: catalina.out. |
|
|
|
|
|
|
|
| ||||||||||||
4.02 |
|
| Verify errors generated from Worksite Setup tests: localhost.~.log. |
|
|
|
|
|
|
|
| ||||||||||||
4.03 |
|
| Verify errors generated from Worksite Setup tests: manager.~.log. |
|
|
|
|
|
|
|
| ||||||||||||
4.04 |
|
| Verify errors generated from Worksite Setup tests: host-manager.~.log. |
|
|
|
|
|
|
|
| ||||||||||||
4.05 |
|
| Verify errors generated from Worksite Setup tests: admin.~.log. |
|
|
|
|
|
|
|
| ||||||||||||
4.06 |
|
| Verify error log entry: Process Start Time. | Log entry includes process start time. |
|
|
|
|
|
|
| ||||||||||||
4.07 |
|
| Verify error log entry: Process End Time. | Log entry includes process end time. |
|
|
|
|
|
|
| ||||||||||||
4.08 |
|
| Verify error log entry: Process ID. | Log entry includes process process ID. |
|
|
|
|
|
|
| ||||||||||||
4.09 |
|
| Verify error log entry: Source System Reference. | Log entry includes source code. |
|
|
|
|
|
|
| ||||||||||||
4.1 |
|
| Verify error log entry: Error Record ID. | Log entry includes correct record in error. |
|
|
|
|
|
|
| ||||||||||||
4.11 |
|
| Verify error log entry: Execution User ID. | Log entry includes execution user ID. |
|
|
|
|
|
|
| ||||||||||||
4.12 |
|
| Verify Error 1. | Error 1 gets logged in the XXX file. System allows restart of process. |
|
|
|
|
|
|
| ||||||||||||
4.13 |
|
| Verify Error 2. | Error 2 gets logged in the XXX file. System allows restart of process. |
|
|
| ||||||||||||||||
|
|
|
| 4.14 |
|
| Add TCs for myriad detailed conditions. |
|
|
|
|
|
|
|
| ||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5.0 Database Verification |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5.01 |
|
| Verify table.column when: xxx. |
|
|
|
|
|
|
|
| ||||||||||||
5.02 |
|
| Add TCs for myriad detailed conditions. |
|
|
|
|
|
|
|
| ||||||||||||
5.03 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5.04 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5.05 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5.06 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5.07 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5.08 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5.09 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5.1 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
6.0 Audits & Controls |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
65.01 |
|
| Verify Security: access user. |
|
|
|
|
|
|
|
| ||||||||||||
6.02 |
|
| Verify Security: maintain user. |
|
|
|
|
|
|
|
| ||||||||||||
6.03 |
|
| Verify Timing | Process completes in <= 30 minutes. |
|
|
|
|
|
|
| ||||||||||||
6.04 |
|
| Verify Integration between components: X & Y |
|
|
|
|
|
|
|
| ||||||||||||
6.05 |
|
| Add TCs for myriad detailed conditions. |
|
|
|
|
|
|
|
| ||||||||||||
6.06 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
6.07 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
6.08 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
6.09 | trainer is not able to add sites from the Worksite Setup tool | New button does not appear under Worksite Setup |
|
| |||||||||||||||||||
|
|
|
|
|
|
|
|
| |||||||||||||||
6. | 1
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
7.0 Performance |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
76.01 |
|
| Add TCs for myriad detailed conditions. Verify that submit response time is reasonable at each step |
|
|
| |||||||||||||||||
|
|
|
|
|
| ||||||||||||||||||
7.02 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
7.03 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
7.04 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
7.05 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
7.06 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
7.07 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
7.08 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
7.09 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
7.1 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
REFERENCES: |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
1) Sample Title of Document | FunctionalSpecv1.0.doc; John Smith | 10/22/2004. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||
2) Other sample reference. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3) Other sample reference. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
4) Other sample reference. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
5) Other sample reference. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
FOOTNOTES: |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
1 = Specifies page &/or section number in Functional Design Specification document for test traceability purposes. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
2 = Specifies page &/or section number in Technical Specification document for test traceability purposes. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3 = This is a sample footnote. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
COMMENTS: |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
1) Functional Design Specifications are found in this Confluence location: Location: Dashboard > STTP > Pages > Home > Design Specifications > 2.0; http://bugs.sakaiproject.org/confluence/display/STTP/2.0 |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
2) This is a sample comment. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
3) This is a sample comment. |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
DOCUMENT REVISION HISTORY |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
/
Pass/Fail 1) Created by James Renfro on 10/2/2006. |
|
|
|
|
|
|
|
|
|
| DOCUMENT REVISION HISTORY |
|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
1) Created by James Renfro on 10/2/2006. | |||||||||||
2) Modified by James Renfro on 10/6/2006. |