Test Plan

New Vision Concept School Portal

Submitted in partial fulfillment of the requirements of the degree of

MSE

Sindhu Thotakura
CIS 895 – MSE Project
Computing and Information Sciences
Kansas State University

Committee Members
Dr. Mitchell Neilsen(Major Professor)
Dr.Gurdip Singh
Dr. Daniel Andresen.

1
Change Log
Version # Changed By Release Date Change Description
------------------------------------------------------------------------------------------------------------------
Version 1.0 Sindhu Thotakura 04/04/2012 Initial Release

2
Table of Contents
1. Test Plan Identifier ..................................................................................................................... 4
2. Introduction ............................................................................................................................... 4
2.1 Objective ............................................................................................................................. 4
2.2 Background .......................................................................................................................... 4
2.3 Scope .................................................................................................................................... 4
2.4. References ........................................................................................................................... 4
2.5. Definitions ........................................................................................................................... 4
3. Test Items ................................................................................................................................... 5
4. Features To Be Tested ................................................................................................................ 5
5. Approach .................................................................................................................................... 6
5.1 Functional Testing ................................................................................................................ 6
5.2 Usability Testing .................................................................................................................. 6
5.3 Compatibility Testing ........................................................................................................... 7
5.4 Performance Testing ............................................................................................................. 7
5.5 Testing Tools........................................................................................................................ 7
6. Test Deliverables ........................................................................................................................ 7
7. Environment ............................................................................................................................... 8
7.1 Hardware .............................................................................................................................. 8
7.2 Software ............................................................................................................................... 8
8. Pass or Fail Criteria..................................................................................................................... 8
9. Suspension Criteria and Resumption Requirements ..................................................................... 8
9.1 Suspension Criteria ............................................................................................................... 8
9.2 Resumption Requirements .................................................................................................... 8

3
1. Test Plan Identifier
New Vision Concept School Portal - Validation-V-1.0

2. Introduction
2.1 Objective
The main objective of the test plan for the New Vision Concept School Portal is to specify the testing
details of the use cases of the New Vision Concept School Portal. The software project test plan also
describes the objective, scope, approach, on identifying and defining the test tools and Environment of the
software testing effort for the New Vision Concept School Portal.

2.2 Background
The main purpose of the project is to develop a website for New Vision Concept School Portal. The users
can browse the website based on the information needed and even they can login into the website to view
particular information. The test plan for this New Vision Concept School Portal ensures that all the
information is provided in a proper way such that user can easily access it. Moreover each role has
different levels of access to the website and test plan has to layout criteria to test the content displayed to
the user when they login to the website is appropriate only to that particular role.

2.3 Scope
This test plan specifies the mechanisms that will be used to test the New Vision Concept School Portal.
This portal is categorized into three functional modules based on user roles: Users, Students and Staff.
Integration and System Testing will be performed to verify the coupling and cohesion of Site and Sub-site
hierarchy.

2.4 References
The following documents will be used as a reference for this test plan:
• IEEE Standard for Software Test Documentation Std 829-1998
• Deliverables of the Phase I for New Vision Concept School Portal
• Vision Document version 2.0
• Project Plan version 2.0

2.5 Definitions
The following are some of the terms and definitions that are related to the test plan of the New Vision
Concept School Portal

4
 • Pass/Fail criteria: Decision rules that are used to determine whether a software item passes or
fails a test.
• Test: A collection of one or more test cases
• Test Item: A software item that is an objective of testing.
• Test Plan: A document describing the scope, approach, resources and schedule of the intended
testing activities.
• Test Summary Report: A document summarizing the testing activities and results.
• Testing: The process of analyzing a software item to detect the differences between the existing
and required conditions

3. Test Items
This section of the test plan lists all the items of the New Vision Concept School Portal that will
be tested:
• Login
• Post and View Homework
• Post and View Results
• Forms
• Graphs
• Graphical User Interface

4. Features to be tested
As per the vision document 2.0 following features will be tested.
Users
SR1 – The user can view only one page at a time in the website.
SR2 – The user can register only if the user is either staff or a student who is studying 8th, 9th or 10th
class.
SR3 – The users can send the feedback.
SR4 – The users should be able to contact the management using the contact form.
Students
SR5 – The student can view the individual results obtained during exams which are posted by teacher.
SR6 – The student can view the class results which are posted by teacher.
SR7 – The student can view the Balance Due.
SR8 – The student can view the Class Schedule.

5
SR9 – The student can view the Homework posted by the teachers.
SR10 – The student can view the Comments posted by the teachers.
Teachers
SR11 – The teacher can update the results of the students.
SR12 – The teacher can write the comments about the students.
SR13 – The teacher can add or delete a student from the class.
SR14 – The teacher can post the Homework.
SR15 – The teacher can write the comments about the students.
SR16 – Appropriate graphs should be shown for the information.

5. Approach
This section of the test plan describes the overall approach for testing the New Vision Concept School
Portal. The types of testing carried out are Functional testing, usability testing and compatibility testing.
Apart from these, tools like JMeter, YSlow, Load Impact are also used. Functional testing tests whether
the system satisfies the basic requirements listed in the vision document. For each of these tests there will
be pass/fail criteria which determines whether the requirement is satisfied of not by the system. Usability
testing is a quality testing which determines the overall usability and user friendliness of the interface.
Compatibility refers to screen and different android device compatibility.

5.1 Functional Testing

The functional testing is mainly done on the whole integrated system to test functionality and make sure
that the project that has been developed meets all the requirements. The test cases for the system testing
will be the combination of unit and integration tests. After conducting unit test module wise, Black Box
Testing will be performed on the system as a whole. Tester inputs data into the application and records
the output from the system.

5.2 Usability Testing

Six users will be asked to use the system, and give their feedback. Comments from the users will be
documented. Among these six users two will be the normal users, the other two will be students and the
remaining two will be staff. All these different kind of users would be given the questionnaire in which
users have to rate for the questions including the easy and proper navigation, layout, visibility, layout,
Going back to homepage from any particular place, etc.

5.3 Compatibility Testing

6
In Compatibility Testing, the system is tested on different browsers which include Internet Explorer,
Mozilla Firefox, Google Chrome and Mac Safari. A Test Log will be used for testing the different
features in the three browsers. Results of the tests are documented in the test log.

5.4 Performance Testing

Jmeter is used to test performance both on static and dynamic resources. It is mainly used for
Performance Testing, Load Testing and Stress Testing. It can be used to simulate a heavy load on a
server, network or an object to test its strength or to analyze overall performance under different load
types. It is used to make a graphical analysis of performance or to test your server/script/object behavior
under heavy concurrent load. It can be used to simulate a heavy load on a server, network or an object to
test its strength or to analyze overall performance under different load types. It is used to make a
graphical analysis of performance or to test your server/script/object behavior under heavy concurrent
load.

5.5 Testing Tools

YSlow:
Yslow is used to analyze web page performance by examining all the components on the page. It also
examines components dynamically created by using JavaScript. It measures page performance and offers
suggestions for improvement.

6. Test Deliverables
• Test design specification
• Test case specification
• Test procedure
• Test Log
• Test summary report
Schedule
The testing is carried out at various phases of the project and the respective deliverables for that
particular phase. The test log will contain the record of all test cases along with pass/fail status. If a test
case fails it will be logged in the test log. The test log will also contain the suggested solution for the
failed test cases. Other independent test cases can be run in parallel but the failed test cases are rerun after
the possible workarounds are carried out.
Software Development Lifecycle Phase Activity

7
 Inception Phase Test plan proposed
Elaboration Phase Test plan approved and test cases are designed.
Construction Phase Test case execution
Transition Phase Alpha and Beta level testing.

7. Environment
This section describes the necessary infrastructure required for the test environment for the New Vision
Concept School Portal

7.1 Hardware
The testing will be done in the Windows 7 laptop which has Microsoft Visual Studio 2010.

7.2 Software
• Operating system: The system will be tested in Windows 7.
• Databases: MS SQL Server 2005 is used to test content data & configuration data of the website.

8. Pass or Fail Criteria

The test cases executed on the Airline Reservation System will pass if they meet the specific requirements
mentioned in the Vision document of the project. A test case is said to fail, if the desired functionality is
not satisfied by the system.

9. Suspension Criteria and Resumption Requirements

9.1 Suspension Criteria
Testing for all the dependent features will be suspended if a test case fails. The failed test case will be
logged onto the test log which contains the description for the error.

9.2 Resumption Requirement

The test cases which are not dependent on the case where the bug is reported will be executed in parallel
with the bug fixing. Once the failed test case has been taken note of and has been identified and fixed then
the testing for the failed test case will resume.