Running Head
Lab III – READ Prototype Test Plan/Procedure
Lab III – READ Prototype Test Plan/Procedure
Andrew Moss
CS411
Janet Brunelle
April 17, 2013
Version 1
1
Lab III – READ Prototype Test Plan/Procedure
2
Table of Contents
1 Objectives .................................................................................................................................... 3
2 References .................................................................................................................................... 3
3 Test Plan....................................................................................................................................... 4
3.1 Testing Approach ...................................................................................................................... 4
3.2 Identification of Tests ............................................................................................................... 6
3.3 Test Schedule .......................................................................................................................... 10
3.4 Fault Reporting and Data Recording ...................................................................................... 10
3.5 Resource Requirements .......................................................................................................... 10
3.6 Test Environment .................................................................................................................... 11
List of Figures
Figure 1 – Major Functional Component Diagram......................................................................... 5
List of Tables
Table 1 – Test Category Identification ........................................................................................... 6
Table 2 - Test Schedule................................................................................................................. 10
Lab III – READ Prototype Test Plan/Procedure
3
1 Objectives
The purpose of this document is to specify a methodology and sequence for testing the
functionality of the READ prototype. Additionally, the tests themselves will be identified herein.
The team behind READ, a Repository for Electronic Aggregation of Documents, intends to
alleviate the lack of quality online resources for displaying publications and grants. The READ
system will use a scraper to provide researchers with a method of organizing their publications
and grants in a format that allows for easy searching, sorting, filtering, and browsing. The testing
described in these pages will confirm that the READ prototype performs as expected and in
doing so, satisfies the requirements established in Lab II.
2 References
McRobbie, Michael A (2012, December 19). The Multibillion-Dollar Threat to Research
Universities. From The Chronicle of Higher Education:
http://chronicle.com/article/The-Multibillion-Dollar-Threat/136363/
Moss, Andrew. (2013). LAB I – READ Product Description. Norfolk, VA: Author.
Moss, Andrew. (2013). Lab II – READ Product Prototype Specification. Norfolk, VA: Author.
National Center for Education Statistics. Degree-granting institutions and branches, by controls
and level of institution and state or jurisdiction, 2010-11. From the Digest of Education
Statistics: http://nces.ed.gov/programs/digest/d11/tables/dt11_280.asp
(This space intentionally left blank.)
Lab III – READ Prototype Test Plan/Procedure
3 Test Plan
The following sections will enumerate the types of tests that will be performed, the
schedule in which the tests will be conducted, recording procedures, required resources, details
about the environment in which testing will occur, and the responsibilities of individual team
members.
3.1 Testing Approach
READ will be tested at the unit, integration, and system levels for compliance with
previously established requirements. Each of the major functional components of the prototype
will be tested and they are illustrated in Figure 1.
(This space intentionally left blank.)
4
Lab III – READ Prototype Test Plan/Procedure
5
Figure 1 – Major Functional Component Diagram
Each of these components will be tested individually, with unit tests, followed by
integration tests that will test interaction between components, and lastly the entire prototype will
be tested as a whole with system tests. The user interface will be tested for functionality and
correct display by visual inspection. The database will be tested using SQL queries submitted
with the MySQL command line client to verify its contents. The scraper will be tested by
manually conducting a search at the Microsoft Academic Search site and comparing the results
with those obtained by the scraper.
Lab III – READ Prototype Test Plan/Procedure
3.2 Identification of Tests
The tests to be performed are identified in Table 1.
Table 1 – Test Category Identification
Module
ID
Module
Test Case
1.1
1.2
Sub-Module
Objective
Publication
Browse through all
Query Page
publications on the system
Grant Query
Browse through all grants on
Page
the system
Home page of READ.
Displays most recent
User
1
documents and llows for
Interface
navigation to other parts of the
1.3
Main Page
UI
Allow registered users to log
into READ for authentication
1.4
Login Page
purposes
List information on the
specific user which is logged
1.5
1.6
Profile Page
in
Publication
Allow the user to submit
Add Page
publictions manually into the
6
Lab III – READ Prototype Test Plan/Procedure
system
Allow the user to submit
Grant Add
1.7
Page
Profile Edit
1.8
Page
grants manually into the
system
Allow the user to submit
changes to their profile page
Allow the user to alter their
Publication
1.9
Edit Page
own publication information in
READ
Allow the user to alter their
Grant Edit
1.10.
Page
own grant information in
READ
Houses all abilities which are
Administration restricted solely to system
1.11
2
Page
administrators
Publications
Backend User
2.1
Interface
2.2
2.3
Page
Default publication display
Filtered publication display
Grants Page
2.4
Default grants displaly
Filtered grants display
Verify username validity and
2.5
Login
authenticity
2.4
Editing
Verify publication editing
7
Lab III – READ Prototype Test Plan/Procedure
Verifiy grants editing
Verify that profile page is
2.5
Profile Page
2.6
Profile Editing
displaying properly
Verify profile editing
Verify that the basic database
Database
3.1
Access
account can log into the
database server
Verify that the basic database
account can add authors to the
3.2
Add Author
Auths table
Verify that the basic database
account can add publications
3.3
Add Paper
to the Paper table.
Verify that the basic database
account can link publications
3.4
3
Owns table test to authors
Verify that the basic database
Database
account can add grants to the
3.5
Add Grants
Grants table.
Verify that the basic database
account can link grants to
authors who are COPIs on
3.6
Add CO_PI
grants
8
Lab III – READ Prototype Test Plan/Procedure
Verify that the Authstrings
Add
3.7
AuthString
basic database account
Microsoft
Verify that publications
Academic
belonging to the author are
4.1
Scraper
4.2
Bibtext Parser
identified and exported
Trigger Parser
Empty Results
Data
4
table can be filled out by the
Process All Items
Scraper
Empty Attributes
Parse Specific Attributes
Correct Format
4.3
Database
Update
Updater
No Overwrite
Required Data
One Author At A Time
Verify that e-mails are sent to
Email
4.4
Notification
author when new publication
is discovered
9
Lab III – READ Prototype Test Plan/Procedure
10
3.3 Test Schedule
The READ team has been allotted 50 minutes for testing. Testing will be conducted in
accordance with the schedule in Table 2.
Table 2 - Test Schedule
Elapsed Time
Duration
Test
(hours:minutes) (minutes)
Objective
0
User
10
Test Event
1.1 – 1.11
Interface
10
10
Back-end
2.1 – 2.6
Interface
20
10
Database
3.1 – 3.7
30
20
Scraper
4.1 – 4.4
3.4 Fault Reporting and Data Recording
All test results will be recorded by hand on a pre-printed paper form.
3.5 Resource Requirements
To present the prototype, the READ virtual machine must be running and have Internet
connectivity. The database will need to be populated with multiple publications, grants, and
authors in order to display complete functionality of the GUI. A desktop machine with Internet
connectivity, an SSH client, and a web browser will be required to conduct the tests. Lastly, the
Lab III – READ Prototype Test Plan/Procedure
11
Computer Science Department’s NIS servers will need to be running to demonstrate user
authentication.
3.6 Test Environment
The testing of the READ prototype will be conducted in the conference room located in
room 3316 of the Engineering and Computer Science building. This room contains two
multimedia projectors and four workstations with flat screen monitors and wireless mice and
keyboards. The majority of the team will stand next to one of the projector screens while another
member of the team conducts tests from one of the workstations.