Running Head: Lab 3 – Prototype Test Plan/Procedure Outline
CS 411W Lab III
Prototype Test Plan/Procedure Outline
For
TRAIN
Prepared by: Drew, Green Team
Date: 04/17/2013
Version: 1
Lab III - Prototype Test Plan/Procedure Outline
2
Table of Contents
Contents
Lab III - Prototype Test Plan/Procedure Outline ...............Error! Bookmark not defined.
1
Objectives .................................................................................................................... 3
2
References ................................................................................................................... 3
3
Test Plan ...................................................................................................................... 4
3.1
Testing Approach ................................................................................................. 4
3.2 Identification of Tests - high level list of individual tests and objective of each
test – this can be in bullet or tabular form (Note: A Test Case will be prepared for each
test identified here) ......................................................................................................... 5
3.3 Test Schedule- a schedule indicating the sequence of tests and time allotted for
each including preparation ............................................................................................ 10
3.4 Fault Reporting and Data Recording - a description of how test results will be
recorded, including any specific values to record and how faults or test failures will be
documented ................................................................................................................... 11
3.5
Resource Requirements ...................................................................................... 12
3.6
Test Environment ............................................................................................... 12
List of Figures
Figure 1: TRAIN Prototype Architecture Diagram. ........................................................... 4
List of Tables
Table 1: List of tests .......................................................................................................... 10
Table 2: Testing schedule ................................................................................................. 10
Table 3: Data recording procedures .................................................................................. 11
Lab III - Prototype Test Plan/Procedure Outline
3
1 Objectives
This test plan will detail how to demonstrate successful operation of TRAIN by
establishing an approach, sequence, and list of tests to be conducted. TRAIN
provides a central repository of Topics that can be searched and combined into
Courses. These procedures are to verify the stable and correct operation of the
application.
2 References
Lab 1 – TRAIN Prototype Descriptive Paper. Version 2. (2013, April). Training Resource
and Information Network. Green Team. CS411W: Drew Carpenter.
Lab 2 – TRAIN Product Specification Outline. Version 1. (2013, April). Training
Resource and Information Network. Green Team. CS411W: Drew Carpenter.
Lab III - Prototype Test Plan/Procedure Outline
4
3 Test Plan
3.1 Testing Approach
The correctness of TRAIN will be verified by major functional area then with
integration tests. The functional areas are illustrated in Figure. Correctness will be
verified through the following types of tests:
 User Interface tests to verify the Admin, Instructor, Customer and Student
pages are intuitive, repeatable and meet the requirements.
 Database and Algorithm test to verify the data is stored and searched
Figure 1: TRAIN Prototype Architecture Diagram.
according to the specifications.
All tests will be performed at a terminal with access to a server running an
installation of TRAIN. Data will be loaded into the database prior to testing.
Verification of all tests will be completed visually through the application interface
and through a direct connection to the database.
Lab III - Prototype Test Plan/Procedure Outline
5
3.2 Identification of Tests
The following tests will be done:
Category
ID
Description
Test
Case
Description
Objective
1.1
User Creation
Verify Creation of
each type of User
and User
capabilities
1.2
Organization
Creation
Demonstrate admin
ability to create
organization
1.3
1.4
User Edit
Demonstrate
Admin ability to
edit user
information
Organization
Edit
Demonstrate
Admin ability to
edit Organization
information
Data Upload
Show the Admins
data upload
functionality
Data Edit
Demonstrate
Admin ability to
edit data
information
Data Update
Demonstrate
Admin ability to
update files
attached to data
Data
Download
Verify Admin
ability to download
files attached to
data
1
Admin Interface
1.5
1.6
1.7
1.8
Lab III - Prototype Test Plan/Procedure Outline
Category
ID
Description
Test
Case
Description
Objective
Customer
Request
Confirm customer
request, and show
course approval
1.10
Course
Creation
Verify course
generation
algorithm,
demonstrate Admin
ability to create
course
1.11
Course
Finalization
Verify course
creation
2.1
Instructor
Customer
Request
Confirms
Instructors
assignment to an
organization
Edit
Organizations
Confirm
functionality when
editing
organizations.
3.2
Create Student
User
Confirm
functionality of
creating a student
user.
3.3
Request
Training
Confirm
functionality of
requesting training.
3.4
Finalize
Course
Request
Confirm
functionality of
finalizing course
request.
1.9
2
Instructor Interface
3.1
3
6
Manager Interface
Lab III - Prototype Test Plan/Procedure Outline
Category
ID
Description
Test
Case
Description
Objective
3.5
View Course
Request
History
Confirm
functionality of
viewing course
request history.
3.6
Edited
Students
Assigned to a
Course
Confirm
functionality when
editing students
assigned to a
course.
Course Open
Feedback
Confirm
functionality when
giving course open
text feedback.
View Course
Confirm
functionality of
viewing a course
4.2
Course
Feedback
Confirm
functionality when
giving open text
course feedback.
5.1
Login Screen
Demonstrate valid
login screen
5.2
Username and
password
Authentication
Demonstrate the
authentication
credentials required
to login.
User Access
Denial
Demonstrate denial
of access with
incorrect
credentials.
3.7
4.1
4
5
7
Student Interface
Authentication and
Access
5.3
Lab III - Prototype Test Plan/Procedure Outline
Category
ID
Description
Test
Case
Description
Objective
Redirection for
Authorized
User
Redirection to
appropriate page
for authorized user.
Header
Demonstrate each
user uses same
header.
6.2
Menu
Demonstrate each
user uses same
menu
6.3
User Specific
Menu Items
Demonstrate menu
items are limited
by user.
Menu Link
Redirection
Demonstrate menu
links redirect user
to appropriate
page.
7.1
Topic Search
Demonstrate
locating topics by
learning objectives
7.2
Learning
Objective
Search
Verify that learning
objectives can be
used to search for
topics
Filtering
Demonstrate that
searching by
keywords filters
through tags to
match learning
objectives
5.4
6.1
6
Template
6.4
7
8
Algorithm
7.3
Lab III - Prototype Test Plan/Procedure Outline
Category
ID
Description
Test
Case
Description
Objective
User Table
Verify the table has
been created
properly
8.2
Role Table
Verify the table has
been created
properly
8.3
Organization
Table
8.1
8.4
Topic Table
Verify the table has
been created
properly
Verify the table has
been created
properly
Course Table
Verify the table has
been created
properly
8.6
Course Session
Verify the table has
been created
properly
8.7
Learning
Objective
Table
Verify the table has
been created
properly
Reference
Table
Verify the table has
been created
properly
Tag Table
Verify the table has
been created
properly
File Table
Verify the table has
been created
properly
8.5
8
9
Database
8.8
8.9
8.10
Lab III - Prototype Test Plan/Procedure Outline
Category
ID
Description
Test
Case
10
Description
Objective
Course
Feedback
Table
Verify the table has
been created
properly
8.12
Role Table
Populated
Verify the role
table contains all
the roles
8.13
Organization
data exists
Verify the default
organization exists
8.13
User data
exists
Verify the default
user exists
8.14
Login with
Default user
8.11
Verify you can
login with the
default user
Table 1: List of tests
3.3 Test Schedule
Testing will follow this schedule:
Start Time
(minutes)
0:00
0:5
0:15
Duration (minutes)
Description
5
10
20
0:35
10
Introduction
Database Demo
Interface Demo
-Admin
-Manager
-Instructor
-Student
Functionality
Demo
0:45
15
Table 2: Testing schedule
Q&A
Test Cases
Covered
8.1-8.14
1.0,6.4
4.1 – 4.7
Lab III - Prototype Test Plan/Procedure Outline
11
3.4 Fault Reporting and Data Recording
Data recording will be done with the following methods:
Component
Recording Process
Database
-
Report failures through visual inspection of
database records using LINQPad
Administrator interface
-
Document through paper forms
-
Report failures through visual inspection of
output and data saved in database
Instructor interface
-
Document through paper forms
-
Report failures through visual inspection of
output and data saved in database
Manager interface
-
Document through paper forms
-
Report failures through visual inspection of
output and data saved in database
Student interface
-
Document through paper forms
-
Report failures through visual inspection of
output and data saved in database
Algorithms
-
Document through paper forms
-
Report failures through visual inspection of
functional outcome
Table 3: Data recording procedures
Document through paper forms
Lab III - Prototype Test Plan/Procedure Outline
12
3.5 Resource Requirements







The following resources are needed to setup and run the tests:
A sever running SQL Server 2012 and TRAIN
A computer with SQL Server Management Studio 2012
A computer with the latest version of Chrome or Firefox
A network connection between the server and two computers
Mock data pre-populated in TRAIN
o Several Learning Objectives, Tags, Topics, and References
o Two organizations with two users each
 One with a Student and a Customer
 One with an Administrator and an Instructor
A copy of the test plan
A copy of the user manual
3.6 Test Environment
The test environment will have two computers connected to a single server. An
installation of TRAIN will reside on the server with some mock data already in the
database. One computer will use a web browser to interact with TRAIN. The other
computer will have an instance of SQL Server Management Studio open to monitor
changes to the train database.