Lab III – Prototype Test Plan and Procedure
Dynamic Mapping Solutions
Rodney Blythe
CS 411W, Spring 2010
Janet Brunelle
April 13, 2010
Lab III – DMS Prototype Test Plan and Procedure
Table of Contents
1
2
3
Objectives.................................................................................................................... 3
References .................................................................................................................. 4
Test Plan ...................................................................................................................... 4
3.1
Testing Approach ................................................................................................ 4
3.2
Identification of Tests ......................................................................................... 7
3.3
Test Schedule ...................................................................................................... 8
3.4
Fault Reporting and Data Recording ................................................................... 9
3.5
Resource Requirements .................................................................................... 10
3.6
Test Environment .............................................................................................. 10
4 Test Responsibilites .................................................................................................. 11
5 Test Procedures ........................................................................................................ 12
5.1
DMS Prototype Route-Finding Algorithm ......................................................... 12
5.2
DMS Prototype Database.................................................................................. 13
5.3
DMS Prototype Administrator Interface........................................................... 15
5.4
DMS Prototype User Interface .......................................................................... 22
6 Traceability to Specific Requirements ...................................................................... 24
List of Tables
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
Table 7.
Table 8.
Table 8.
Identification of Tests Table ................................................................................. 7
Test Schedule Table.............................................................................................. 9
Fault Reporting and Data Table............................................................................ 9
Test Responsibilites Table .................................................................................. 12
DMS Prototype Route-Finding Algorithm Test Cases ........................................ 12
DMS Prototype Database Schema and Functionality Test Cases ...................... 13
DMS Prototype Administrative Interface Test Cases ......................................... 16
DMS Prototype User Interface Test Cases ......................................................... 22
DMS Prototype Traceability Matrix.................................................................... 25
List of Figures
Figure 1. DMS Prototype Major Functional Components Diagram ................................... 5
Figure 2. Engineering and Computer Science Building Conference Room Layout .......... 11
2
Lab III – DMS Prototype Test Plan and Procedure
1 Objectives
The Dynamic Mapping Solutions (DMS) prototype provides a simple and affordable
solution to the issues caused by non-dynamic mapping technologies. The DMS mapping
prototype features user friendly control structures and intuitive feature navigation. A ZeroFootprint Model is be used in the DMS prototype; therefore, Administrators and end-users will
be able to access the DMS prototype through an entirely Internet-based JavaScript web
document. The Zero-Footprint Model used by the DMS prototype provides Administrators and
end-users with the ability to access the DMS prototype as quickly as their supported mobile
device can render the DMS prototype. Administrators will have the option to update the DMS
prototype or product nearly anywhere in the world using a supported mobile device.
Updating non-dynamic mapping technologies is often costly, especially if the mapping
technology is based off of a static paper map. The DMS product requires only a very short time
for Administrators to update any editable object on a particular DMS product map. Once an
alteration is submitted by an authorized Administrator, the update is made instantly available
to end-users viewing and interacting with the DMS product User Interface. The final DMS
product provides Administrators with the unique option to Route end-users through only areas
that are thought to be safer for pedestrians. Rather than routing an end-user using the shortest
possible Route, the DMS product can Route an end user around potentially unsafe areas such
as unlit or slippery ice-covered Paths.
The test plan for the DMS prototype will serve as a method by which the Route-Finding
Algorithm, database, Administrator Interface, and User Interface can be tested for efficiency,
security, and functionality. The test cases will serve as a platform to validate and evaluate
3
Lab III – DMS Prototype Test Plan and Procedure
individual portions of the DMS prototype. Each test case procedure will have a set of input
parameters and at least one desired result or output.
2 References
Blythe, RF. (2010, March 21). Dynamic Mapping Solutions Product Description .
Retrieved from
http://cs.odu.edu/~411green/assignments/DMS_ Lab2_Blythe.docx
Blythe, RF. (2010, March 21). Prototype Product Specification. Retrieved from
http://cs.odu.edu/~411green/assignments/DMS_ Lab1_Blythe.docx
Burke, Victoria E. Personal Interview. 21 Oct. 2009.
“Campus Map Options” Survey. 19 Oct. 2009.
Conlin, JC, et al. (2009, December). Digital Mapping Solution. Retrieved from
http://cs.odu.edu/~411green/assignments/finalPresentation.pptx
Conlin, JC, et al. (2009, December 16). Digital Mapping Solution. Retrieved from
http://cs.odu.edu/~411green/assignments/DMS_SBIR_Documentation.docx
Dynamic Mapping Solutions. (2009, December). Retrieved from
http://cs.odu.edu/~411green/index.php
Long, James W. Personal interview. 23 Oct. 2009.
3 Test Plan
The test plans for the DMS prototype are specifically designed to evaluate the
functionality documented in the DMS requirements documentation. A schedule and a detailed
set of testing procedures are included in each of the test plan. Upon completion of the
prototype, all of the test cases must have successful results.
4
Lab III – DMS Prototype Test Plan and Procedure
3.1 Testing Approach
Each of the major functional components developed by the DMS team will be tested
and verified through individual test cases. The major functional components to be test include
the Database, Website, Administrator Interface, Back-end Algorithms, and the User Interface.
Figure 1 – DMS Prototype Major Functional Components Diagram
The Route-Finding Algorithm will be tested and verified using data allocated from
human-controlled computer input interactions with the interactive controls from both the User
Interface and the Administrator Interface. The efficiency of the Route-Finding Algorithm will be
tested using the difference in time between the input and the output of certain key prototype
Route finding operations. Erroneous Administrator Interface or User Interface input data will
be sent to the Route-Finding Algorithm to ensure that the proper error reporting and error
exceptions are employed.
The database functionality of the DMS prototype will be verified using a MySQL prompt
and a set of test queries. Select queries will be verified to ensure that the proper data rows are
5
Lab III – DMS Prototype Test Plan and Procedure
returned. Update queries will be verified to ensure that only the intended data columns within
a particular data row were updated. Insert queries will be verified to ensure that all of the
input data from the Administrator Interface or the User Interface matches the data inserted
into a new row in the database. The database will be additionally tested using data allocated
from human-controlled computer input interactions with the interactive controls from both the
User Interface and the Administrator Interface.
The Administrator Interface and website portal will be tested for functionality as well as
authentication and security. Authentication and security tests will verify the website portal
surrounding the Administrator Interface and will not involve the embedded Administrator
Interface. The Administrator Interface and User Interface within a website portal will be tested
and verified using a separate set of test cases designed to ensure that the graphical elements of
the both interfaces are displayed and updated as the requirements documentation requires.
[This space is intentionally left blank]
6
Lab III – DMS Prototype Test Plan and Procedure
7
3.2 Identification of Tests
The DMS prototype is tested and verified using four categories of testing and evaluation.
As can be seen in Table 1, the categories are divided into a series of individual tests, each with a
summary of the test to be performed. All of the test cases provide a set of detailed test
implementation instructions as well as a set of expected results for verification.
Category
Description
Test
Case
1.1.1
1.1.2
1.1.3
1.1.4
1
Route-Finding
Algorithm
1.2.1
1.2.2
1.3.1
Description
Select a valid start and end location. Run the route-finding
algorithm and verify a route is properly built.
Select a valid start location and do not select an end
location. Try to run the route-finding algorithm and verify
that an error is displayed to the user.
Do not select a start location and select a valid end location.
Try to run the route-finding algorithm and verify that an
error is displayed to the user.
Select neither a start location nor an end location. Try to run
the route-finding algorithm and verify that an error is
displayed to the user.
Select a valid start and end location with a relatively small
distance between them. Generate a path and verify that
the algorithm does not take more than 10 seconds to run.
Select a valid start and end location with a relatively large
distance between them. Generate a path and verify that
the algorithm does not take more than 10 seconds to run.
Select a valid start and end location which has a path
running through an overlay.
Run the algorithm with the overlay turned off and verify the
route is built using the node in the overlay.
Run the algorithm with the overlay turned on and verify an
alternate route is built around the node in the overlay.
[This space is intentionally left blank]
Lab III – DMS Prototype Test Plan and Procedure
Category
2
Description
Database
Test
Case
3
4
User Interface
Description
2.1
Database module authenticates and connects
2.2
3.1
Select Queries return an ArrayList of the desired type which
includes all items requested by the SQL Statement
Add Queries add object to database and do not affect other
items. All IDs auto increment
Update queries update given object and do not affect other
objects in database
Verify Authentication
3.2
Verify Test Mode
3.3
Verify Node Tool
3.4
Verify Path Tool
3.5
Verify Structure Tool
3.6
Verify Overlay Tool
4.1
Load End User Interface/Test Mode
4.2
Node Selection Functionality
4.3
Route Generation Functionality
4.4
Clear Path Functionality
4.5
Clear Map Functionality
4.6
Structure Information Functionality
4.7
Search Functionality
2.3
2.4
Administrator
Interface
8
Table 1 – Identification of Tests Table
3.3 Test Schedule
The DMS team is allotted one hour with which to present the capabilities and
functionality of the DMS prototype. The first fifteen minutes of the demonstration will be used
to introduce the DMS solution and to initially set up of the DMS prototype. Following this
introduction and setup period, the DMS prototype will be displayed on two projection screens.
A single minute will be required in order to log into the Administrator Interface of the DMS
prototype. Once logged in, twenty minutes will be needed in order to demonstrate the
capabilities and functionality of the Design Mode of the Administrator Interface. Two minutes
Lab III – DMS Prototype Test Plan and Procedure
9
will be necessary in order to present the Overlay Mode of the Administrator Interface. The final
fifteen minutes will be used to demonstrate the capabilities and functionality of the User
Interface.
Start Time
Duration
Description
Test Case
0:15
0:01
Login To Administrator Interface
3.1
0:16
0:20
Design Mode
3.3, 3.4, 3.5, 2.1-2.4
0:36
0:02
Overlay Mode
3.6
0:38
0:15
User Interface
1.1-1.3,2.1-2.4,4.1-4.7
Table 2 – Test Schedule Table
3.4 Fault Reporting and Data Recording
Both failed and verified tests will be recorded by the DMS team throughout the testing
process of the DMS prototype. An individual member of the DMS team is responsible for
testing a single component of the DMS prototype. A DMS team member cannot test and
evaluate a portion of the DMS prototype that was developed primarily by that team member.
The test components and recording process of each individual DMS prototype component can
be found in Table 3.
Component
Route-Finding Algorithm
Database Schema and
Functionality
Administrator Interface
User Interface
Process of Recording
Report failures through interactions with the Administrator and User Interfaces
Document using both soft and hard copy formats
Report failures through a visual inspection of the results of SQL queries
Document using both soft and hard copy formats
Report failures through a visual inspection of interface and website portal interactions
Document using both soft and hard copy formats
Report failures through a visual inspection of interface interactions
Document using both soft and hard copy formats
Table 3 – Fault Reporting and Data Recording Table
[This space is intentionally left blank]
Lab III – DMS Prototype Test Plan and Procedure
3.5 Resource Requirements
The DMS team requires three Internet-connected computers for demonstrational
purposes. Two of the computer must display separate content on two separate projectors. The
DMS prototype web portal and the embedded User and Administrator Interfaces will be
displayed on these two projectors. The third computer must display test data from the DMS
prototype MySQL database.
3.6 Test Environment
A conference room located in the Engineering and Computer Science building on the Old
Dominion University campus will serve as the demonstrational platform for the DMS prototype
presentation. Three of the four laptops located in the conference room will be required by the
DMS team. One of the laptops will display the User Interface on Projector Screen 1. A second
laptop will display the Administrator Interface on Projector Screen 2. The third laptop will
display the contents of the DMS prototype database on TV 2.
[This space is intentionally left blank]
10
Lab III – DMS Prototype Test Plan and Procedure
Figure 2 – Engineering and Computer Science Building Conference Room Layout
4 Test Procedures
Each member of the DMS team will have a separate responsibility for the DMS
prototype presentation. Joseph Conlin will introduce the DMS solution and discuss the
feasibility of the DMS product. Brittany Cunningham will demonstrate the capabilities and
functionality of the User Interface. Sean Christe will demonstrate the capabilities and
functionality of the Administrator Interface. Ian Iepson will demonstrate the database
interactions of the DMS prototype. Brandon Smith will take detailed notes and record any
useful information acquired from the presentation. Rodney Blythe will record all test results
and extrapolate any necessary information discovered during the presentation.
[This space is intentionally left blank]
11
Lab III – DMS Prototype Test Plan and Procedure
Team Member
Joseph Conlin
Brittany Cunningham
Sean Christe
Ian Iepson
Brandon Smith
Rodney Blythe
12
Responsibilities
Introduction and Feasibility
User Interface
Administrator Interface
Database
Notes
Record test results
Table 4 – Test Responsibilities Table
5 Test Procedures
The testing procedures detailed in Section 5 are each designed to test and evaluate the
required capabilities and functionality of the DMS prototype. The individual test cases are
divided into the four major functional component categories of the DMS prototype. These
categories include the Route-Finding Algorithm, the database schema and functionality, the
Administrator Interface, and the User Interface.
5.1 DMS Prototype Route-Finding Algorithm
The DMS prototype Route-Finding Algorithm is responsible for the back-end data
manipulation functionality of the DMS product. Therefore, the Route-Finding Algorithm must
be tested to ensure that data is input and output both efficiently and correctly. The following
are the individual test cases for the Route-Finding Algorithm of the DMS prototype:
Description: Route-Finding Algorithm Test with Error Message
Purpose: Verify correct route and error message
Setup Conditions: DMS Admin Interface open
Test Case Activity
Pass/Fail Comments Expected Result
1
Select a valid start and end location.
Route is properly built.
Run the route-finding algorithm.
Test Category ID: 1
Test Case: 1.1
2
3
Select a valid start location and do
not select an end location. Try to
run the route-finding algorithm.
Do not select a start location and
select a valid end location. Try to
Error message is
displayed to the user.
Error message is
displayed to the user.
Lab III – DMS Prototype Test Plan and Procedure
4
run the route-finding algorithm.
Select neither a start location nor an
end location. Try to run the routefinding algorithm.
13
Error message is
displayed to the user.
Description: Route-Finding Algorithm Run Time Test
Purpose: Test Route-Finding Algorithm speed
Setup Conditions: DMS Admin Interface open
Test Case Activity
Pass/Fail Comments Expected Result
1
Select a valid start and end location
Route-finding algorithm
with a relatively small distance
completes and displays a
between them. Generate a path
path within 10 seconds.
2
Select a valid start and end location
Route-finding algorithm
with a relatively large distance
completes and displays a
between them. Generate a path
path within 10 seconds.
Test Category ID: 1
Test Case: 1.2
Description: Route finding Algorithm with Overlay
Purpose: Verify Overlays working correctly
Setup Conditions: DMS Admin Interface open
Test Case Activity
Pass/Fail Comments
1
Select a valid start and end location
which has a path running through an
overlay. Run the algorithm with the
overlay turned off and verify the
route is built using the node in the
overlay. Run the algorithm with the
overlay turned on.
Test Category ID: 1
Test Case: 1.3
Expected Result
The route-finding
algorithm must use an
alternate route,
demonstrating that the
path is affected by the
active overlay.
Table 5 – DMS Prototype Route-Finding Algorithm Test Cases
5.2 DMS Prototype Database
The DMS prototype database is responsible for storing, organizing, and providing ready
access to a majority of the data utilized by the DMS prototype. Therefore, the database must be
capable of efficiently and correctly interfacing with the DMS product. The following are the
individual test cases for the database of the DMS prototype:
[This space is intentionally left blank]
Lab III – DMS Prototype Test Plan and Procedure
Description: Database
Purpose: Database Module Authenticates and Connects
Setup Conditions: Database credentials
Test Case Activity
Pass/Fail Comments Expected Result
1
Connect
Java database connection
is initialized and does not
throw connection error
2
Simple Queries can be run
Simple SQL Queries can
be run with expected
results
Test Category ID: 2
Test Case: 2.2
Description: Database
Purpose: Select Queries Return and ArrayList of the desired type which
includes all items returned by the SQL Statement
Setup Conditions: Database connection and SQL Select Queries
Test Case Activity
Pass/Fail Comments Expected Result
1
Select all nodes with the following
ArrayList<Node>
SQL command:
containing all nodes in
SELECT *
the DMS database
FROM Node;
2
Select all paths with the following
ArrayList<Path>
SQL Command:
containing all nodes in
SELECT *
the DMS database
FROM Path;
3
Select all Structures with the
ArrayList<Srtructure>
following SQL Command:
containing all nodes in
SELECT *
the DMS database
FROM Structure
Test Category ID:2
Test Case: 2.2
[This space is intentionally left blank]
14
Lab III – DMS Prototype Test Plan and Procedure
Description: Database
Purpose: Entries can be added to database without affecting other entries
Setup Conditions: Database connection and data to be entered
Test Case Activity
Pass/Fail Comments Expected Result
1
Insert a node with the following SQL
Node is added to
Command:
database and all
INSERT INTO Node
other data is
(longitude,latitude,weight)
unaffected
VALUES(54.231,34.234,5);
2
Insert a path with the following SQL
Path is added to
Command:
database and all
INSERT INTO Path
other data is
(node1ID, node2ID, weight)
unaffected
VALUES(3,4,5);
3
Add Structure with the following SQL
Structure is added to
Command:
database and all
INSERT INTO Structure
other data is
(name,longitude,latitude)
unaffected
VALUES("Spong",45.241,35.321);
Test Category ID: 2
Test Case: 2.2
Description: Database
Purpose: Entries can be updated without affecting other entries
Setup Conditions: Database credentials
Test Case Activity
Pass/Fail Comments Expected Result
1
Update a node's location with the following
Node 1 location now
SQL Statement:
reads 25.134,45.243
UPDATE Node
and all other nodes are
SET longitude=25.134,
unaffected
latitude=45.243
WHERE nodeID = 1
2
Update
Structure description
UPDATE Structure
reads "CS Main
SET description="CS Main Office"
Office" and all other
WHERE structureID = 1;
structures are unaltered
Test Category ID: 2
Test Case: 2.2
Table 6 – DMS Prototype Database Schema and Functionality Test Cases
5.3 DMS Prototype Administrator Interface
The DMS prototype Administrator Interface is responsible for all Administrator-based
interactions with the DMS prototype. Therefore, the Administrator Interface must be capable
of efficiently, securely, and correctly interfacing with an Administrator. The following are the
individual test cases for the Administrator Interface of the DMS prototype:
15
Lab III – DMS Prototype Test Plan and Procedure
Description: Admin Interface
Purpose: Verify Authentication
Setup Conditions: Administrative user credentials are statically coded in the in
the log in page source code.
Test Case Activity
Pass/Fail Comments Expected Result
1
Visually verify that a username and
All fields are displayed
a password field, as well as a “log
in” button, is displayed on the log in
page.
2
Leave the username field blank and
Redirect to log in page.
type “test” into the password field.
Display error message
Submit the log in form.
stating, “Username field
was left blank”
3
Leave the password field blank and
Redirect to log in page.
type “test” into the username field.
Display error message
Submit the log in form.
stating, “Password field
was left blank.”
4
Leave the both the username and
Redirect to log in page.
password fields blank. Submit the
Display error message
log in form.
stating, “Username and
Password fields were left
blank.”
5
Type “invalid” into both the
Redirect to log in page.
username and password fields.
Display error message
Submit the log in form.
stating, “Invalid
Username or Password.”
6
Type “admin” into the username
Redirect to the default
field and “password” into the
homepage.
password field. Submit the log in
form.
7
Click the log out link on the default
Redirect to the log in
prototype homepage.
page.
8
After logging out of the prototype,
Redirect to the log in
select the “login.php” portion of the
page.
URL address and replace it with
“index.php”. Navigate to the
address.
Test Category ID: 3
Test Case: 3.1
[This space is intentionally left blank]
16
Lab III – DMS Prototype Test Plan and Procedure
Description: Admin Interface
Purpose: Verify Test Mode
Setup Conditions: Administrative user has navigated to the default prototype
page.
Test Case Activity
Pass/Fail Comments Expected Result
1
Visually verify that a “Test Mode”
Test Mode button is
button is displayed.
displayed.
2
Click on the “Test Mode” button.
A new browser window is
displayed containing the
User Interface prototype.
Test Category ID: 3
Test Case: 3.2
[This space is intentionally left blank]
17
Lab III – DMS Prototype Test Plan and Procedure
Description: Admin Interface
Purpose: Verify Node Tool
Setup Conditions: Administrative user has navigated to the Design Mode
interface.
Test Case Activity
Pass/Fail Comments Expected Result
1
Visually verify that a Node Tool
A Node Tool button is
button exists.
displayed.
2
Click the Node Tool button. Click
A blue pushpin Node icon
on the interactive map.
is displayed at the mouseclick location on the
interactive map. A row is
added to the Node table
in the database containing
a uniquely incremented
ID number, a latitude
value, a longitude value,
and a weight value.
3
Visually verify that a Select Tool
A Select Tool button is
button exists.
displayed.
4
Click on the Select Tool button.
A dialogue box is
Click on a Node on the interactive
displayed.
map.
5
Click the “delete node” button.
The selected Node icon is
removed from the
interactive map. The
database row containing
the data for the selected
Node is removed from the
Node table.
6
Click on the Select Tool button.
The selected Node icon is
Click on a Node icon on the
relocated to the dragged
interactive map and drag the node to
mouse location on the
another location within the
interactive map. The row
interactive map.
containing the data for the
relocated Node is updated
to reflect the new latitude
and longitude values.
Test Category ID: 3
Test Case: 3.3
[This space is intentionally left blank]
18
Lab III – DMS Prototype Test Plan and Procedure
Description: Admin Interface
Purpose: Verify Path Tool
Setup Conditions: Administrative user has navigated to the Design Mode
interface.
Test Case Activity
Pass/Fail Comments Expected Result
1
Visually verify that a Path Tool
A Path Tool button is
button exists.
displayed.
2
Click the Path Tool button. Click
A blue line is displayed
on a Node icon and then click on a
between the two selected
second Node icon.
Node icons. A row is
added to the Path table in
the database containing a
uniquely incremented ID
number, an ID number
for both selected Nodes,
and a combined weight
for the selected Nodes.
3
Visually verify that a Select Tool
A Select Tool button is
button exists.
displayed.
4
Click on the Select Tool button.
A dialogue box is
Click on a Path line on the
displayed.
interactive map.
5
Click the “delete path” button.
The selected Path line is
removed from the
interactive map. The
database row containing
the data for the selected
Path is removed from the
Path table.
Test Category ID: 3
Test Case: 3.4
[This space is intentionally left blank]
19
Lab III – DMS Prototype Test Plan and Procedure
Description: Admin Interface
Purpose: Verify Structure Tool
Setup Conditions: Administrative user has navigated to the Design Mode
interface.
Test Case Activity
Pass/Fail Comments Expected Result
1
Visually verify that a Structure Tool
A Structure Tool button is
button exists.
displayed.
2
Click the Structure Tool button.
A red pushpin Structure
Click on the interactive map.
icon is displayed at the
mouse-click location on
the interactive map. A
dialogue box is displayed.
3
Input “Test Building” into the name
The dialogue box
field and “Jane Doe – 302 Test
disappears. A row is
Building” in the description field.
added to the Structures
Click the “insert structure” button.
database table containing
a uniquely incremented
ID number, a name with a
value of “Test Building”,
a description with a value
of “Jane Doe – 302 Test
Building”, a longitude
value, and a latitude
value.
4
Visually verify that a Select Tool
A Select Tool button is
button exists.
displayed.
5
Click on the Select Tool button.
A dialogue box is
Click on a Structure icon on the
displayed.
interactive map.
6
Click the “delete structure” button.
The selected Structure
icon is removed from the
interactive map. The
database row containing
the data for the selected
Structure is removed
from the Structure table.
Test Category ID: 3
Test Case: 3.5
[This space is intentionally left blank]
20
Lab III – DMS Prototype Test Plan and Procedure
Description: Admin Interface
Purpose: Verify Structure Content Manipulation Functionality
Setup Conditions: Administrative user has navigated to the Design Mode
interface and clicked on a Structure icon on the interactive map displaying a
dialogue box.
Test Case Activity
Pass/Fail Comments Expected Result
1
Visually verify that a list of
A list of Structure
Structure is displayed.
contents is displayed.
2
Visually verify that a “delete
A “delete structure”
structure” button is displayed.
button is displayed.
3
Visually verify that a form
All form fields are
containing a text area for Structure
displayed.
contents and an “update contents”
button is displayed.
4
Input “John B. Smith – 1104 Test
The database row
Building” into the Structure
containing the Structure
contents text area. Click the
description data for the
“update contents” button.
selected Structure is
updated to contain “John
B. Smith – 1104 Test
Building”. The Structure
contents list in the
dialogue box displays
“John B. Smith – 1104
Test Building”.
Test Category ID: 3
Test Case: 3.6
Description: Admin Interface
Purpose: Verify Overlay Tool
Setup Conditions: Administrative user has navigated to the Design Mode
interface.
Test Case Activity
Pass/Fail Comments Expected Result
1
Visually verify that a series of
Overlay buttons are
Overlay buttons are displayed.
displayed.
2
Click on the “on” button next to a
The weight increase
particular Overlay.
specified by the Overlay
is added to the weight
values in the database for
each Path affected by the
Overlay.
3
Click the “off” button next to an
The weight increase
Overlay that is currently “on”.
specified by the Overlay
is subtracted from the
weight values in the
database for each Path
affected by the Overlay.
Test Category ID: 3
Test Case: 3.5
Table 7 – DMS Prototype Administrative Interface Test Cases
21
Lab III – DMS Prototype Test Plan and Procedure
5.4 DMS Prototype User Interface
The DMS prototype User Interface is responsible for all end-user-based interactions with
the DMS prototype. Therefore, the User Interface must be capable of efficiently and correctly
interfacing with an end user. The following are the individual test cases for the User Interface
of the DMS prototype:
Test Category ID: 4
Description: Load End User Interface/Test Mode
Test Case: 4.1
Purpose: Demonstrates that correct interface elements load
Specification:
Page elements load appropriately
3.1.4.2.1
Test Level:
System
Test Type:
Functional
Setup Conditions:
None
Test Case Activity
Pass/Fail Expected Result
1
Load website <URL>
Static Map loads
2
Load website <URL>
Search Box loads
3
Load website <URL>
Information Box loads
Test Category ID: 4
Test Case: 4.2
Description: Node Selection Functionality
Purpose: Demonstrates that Nodes are selectable and can be added
to the requested Route.
Node selection
Specification:
3.1.4.2.2
Test Level:
System
Test Type:
Functional
Setup Conditions:
Test 4.1 is completed successfully
Test Case Activity
Pass/Fail Expected Result
1
Single-click a point on the map
Nearby Nodes become visible for
selection
2
Double-click a visible Node
Node is added to the Route
3
Single-click a point on the map
Nearby Nodes become visible for
selection
4
Double-click a visible Node
Node is added to the Route
5
Single-click a point on the map
Nearby Nodes become visible for
selection
6
Double-click a visible Node
Nothing happens
[This space is intentionally left blank]
22
Lab III – DMS Prototype Test Plan and Procedure
Test Category ID: 4
Test Case: 4.3
Description: Route Generation Functionality
Purpose: Demonstrates that a valid Route is returned after Nodes are
selected
Call Route-Finding Algorithm
Specification:
3.1.4.2.3
Specification:
Display returned Route
3.1.4.2.4
Test Level:
System
Test Type:
Functional
Setup Conditions:
Test 4.2 is completed successfully
Test Case Activity
Pass/Fail Expected Result
1
Click on the button to start the
Route is displayed
Route-Finding Algorithm
Test Category ID: 4
Description: Clear Path Functionality
Test Case: 4.4
Purpose: Demonstrates that a Route can be cleared after generation
Specification:
Clear Path button
3.1.4.2.2
Test Level:
System
Test Type:
Functional
Setup Conditions:
Test 4.3 is completed successfully
Test Case Activity
Pass/Fail Expected Result
1
Click the Clear Path button
Generated Route and associated
Nodes are cleared
Test Category ID: 4
Description: Clear Map Functionality
Test Case: 4.5
Purpose: Demonstrates that the entire map can be cleared
Specification:
Clear Map button
3.1.4.2.2
Test Level:
System
Test Type:
Functional
Setup Conditions:
None
Test Case Activity
Pass/Fail Expected Result
1
Single-click a point on the map
Nearby Nodes become visible for
selection
2
Single-click a point on the map
Nearby Nodes become visible for
selection and previous Nodes remain
3
Single-click a point on the map
Nearby Nodes become visible for
selection and previous Nodes remain
4
Click the Clear Map button
All Nodes and Paths on the map are
cleared
[This space is intentionally left blank]
23
Lab III – DMS Prototype Test Plan and Procedure
Test Category ID: 4
Test Case: 4.6
Description: Structure Information Functionality
Purpose: Structure information of a Node is appropriately displayed on
mouse-over
Specification:
Dialogue box displayed on mouse-over, to include building name and
3.1.4.2.1
information
Test Level:
System
Test Type:
Functional
Setup Conditions:
None
Test Case Activity
Pass/Fail Expected Result
1
Single-click a building on the
Nearby Nodes become visible for
map
selection
2
Hover mouse over a visible
Building name and information is
Node
displayed
Test Category ID: 4
Description: Search Function Functionality
Test Case: 4.7
Purpose: Demonstrates that the Search Function returns valid results
Specification:
Search function
3.1.4.2.2
Test Level:
System
Test Type:
Functional
Setup Conditions:
Test 4.2, 4.3 are completed successfully
Test Case Activity
Pass/Fail Expected Result
1
Type “Visual Arts Building” in the
Visual Arts Building is displayed
Search Box
2
Double-click on the visible Node
Node is added to the Route
3
Type “Student Health Services”
Webb Center is displayed
in the Search Box
4
Double-click on the visible Node
Node is added to the Route
5
Click on the button to start the
Route is displayed
Route-Finding Algorithm
Table 8 – DMS Prototype User Interface Test Cases
6 Traceability to Specific Requirements
The relationships between the functional requirements and the test cases for the DMS
prototype can be found in the traceability matrix in Table 7 on page. The specific test cases for
each required set of functionality detailed in the functional requirements documentation can
found by cross referencing a specific component with an associated test case.
24
Lab III – DMS Prototype Test Plan and Procedure
Table 9 – DMS Prototype Traceability Matrix
25