Final Semister Project How to Test a Software

035-TEST PLAN-
SOFTWARE TESTING FOR APS ZAMZAMA
V1.0

Summary…………………………………………………………………………………………………
4
Background….…………………………………………………………………………………………
5
Project Scope…………………………………………………………………………………………
5
Test Plan Objectives/ Deliverables ………………………………………………………
5
Features to be Tested…………………………………………………………………………..
6
Test Strategy………………………………………………………………………………………..
6
System Functionality Test……………………………………………….
6
Security Test……………………………………………………………………
6
Documentation Test………………………………………………………..
6
Regression Test……………………………………………………………….
7
User Acceptance Test……………………………………………………..
7
Test Pass/Fail Criteria…………………………………………………………………………..
7
Suspension/ Resumption Criteria………………………………………………………….
7
Defect Reporting…………………………………………………………………………………….
7
Test Deliverables /Test Deliverables…………………………………………………….
8
Resources and Responsibilities……………………………………………………………..
8
Resources……………………………………………………………………………..
8
Responsibilities……………………………………………………………………..
8
Security Clearance…………………………………………………………………………………..
9
Risks…………………………………………………………………………………………………………
9
Management…………………………………………………………………………………………..
9
Personnel…………………………………………………………………………………………………..
9
Requirements………………………………………………………………………………………….
9
Documentation………......................................................................
9


Document Name
Prepared / Reviewed by
Review Summary
Date
035- Test Plan Document for School Management System Project
Ahmed Zeb
Document Created
12-28-2007


SUMMARY
This document covers the Test Plan for the APS Zamzama testing Project. Documents that are referenced for the preparation of this test plan involve:
· Requirement Document – APS Zamzama.doc
BACKGROUND
The main disadvantage in the manual work was that, there was no sharing of information between different activities of the departments. This created a lot of problem for the employees of the school. To perform work manually, it wasted a lot of time of the school’s employee. It took a lot of time to storage and retrieve records. As the system was totally dependent on the human labor, so it needed number of employee to do any task. Due to manual work there was chance for the employee to tired or became ill and they to make mistake.
PROJECT SCOPE
School Management System was designed to cater for the growing need of automation of processes and ease of use. The application aims to provide better and automated accounting, admission, examination and employee modules.
TEST PLAN OBJECTIVES / DELIVERABLES
This Test Plan for the School Management System will comprise of the following Objectives / Deliverables:
1. Define the activities required to prepare, execute, and report the White Box (Unit, Module, Integration, System) and Black Box (Usability, Functional, Regression and User Acceptance Testing).
2. Communicate the Test Strategy to all responsible parties.
3. Communicate the various Dependencies and Risks to all responsible parties.



FEATURES TO BE TESTED
Following is the list of features of the School Management System Project that are to be tested:

The Examination section will keep all the records of all students including mid term, final term, Assignments, weekly tests Marks.
The passing marks are 5o %. They calculate all mid term, Final term, Assignments, weekly tests Marks and which student took 50 % he will be promoted to next Class, while there will be no Final Exam of Class 9th actually the 9th and 10th Classes subjects are same so they take only one (1) Exam of Both Classes.
The Examination Section also to keep the record of,
Warning
This is the warning form of the school. Warning which is given by the principle to the students if we click on search button a frame will open & give following search options
Student no
Student name
Subject id
Subject Name
All Record
The fields of this form are,
Adm_ no (FK), Warning _no (PK), Class_ no (FK), Section _no (FK), Subject _no (FK), Date, Principle remarks.

COUNCIL FORM
The APS make a council of Intelligent and brilliant Students and the head of the council is a teacher the council members go to the week Students that why they cannot study are there any home problem or due to any other reason they can not study.
The council members also teach the week Students Free of Cost.
Observation
The observation also to keep all the records of all the students and they directly contact with Students Parents.
This is the main form of the Zamzama Public School Nowshera.This form is used for the admission process of the student. It contains the basic information about students.
In the registration field we give the registration no & the rest of the information displayed on the form.
This is admission search form. In this form we can search the record of the student by the following search option & the record of the students will be displayed in the grid.
By Student Name
By Admission No
By Gender
By Section
By Class
By Father Name
When the user is going to search the record of the student if the user write e.g. a or b or any other alphabet the whole list of the student will be open in the grid whose name is starting from a or b or any other alphabet, or when he write full name of the student only that student data will be come to the grid whose name is written by the user.
The account section will maintain all the accounts of the school. It has two major components.
· Fee Structure
The Fee Structure of the account section will show the structure of the student, which they have paid or have to be paid when he/she admitted in the School.
· Monthly Fee



The fields of this form are,
Serial _no, Admission _no (FK), Registration fee, Library fee, Computer fee, Science fee, Sports fee, Book fee, Examination fee, Security fee, Annual fee, Category, Relatives, Month, total.
The user only fill the above fields the computer will automatically calculate all the fields.



MONTHLY FEES FORM
Serial _no (FK), Admission _no (FK), Class _no (FK), Library fee, Computer fee, Science fee, Sports fee, Book fee, Examination fee, Security fee, Annual fee, Category, Relatives, Month, Late fee fine, Absentee fine, Tuition fee, Total.
The user only fill the above fields the computer will automatically calculate all the fields



SUBJECT INFORMATION FORM
This is the subject information form of the School, that which subject is Teaching by which Teacher to which Class and also store the Subject Edition & the record is saved by subject no.
If we click on search button a frame will open which give following search options:

Student no
Student name
Subject id
Subject Name
All Record
By selecting one search option the record will be displayed on flex grid.
NOTE:
The subject no must be ‘integer’.The fields of this form are’
Subject _no, Subject name, Sub edition, Class _no (FK), Teacher.
TEACHER’S OBSERVATION FORM
This form is used for teacher’s observation about students. The teachers checks the record of the student & give his remarks about the students.
When a Teacher enter admission no the admission no will only accept ‘integer’ not any other character or any thing else & the record will display.
If we want to delete a record from database we can only delete record by class no, not on any other field.
The fields of this form are,
Adm_ no (FK), Observation _no (PK), Class_ no (FK), Section _no (FK), Class teacher, First remarks, Date, Second remarks, Date.






TEST STRATEGY
The test strategy consists of a series of different tests that will fully exercise the School Management System Project requirements. The primary purpose of this testing is to uncover the system limitations and measure its full capabilities as per the modifications performed. The initial testing will be carried out on the QA Server. A list of the various planned tests and a brief explanation follows below:
1. Unit testing:
Unit testing will focus on the testing of a single unit of code. Unit testing will help verify the integrity of a single unit. It will make sure that a single unit performs its designated task and is fulfilling the requirements ( or sharing the load to fulfill it).
2. Integration Testing:
Integration testing will focus on the integration of two modules and their impact on the overall system. Tests will be performed to determine the compatibility of two modules with each other and with the system.
3. Module Testing:
Module testing will be carried to determine functionality of a single module. Efforts will be made to test all possible paths.

4. System Functionality Test
The System Functionality Test will focus on the behavior of the School Management System Project users as per the requirements. User scenarios will be executed against the system to find the defects in the modified functionality.
Overall, the system tests will verify whether it meets the functionality defined in the Requirements Documents.
5. Security Test
The Security Tests will determine the accessibility of Internal Users to the “School Management Software”. Everyone should not be allowed to use the software. The concerned person should only view reports.
6. Documentation Test
Tests will be conducted to check the accuracy of the documentation provided to the QA Team till the completion of the project. These tests will ensure that no feature is missing, or needed data set unavailable, and the School Management System Project can easily be understood.

7. Regression Test
The testing cycle will be repeated if the fixes are made to the defects found. Regression Test is done in order to check if maybe any error has been introduced due to the Changes / Fixes done.

8. User Acceptance Test (Optional)
Once the School Management System Project is ready for implementation / deployment, end users will perform User Acceptance Testing (UAT). The purpose of this testing is to confirm that the system is developed according to the specified user requirements and is ready for operational.

TEST PASS / FAIL CRITERIA
Following functionalities will determine the Test Pass/Fail Criteria of School Management System Project .
· All the intended requirements for the School Management System Project are working fine.
SUSPENSION/RESUMPTION CRITERIA
If any defects are found which may seriously impact the testing progress, the QA Manager may choose to suspend testing. Criteria that will justify test suspension are:
1. As per described in the documentation, the intended functionalities of School Management System Project are not working properly
If testing is suspended, resumption will only occur when the problem(s) that caused the suspension has been resolved. When a critical defect is the cause of the suspension, the QA Department must verify the “FIX” before testing is resumed.

DEFECT REPORTING
No formal defect report will be documented during the testing cycle. When defect(s) are found, the QA Analysts will notify all issues to the development team at Mantis (En Pointe Bug Tracker). In case of ambiguity, discussions will be carried out between the concerned teams. The development team will then resolve the reported defect(s). Once the resolution is prepared, a notification is sent to all assigned team members of development; mentioning the defect(s) which are resolved. The QA Department then will resume testing and will verify the issue as ‘Open’ or ‘Closed’. Once all defect(s) are resolved and verified by QA,
The QA / EDI Team Lead will give the final Sign Off for moving subsequent build(s) into production.



TEST DELIVERABLES
Following are the test deliverables of School Management System Project:
1. Test Plan Document
2. Develop Test Cases
3. Testing Methodologies
4. Execute tests
5. Defect Report


RESOURCES AND RESPONSIBILITIES
The QA Team will determine when system tests will start and end. They will also be responsible for coordinating schedules & equipment for the personal involved in testing as well as writing / updating the Test Plan, and other documents.
1. Resources
The Project team consists of:
1. Project Manager ------------ Ahmed Zeb
2. Snr. Supervisor QA ------------ Ahmed Zeb
3. Project Lead Developer ------------ Ahmed Zeb
4. QA Analysts ------------ Ahmed Zeb


2. Responsibilities
Project Manager
Responsible for Project schedules and the overall success of the project.
Snr. Supervisor QA
Ensures the overall success of the Test Cycles. He will determine when system tests will start and end and also be responsible for coordinating schedules & equipment for the personal involved in testing as well as writing / updating the Test Plan, and other documents.

Project Lead Developer
Serve as a primary contact between the development department and the project team.
QA Analyst
Responsible for documenting, executing the test cases and defect reporting. Will coordinate and communicate the testing status to the project team.
User
Will assist in performing Beta and User Acceptance testing.

SECURITY CLEARANCE
All the information related to the School Management System of users should be provided to the QA Team (Testing team).
RISKS
1. Management
Management support is needed to insure testing is an event based process guided by milestones not by predetermined time frames. Management can reduce the risk of delays by ensuring dedicated testing personal, test equipment, and simulated system environments are available as requested.

2. Personnel
Dedicated staff is needed in order to promptly execute the test scenarios. If we have attrition of any type either external or internal we will experience delays in the project. All efforts to minimize attrition should be realized by all levels of management.
3. Requirements
The test plan and test schedule are based on the current available Documentation. Any changes to the requirements could affect the test schedule and will need to be approved by the Project Team.

DOCUMENTATION
The following documentation will be available at the end of the test phase:
1. Test Plan
2. Test Cases
3. Bug Reports

TEST CASES

Test Case Id
1
Test Date
12/28/2007
Test Point

Pre-Requisite
NA
Use Case Name
1.1
Test Engineer
Ahmed Zeb
Description
Login into System
Test Case Type
Functional
Steps Performed
1. Go to Desktop.
2. Open the Application
3. Give the correct username and correct password.
Expected Output
User should be allowed to enter into the system.
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement


Regards,
Ahmed Zeb
Q.A Analyst - Quality Assurance Department
Ph: 0334-5088530

Test Case Id
2
Test Date
12/28/2007
Test Point
Admission section form
Pre-Requisite
1
Use Case Name
2.1
Test Engineer
Ahmed Zeb
Description
Login into System
Test Case Type
Functional
Steps Performed
1. Go to Desktop.
2. Open the Application
3. Click Admission section.
4. Click the Add button on top.
Expected Output
All the fields (name, last name etc) should get blank except for student id field.
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement


Test Case Id
3
Test Date
12/28/2007
Test Point
Admission section form
Pre-Requisite
2
Use Case Name
2.2
Test Engineer
Ahmed Zeb
Description
Save button again after filling the values in fields
Test Case Type
Functional
Steps Performed
Go to Desktop.
2. Open the Application
3. Click Admission section.
4. Click the Add button on top.
5. Click the Add Button again after filling the values in the form.
Expected Output
Message box should be displayed “Please save the exisisting values”.
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement


Test Case Id
3.1
Test Date
12/28/2007
Test Point
Admission section form
Pre-Requisite
2
Use Case Name
2.3
Test Engineer
Ahmed Zeb
Description
Next Button
Test Case Type
Functional
Steps Performed
Go to Desktop.
2. Open the Application
3. Click Admission section.
4. Click the Next button on top.
5.When the user continuously clicking next button and reach last record and then click next button again.
Expected Output
Message box should be displayed “This is Last Record ”.
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement



Test Case Id
3.2
Test Date
12/28/2007
Test Point
Admission section form
Pre-Requisite
2
Use Case Name
2.4
Test Engineer
Ahmed Zeb
Description
First Button
Test Case Type
Functional
Steps Performed
Go to Desktop.
2. Open the Application
3. Click Admission section.
4. Click the First button on top.
5.Click the First Button to check the First record if the user again click the First button.
Expected Output
Message box should be displayed “This is The First Record ”.
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement





Test Case Id
3.3
Test Date
12/28/2007
Test Point
Admission section form
Pre-Requisite
2
Use Case Name
2.4
Test Engineer
Ahmed Zeb
Description
Last Button
Test Case Type
Functional
Steps Performed
1.Go to Desktop.
2. Open the Application
3. Click Admission section.
4. Click the Last button on top.
5. Click the Last Button to check the Last record if the user again Click the Last Button.
Expected Output
Message box should be displayed “This is Last Record ”.
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement









Test Case Id
4
Test Date
12/28/2007
Test Point
Examination section form
Pre-Requisite
2
Use Case Name
4.1
Test Engineer
Ahmed Zeb
Description
Previous Button
Test Case Type
Functional
Steps Performed
1.Go to Desktop.
2. Open the Application
3. Click Examination section.
4. Click the Previous button on top.
5. When the user continuously clicking Previous button and when reach first record and when again click Previous button.
Expected Output
Message box should be displayed “This is The First Record ”.
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement





Test Case Id
4
Test Date
12/28/2007
Test Point
Examination section form
Pre-Requisite
2
Use Case Name
4.2
Test Engineer
Ahmed Zeb
Description
Update Button
Test Case Type
Functional
Steps Performed
1.Go to Desktop.
2. Open the Application
3. Click Examination section.
4. Click the Update Button on top.
Expected Output
Message box should be displayed “Do you want to Update the Record” and when user click on “yes” Button then he is allow to Update the Record and when user click on “Save” Button to save the record Message box should be displayed “The record which you Update is Saved Successfully ”.
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement






Test Case Id
4
Test Date
12/28/2007
Test Point
Examination section form
Pre-Requisite
2
Use Case Name
4.3
Test Engineer
Ahmed Zeb
Description
Reports Button
Test Case Type
Functional
Steps Performed
1.Go to Desktop.
2. Open the Application
3. Click Examination section.
4. Click the Reports Button on top.
Expected Output
This Button is used when user to see the report of the student and want to make a hard copy of it.
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement



Test Case Id
5
Test Date
12/28/2007
Test Point
Examination section form
Pre-Requisite
2
Use Case Name
5.1
Test Engineer
Ahmed Zeb
Description
Exit Button
Test Case Type
Functional
Steps Performed
1.Go to Desktop.
2. Open the Application
3. Click Examination section.
4. Click the Exit Button on top.
Expected Output
This Button is used when user want to Exit from the Existing Form.0…….
Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement



Test Case Id
6
Test Date
12/28/2007
Test Point
Employees section form
Pre-Requisite
2
Use Case Name
5.1
Test Engineer
Ahmed Zeb
Description
Exit Button
Test Case Type
Functional
Steps Performed
1.Go to Desktop.
2. Open the Application
3. Click Employees section.
4. Click the Search Button on top.
Expected Output
This Button is used when user want to search the record of any employee.

Result (Pass/Fail)
PASS
Observations/
Suggestions for Improvement