Test Plan - Site Creation Tool for Trainers

DRAFT

Testing the Site Creation Tool for Trainers

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

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.

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.

Like any test, even though the functionality is simple, there are dozens of variations that could impact whether the tool works. Creating a new site from template is a 4-step process

#	FDS Trace1	TS Trace2	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
1.02			Add courses for multiple users by typing kerberos ids and email addresses	Sites are created with correct tools & content
1.03			Add course for a single user by file upload	Site is created with correct tools & content
1.04			Add courses for multiple users by file upload	Sites are created with correct tools & content
1.05			Add project for a single user by typing email address	Site is created with correct tools & content
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	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
2.0 User Interface Element Verification
2.01			Verify abc having: X when Y is true.	The ABC record successfully updates.
2.02			Verify abc having: X when Y is false.	The ABC record successfully updates.
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.'
2.04			Add TCs for myriad detailed conditions.
2.05
2.06
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 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
6.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
6.1

7.0 Performance
7.01			Add TCs for myriad detailed conditions.
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

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