PROJECT
SECME
Test Plan
Modification history:
|
Version |
Date |
Who |
Comment |
|
v0.0 |
08/15/00 |
G. H. Walton |
Template |
|
v1.0 |
08/15/02 |
Carthik A.Sharma |
Initial Version |
v2.0 |
09/29/02 |
Santhosh J.Grandai |
Modified as Per Team Review -Submitted |
v3.0 |
11/18/02 |
Santhosh J.Grandai |
Final Version |
|
... |
|
|
|
Team Name: TEAM SECME
Team Members:
Contents of this Document
Overall
Objective for Software Test Activity
SECTION
1: Introduction
Reference
Documents:
SECTION
2: Description of Test Environment
·
The
test environment includes,
·
Operating
System: Windows 95/98/NT installed with tomcat server 3.2.4 and jdk 1.2.2
·
Database:
MS ACCESS with ODBC data connectivity facility.
·
Browsers:
Internet Explorer or Netscape Navigator with Java enabled.
·
PC
Minimum Requirements: Pentium processor, 450MHz, 128MbRAM.
· The test environment will be different from the environment in which the software will operate. All the web pages i.e. the java server pages developed are stored locally in the system and then they are run in the local machine. In the actual environment in which the software will operate, the web pages developed will be stored in a server and it will be accessed remotely from PCs or servers.
SECTION
3: Stopping Criteria
The
stopping Criteria of the testing will be after successful execution of all the
test cases mentioned.
SECTION
4: Description of Individual Test Cases
Test
Case 1:
·
Test Objective: The MECSP Organizer can successfully login into the system.
·
Test Description: The MECSP Organizer will enter his/her login name and password and
then press the Submit button. For test purposes we entered the following data,
Username = “organizer” and Password = “pass123”.
·
Test Conditions: See Test Environment.
·
Expected Results: If the username and password entered was correct then the MECSP
Organizer will be able to log into the system and go on to the next web page
the “MECSP Organizer Main Page” which has various options in the system. If the
username or password entered is incorrect then the MECSP Organizer will see
an “LOG IN FAILURE” web page.
Test Case 2:
·
Test Objective: The School Coordinator can successfully login into the system.
·
Test Description: The School Coordinator will enter his/her login name and password and
then press the Submit button. For test purposes we entered the following data ,
Username = “coordinator” and Password = “pass123”.
·
Test Conditions: See Test Environment
·
Expected Results: If the username and password entered was correct then the School
Coordinator will be able to log into the system and go on to the next web page
the “School Coordinator Main Page” which has various options in the system. If
the username or password entered is incorrect then the School Coordinator will
see an “LOG IN FAILURE” web page.
Test Case 3:
·
Test Objective: The MECSP Organizer can successfully send information or notification
to school coordinators regarding upcoming events and workshop.
·
Test Description: The MECSP Organizer will click the “Send Notification to School
Coordinators” option in the “MECSP Organizer Main Page” which will open a new
web page, where the MECSP Organizer can type in the subject and the message to
be sent in the respective text areas and click the ‘Send’ button.
·
Test Conditions: See Test Environment
·
Expected Results: After clicking the ‘Send’ button, the email address to which the
message has to be sent will be pulled from the database in the table “USER”
from the US_EMAIL column and the message should be sent successfully.
Test Case 4:
·
Test Objective: The MECSP Organizer can successfully add an Annual Competition.
·
Test Description: The MECSP Organizer will click the “ADD AN ANNUAL COMPETITION” option
in the “MECSP Organizer Main Page” which will open up a new web page to add the
ANNUAL COMPETITION details. For test purposes we entered the following data,
DATE = “01/18/03”, TIME=“09:00 PM” and LAST DAY FOR REGISTRATION = “12/15/02”.
·
Test Conditions: See Test Environment
·
Expected Results: All the mentioned data will be stored into the database in the table
named “COMPETITION” into their respective columns.
Test Case 5:
·
Test Objective: The MECSP Organizer can successfully add an Event for the Annual Competition.
·
Test Description: The MECSP Organizer will click
the “ADD AN EVENT” option in the “MECSP Organizer Main Page” which will open up
a new web page to add the declare an event and add its respective details. For
test purposes we entered the following data, NAME = “ROCKET”,
RULES=”XXXXXXXXX”, DATE = “01/18/03”, TIME=“12:00 PM” and NUMBER OF PARTICIPANS
IN A TEAM= 12.
·
Test Conditions: See Test Environment
·
Expected Results: All the mentioned data will be stored into the database in the table
named “EVENT” into their respective columns.
Test Case 6:
·
Test Objective: The MECSP Organizer can successfully see the summary of Events added
into the database for the Annual Competition.
·
Test Description: The MECSP Organizer will click the “View Summary” button
in the “ADD EVENT” web page which will open up a new web page showing all the
events added with its details in a tabular form with event names as hyperlinks.
·
Test Conditions: See Test Environment
·
Expected Results: The MECSP Organizer can successfully view all
the events and its details added in the database correctly.
Test Case 7:
·
Test Objective: The MECSP Organizer can successfully view the event details filled in
a way so that it can be modified , if the MECSP Organizer wants to change the data
entered about an event incorrectly.
·
Test Description: The MECSP Organizer will click one of the event
names, which are shown as hyperlinks on the “EVENT SUMMARY” web page.
·
Test Conditions: See Test Environment.
·
Expected Results: The MECSP Organizer can successfully view a web
page similar to “ADD EVENT” web page with all the text areas filled in
automatically with the correct details for that particular event, so that the
MECSP Organizer can change the details.
Test Case 8:
·
Test Objective: The MECSP Organizer can successfully change the event details filled
in before and restore into the database.
·
Test Description: The MECSP Organizer will change some of the details
in the event and click the “OK” button.
·
Test Conditions: See Test Environment.
·
Expected Results: The MECSP Organizer can successfully change the
details and resubmit the results into the database for that particular event.
Test Case 9:
·
Test Objective: The School Coordinator can successfully send information or queries to
MECSP Organizers regarding annual competition or events.
·
Test Description: The School Coordinator will click the “SEND QUERY”
option in the “school Coordinator Main Page” which will open a new web page,
where the School Coordinator can type in the subject and the message to be sent
in the respective text areas and click the ‘Send’ button.
·
Test Conditions: See Test Environment
·
Expected Results: After clicking the ‘Send’ button, the email address
to which the message has to be sent will be pulled from the database in the
table “USER” from the US_EMAIL column and the message should be sent
successfully.
Test Case 10:
·
Test Objective: The School Coordinator can successfully register a student to
participate in the annual competition.
·
Test Description: The School Coordinator will click the “REGISTER
STUDENTS” option in the “School
Coordinator Main Page”, which will open up a new web page will various
textboxes and option buttons to be filled in by the School Coordinator. For
test purposes we entered the following data, STUDNENT FIRST NAME = “JOHN”,
MIDDLE NAME = “A”, LAST NAME =
“SMITH”, GRADE LEVEL = 3,MATH LEVEL = “ADVANCED MATH”, EVENTS = “ROCKET” and
then click the “SUBMIT” or “ADD MORE STUDENTS” button.
·
Test Conditions: See Test Environment.
·
Expected Results: The values entered by the School Coordinator are
successfully filled into the database in the table “REGISTRATION_ANNUAL” into
their respective columns.
Test Case 11:
·
Test Objective: The School Coordinator can successfully register more number of
students to participate in the annual competition.
·
Test Description: The School Coordinator will click the “ADD MORE
STUDENTS” button, so that the same page will refresh again and will be shown
with empty fields, so that the School Coordinator can enter information about
another student. The data entered will be similar to that as shown in test case
10.
·
Test Conditions: See Test Environment
·
Expected Results: The values entered by the School Coordinator about
another student Coordinator are successfully filled into the database in the
table “REGISTRATION_ANNUAL” into their respective columns.
Test Case 12:
·
Test Objective: The School Coordinator can successfully view the filled in information
about the students to participate in the events of annual competition, to make
sure the information entered was right.
·
Test Description: The School Coordinator will click the “ View Summary”button and then a new web page will open up with details of each and every student filled in by the school coordinator in a tabular form.
·
Test Conditions: See Test Environment
·
Expected Results: The School Coordinator can successfully view all
the student details with student name as hyperlinks added in the database
correctly.
Test Case 13:
·
Test Objective: The School Coordinator can successfully view the student details filled
in a way so that it can be modified, if the School Coordinator thinks that the
data entered about a particular student should be changed.
·
Test Description: The School Coordinator will click one of the
student names, which are shown as hyperlinks on the “ SUMMARY” web page.
·
Test Conditions: See Test Environment.
·
Expected Results: The School Coordinator can successfully view a web
page similar to “REGISTER STUDENTS” web page with all the text boxes and option
values filled in automatically with the correct data for that particular
student, so that the School Coordinator can change the data.
Test Case 14:
·
Test Objective: The School Coordinator can successfully change the Student data filled
in before and restore into the database.
·
Test Description: The School Coordinator will change some of the data
about the student entered before shown as explained in the Test Case 10 and
click the “OK” button.
·
Test Conditions: See Test Environment.
·
Expected Results: The School Coordinator can successfully change the
data and resubmit the data into the database for that particular student.
Test Case 15:
·
Test Objective: The School Coordinator can successfully go to the “SUMMARY ” web page
even if there is no change in the data entered.
·
Test Description: The School Coordinator will view the data shown as
described in Test case 13 and does not change any data entered and clicks the
“OK” or “CANCEL” button.
·
Test Conditions: See Test Environment.
·
Expected Results: The School Coordinator will view the “SUMMARY” page again.
Test Case 16:
·
Test objective: Deletion of data about a student by the School Coordinator.
·
Test Description: The School Coordinator will be able to see the
option button shown as a column for all the students stored in the “SUMMARY PAGE”, so the school coordinator
can click the option button for the particular student for whom the data has to
be deleted from the database and then click the “DELETE” button.
·
Test Conditions: See Test Environment.
·
Expected Results: The data for the particular student selected will
be removed from the database and the “SUMMARY PAGE” will be again showed to the
School Coordinator with the absence of the deleted record.
Test Case 17:
·
Test objective: Ability to show to the School Coordinator that the data entered about
each student stored in the database is not confirmed.
·
Test Description: There is a field in the “SUMMARY PAGE” for each
student stating “YES” or “NO” indicating whether the data entered about each
student is stored or not. The field will turn to “YES” only when the School
Coordinator will click the “Submit to MECSP” button.
·
Test Conditions: See Test Environment
·
Expected Results: The School Coordinator should see the “NO” value
for each student data row because the School Coordinator did not click the
“Submit to MECSP” button till now.
Test Case 18:
·
Test objective: Confirmation of submission of data regarding all the students entered.
·
Test Description: The School Coordinator will click the “Submit to
MECSP” button in the “SUMMARY PAGE” to confirm their submission of data into
the database.
·
Test Conditions: See Test Environment.
·
Expected Results: The valid field in the “REGISTER_COMPETITION” table
in the SECME database will be set to “YES” in the “SUBMITTED” field for all the student rows entered by the
School Coordinator and the School Coordinator will be taken to the “SCHOOL
COORDINATOR MAIN PAGE”.
Test Case 19:
·
Test objective: School Coordinator can see the data entered days before and change it,
after logging into the system.
·
Test Description: The School Coordinator will log into the system and
then click the “VIEW SUMMARY” option in the “SCHOOL COORDINATOR MAIN PAGE”.
·
Test Conditions: See Test Environment.
·
Expected Results: The School Coordinator will see the “SUMMARY PAGE”
with all the data about each student filled in before which can be modified and
resubmitted as described in Test Case 14.
Test Case 20:
·
Test objective: School Coordinator can view the data entered about a particular
student which was not confirmed by clicking the “SUBMIT TO MECSP” button
because may be the system went down after entering the data or the School
Coordinator forgot to click the “SUBMIT TO MECSP” button entering data for say
about 30 students.
·
Test Description: The School Coordinator will logon to the system and
then click the “VIEW SUMMARY” option in the
“SCHOOL COORDINATOR MAIN PAGE”.
·
Test Conditions: See Test Environment.
·
Expected Results: The School Coordinator will see the “SUMMARY PAGE”
with all the data entered before with the “NO” value in the “SUBMITTED” field
for the student data, which was not confirmed for submission for various
reasons explained in the Test objective. Now the School Coordinator can confirm
the submission of pre-entered data by just clicking the “SUBMIT TO MECSP”
button.
Test Case 21:
·
Test objective: The MECSP Organizer can Successfully view the student data filled in
by the School Coordinator of all schools participating in the annual
competition.
·
Test Description: The MECSP Organizer will log into the system and
click the “SCHOOL DETAILS SUMMARY” option in the “MECSP ORGANIZER MAIN PAGE”.
·
Test Conditions: See Test Environment.
·
Expected Results: The MECSP Organizer should be able to view all the
data regarding the schools and the students participating in the events and the
name of the events in which in the students are participating in a nice
formatted tabular manner.
Test Case 22:
·
Test objective: Log out of the system successfully.
·
Test Description: The MECSP Organizer and the School Coordinator
should be able to logout of the system successfully when they click the
“LOGOUT” option.
·
Test Conditions: See Test Environment.
·
Expected Results: The MECSP Organizer and the School Coordinator logs
out of the system successfully and views the MECSP home page
Template created by G. Walton (GWalton@mail.ucf.edu) on March 28, 1999 and last modified on August 15, 2000.
This page last modified by Santhosh J.Grandai (santhu79@hotmail.com) on December 04,2002.