Running Head: LAB III – PROTOTYPE TEST CASE AND PROCEDURE
Lab III – Prototype Test Case and Procedure
Marrissa A. Webster
Professor Janet Brunelle
April 18, 2011
Version One
1
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
2
Table of Contents
1. OBJECTIVE ................................................................................................................................3
2. REFERENCES ............................................................................................................................4
3. TEST PLAN.................................................................................................................................4
3.1. Testing Approach ..................................................................................................................4
3.2. Identification of Tests ...........................................................................................................6
3.3. Test Schedule ........................................................................................................................8
3.4. Fault Reporting and Data Recording ....................................................................................9
3.5. Resource Requirements ........................................................................................................9
3.6. Test Environment ................................................................................................................10
4. TEST RESPONSIBILITIES ......................................................................................................10
5. TEST PROCEDURES ...............................................................................................................10
6. TRACEABILITY TO REQUIREMENTS ................................................................................11
List of Figures
Figure 1. GAS Prototype Major Functional Component Diagram..................................................5
Figure 2. Engineering and Computer Science Building Conference Room Layout .....................10
List of Tables
Table 1. Identification of Tests ........................................................................................................8
Table 2. Test Schedule .....................................................................................................................9
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
1.
3
OBJECTIVE
The Geographical Auto-Delivery System (GAS) prototype provides a simple and
affordable solution to the main issues when traveling. GAS displays notifications of participating
businesses that are within five miles of where the end-user clicks on the map. The end-user has
an option to fill out a profile of his or her favorite businesses to filter out any business that he or
she may not like. This profile is initially filled out after registration and can be updated whenever
desired. The end-user profile automatically updates whenever there are new businesses
participating.
A business may participate by registering on the GAS prototype website. After initial
registration, the business must wait for verification before being able to update the business
profile, which contains the establishments the business may have. This profile may be updated
after notification that their business has been verified and anytime after that verification. After
the business initially fills out the business profile and the business logs in for a second time, the
most updated profile will display.
When an end-user logs in, he or she has an option to update his or her profile or may
access the map application to click on a location and view the businesses within five miles of
that location. The types of businesses displayed are food, gas station, hotel, and attraction. The
notifications will include the name of the business, address, phone number, hours of operation,
and any other information provided in that business’s profile. This will give the end-user an idea
of what businesses are in the area of where he or she clicked and more information of the
business so the user can determine if he or she would like to visit that particular business.
The test plan for the GAS prototype will serve as a method by which the GAS website,
end-user profile, business profile, database, animated GIF, geographical user interface,
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
4
notifications, distance algorithm, database communication, and authentication and access control
can be tested for efficiency, security, and functionality. The test cases will serve as a platform to
validate and evaluate individual portions of the GAS prototype. Each test case procedure will
have a set of input parameters and at least one desired result or output.
2.
REFERENCES
Webster, M.A. (2011). Lab I – GAS Product Description. Old Dominion University. Department
of Computer Science.
Webster, M.A. (2011). Lab II – GAS Prototype Product Specification. Old Dominion University.
Department of Computer Science.
3.
TEST PLAN
The test plans for GAS prototype are designed to evaluate the functionality outlined in
the GAS requirements documentation. For each test plan, a schedule and detailed set of
procedures are provided. After completion of the GAS prototype, all test cases must have
reached successful results.
3.1.
Testing Approach
Each major component used in the GAS prototype will be tested through the individual
test cases. The major components to be tested include the database, the notification subsystem,
and the website. The website also contains the end-user profile and the business profile.
[This space intentionally left blank]
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
5
Figure 1. GAS Prototype Major Functional Component Diagram
The end-user and business profiles must be tested a few different ways since they retrieve
information from the database and send information to the database. To verify the information
retrieved from the database is valid, the data included in the profiles will be cross-referenced
with the data in the database. To verify the information sent to the database was valid the data in
the database will be cross-referenced with the information inputted through the profile, whether
it was the business profile or the end-user profile.
The Distance Algorithm will be tested by clicking on a location on the map and verify
that the notifications displayed are the correct participating businesses within five miles of the
location clicked via a notification. This will require the information from the database along with
the information inputted from clicking on a certain location on the map. Cross-referencing the
information in the notification with the data in the database will test the notifications.
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
6
Authentication and Access Control will be tested a couple of ways. One way is that a user
will attempt to type in an incorrect username and password combination, which should not allow
the user to proceed without entering the combination again until it is correct. After the correct
username and password combination is entered, the access level will determine the next page
displayed, which is stored in the database. The access level stored in the database and the page
displayed will be cross-referenced to verify if this test is successful.
3.2.
Identification Of Tests
The GAS prototype is tested and verified using 10 categories of testing and evaluation.
Table 1 outlines the categories along with a description of each test to be performed. Section 5.1
provides more details, including the procedure and expected results, for each individual test case
outlined in Table 1.
[This space intentionally left blank]
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
Cat
Id
1
Description
GAS Product Website
(Yousef)
Test
Case #
1.1
1.2
1.3
2
End-User Profile
(Marrissa)
2.1
4.3
Verify data existence and integrity in database
Verify that the animated GIF will display the
“About” page of the GAS website
Verify that the test harness GUI will display
properly
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
4
Database (Ryan)
Verify website is fully functional and resolution on
Firefox and Internet Explorer
Verify all contents of the website are displayed
properly
Verify all website links are working and not broken
4.2
2.3
Business Profile (John)
Description
During initial registration, verify that the end-user
profile displays after clicking the submit button in
the registration page
Verify that the correct points of interest are being
displayed on the end-user profile form
Verify that the profile for the particular end-user is
displaying the most updated profile
Check that expected page appears after submit
button is clicked
Check that the address is correct on the
establishment form within the business profile
Check that the e-mail address contains the @ sign
and valid domain
Check that the phone number is the correct number
of digits and contains the area code
Check to make sure the Terms of Agreement is
agreed to via the checkbox labeled “I Agree”
Ensure that once an establishment is added to the
business profile, the information is transmitted to
the database correctly
Show that when restaurant is chosen as the business
type, that particular page is displayed
Show that when gas station is chosen as the
business type, that particular page is displayed
Show that when hotel is chosen as the business
type, that particular page is displayed
Show that when attraction is chosen as the business
type, that particular page is displayed
Verify primary key constraints are properly
enforced in each table
Verify foreign key constraints are properly enforced
2.2
3
7
4.1
5
Animated GIF (Becky)
5.1
6
Graphical User Interface
(Becky)
6.1
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
Cat
Id
7
8
9
Description
Notifications (Becky)
Distance Algorithm
(Ben)
Database
Communication (Ben)
Test
Case #
7.1
8.1
9.1
9.2
10
Authentication and
Access Control (Alvin)
10.1
10.2
10.3
10.4
8
Description
Verify that the end-user can interact with the map
GUI and receive the proper output
Verify the Distance Algorithm is functioning
correctly
Verify data inserted into the database for End Users
through the website is valid
Verify data inserted into the database for Business
Users through the website is valid
Verify that only proper username and password
combination allows a visitor to gain Traveler
Access Level
Verify that only a proper username and password
combination allows a visitor to gain Business User
Access Level
Verify that only a proper username and password
combination allows a visitor to gain Establishment
User Access Level
Only visitors with the appropriate access level
should be able to access restricted pages
Table 1. Identification of Tests
3.3
Test Schedule
The GAS team is allotted one hour to demonstrate the functionality and capabilities of the
prototype. The first 15 minutes will be used to introduce the GAS solution. The next five minutes
will be used to navigate through the GAS website and the animated GIF will be presented in the
next five minutes. The database will then be shown along with the schema and the data already
entered into it. For the next 10 minutes, a new business will be added to the application through
the website and the functionality of the profile will be demonstrated. Following the business
registration, the same demonstration will be shown but for an end-user. The next three minutes
will be used to demonstrate the functionality of the test harness and notifications displayed using
the distance algorithm. Finally, there will be a question and answer session for any questions the
review board may have. Table 2 outlines the test schedule that will be used during the
demonstration.
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
Start
Time
(min)
0:00
Duration
9
Description
Test Case #
15
Introduction
n/a
0:15
5
1.1, 1.2, 1.3
0:20
5
View the different pages on the GAS
website (Home, FAQs, Contact Us,
About GAS)
Show the Animated GIF on the About
GAS page
0:25
2
Display the database and the data in it
4.1, 4.2, 4.3
0:27
10
Business Registration and Profile
3.1, 3.2, 3.3, 3.4, 3.5, 3.6,
3.7, 3.8, 3.9, 3.10, 10.2,
10.3, 10.4, 9.2
0:37
10
End-User Registration and Profile
2.1, 2.2, 2.3, 10.1, 10.4, 9.1
0:47
3
6.1, 7.1, 8.1
0:50
10
Display the Test Harness and show the
notifications
Questions
5.1
n/a
Table 2. Test Schedule
3.4.
Fault Reporting And Data Recording
Throughout the testing process of the GAS prototype, the GAS team will record the
failed and verified tests. The test results will be recorded on a test validation sheet as passing or
failing. These results will be determined through visual inspection of the returned queries or the
GUI screens through the test harness or profiles.
3.5.
Resource Requirements
The GAS team requires two computers that are connected the Internet. One is used to
access the GAS website and the other is used to access the GAS database. The GAS team also
requires a projector used to display the website and a TV used to display the database. This will
allow easy cross-referencing of the database with the different components on the website,
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
10
including the end-user profile, business profile, and notifications displayed through the test
harness.
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 GAS prototype
presentation. The computer located in the conference room will be required by the GAS team to
display the website, which will also be projected through projector screen 1 and projector screen
2. Another computer will be needed to display the database and that computer will be displayed
through TV 2. Figure 2 shows the layout of the conference room.
Figure 2. Engineering and Computer Science Building Conference Room Layout
4
TEST RESPONSIBILITIES
Please see the team’s collaborative version.
5
TEST PROCEDURES
Please see the team’s collaborative version.
LAB III – PROTOTYPE TEST PLAN AND PROCEDURE
6
TRACEABILITY TO REQUIREMENTS
Please see the team’s collaborative version.
11