Test Plan - Site Creation Tool for Trainers

Testing the Site Creation Tool for Trainers

The full story is available on JIRA.

The requirement can be summarized as: "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."

#	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			Verify Worksite Setup for: Course Sites.	Basic Course Site is successfully created.
1.02			Verify Worksite Setup for: Project Sites.	Basic Project Site is successfully created.
1.03			Add TCs for myriad detailed conditions.
1.04
1.05
1.06
1.07
1.08
1.09
1.1

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			Add TCs for myriad detailed conditions.
3.02
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.