Test Plan - Site Creation Tool for Trainers

Testing the Site Creation Tool for Trainers

DRAFT

The user story here can be summarized as follows:

"We need a tool that will allow a number of workshop sites to be created based on a list of attendees for a training workshop--and a way for the workshop instructor to just enter names in a form that will run a site creation job in order to handle last minute appearances by people wanting to take the class."

JIRA Ticket(s) relating to this story:

SAK-129

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
- Copy realm !site.template.course to !site.template.training-course
- Copy realm !site.template.project to !site.template.training-project
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

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.

Some key understandings

Creating a new site from template is a 4-step process.
There are two paths to giving the app its list of kerberos ids/email addresses – one is by typing them in by hand, the other using a flat text file.
If a given kerberos id or ucdavis email address is not correct, then that record will be ignored
Although a copy of the template site is made for each user's training site, still it's possible, in steps 3 and 4, to prevent specific tools or content from being copied into the new training site by unchecking a box to the right of the specific tool name under the appropriate screen.

	# Test Condition	Expected Result
Functional Area: Site Creation Tool for Trainers
Component Name(s): ucd-training-admin-tool


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 projects for multiple users by typing kerberos ids and email addresses with reduced content	Sites are created with correct tools & reduced content
1.03	Add project for a single user by file upload with reduced tool set	Site is created with reduced tools & 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	Delete one or more sites created by tester	Site should be removed in the tool and no longer available to user
2.0 User Interface Element Verification
2.01	Verify template list	Only courses and projects accessible to the trainer should be visible
2.02	Verify training site list	Only courses and projects created by the testers should be visible

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

4.0 Error Handling-Log Verification
4.01	Verify errors generated from Training Site Creation tests: catalina.out.

6.0 Audits & Controls
6.01	Verify Security: trainer is not able to add sites from the Worksite Setup tool	New button does not appear under Worksite Setup

7.0 Performance
7.01	Verify that submit response time is reasonable at each step


REFERENCES:

1) Title of Document	document name; author	date

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.

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

DOCUMENT REVISION HISTORY

1) Created by James Renfro on 10/2/2006.