Software TestPlan

8/3/2019 Software TestPlan

http://slidepdf.com/reader/full/software-testplan 1/27

Software Test Plan

Version 1.0

For

Automation of Placement Cell

Prepared by

Name : Zafaryab Haider Nikhil Singh

Faculty no : 11PEM364 11PEM363

Submitted in partial fulfillment of the requirements of M.Tech Project

October 19, 2011



Table of Contents

Contents

1. Revision History ..................................................................................................................... 3 2. References ............................................................................................................................... 3 3. Introduction ............................................................................................................................. 3 4. Test Items................................................................................................................................. 3 5. Software Risk Issue ............................................................................................................... 3 6. Features to be Tested ........................................................................................................... 4 7. Features not to be Tested .................................................................................................... 4 8. Approaches ............................................................................................................................. 4

8.1 Content Testing: ................................................................................................................ 4 8.2 User Interface Testing ....................................................................................................... 5 8.3 Navigation Testing ............................................................................................................ 5 8.4 Function Testing ............................................................................................................... 5 8.5 Configuration Testing ....................................................................................................... 5

9. Item Pass / Fail Criteria ........................................................................................................ 6 10. Test Deliverables ................................................................................................................. 6 11. Remaining Test Tasks........................................................................................................ 6 12. Environmental Needs ......................................................................................................... 6 13. Staffing and Training Needs............................................................................................. 6 14. Planning Risks and Contingencies ................................................................................ 6 15 .Test Cases............................................................................................................................. 6 16. Glossary....................................................................... Error! Bookmark not defined.



1. Revision History

Date Reason For Changes Version

20/10/2011 Initial version of the document. 1.0

2. References

The following documents were used as sources of information for the test plan: a) Placement Cell website (www.zhcetplacement.com) SRS, Version 1.2

b) Placement Cell website (www.zhcetplacement.com) SDD, Version 1.1

3. Introduction

Purpose: The test plan document describes the outputs that are obtained at various legal andillegal inputs. It employs appropriate strategies and methodologies to plan, organize, execute and

manage testing of software projects.

Scope: The project will have three levels of testing, Unit, System/Integration and Acceptance.

Unit testing will be discussed in approach section. System testing will be performed after all the

tested units are integrated. Then it will be reviewed with respect to the SRS.

4. Test Items

All items that make up the system will be tested during the system test.The following documents will provide the basis for defining correct operation:

a) Placement Cell website (www.zhcetplacement.com) SRS, Version 1.2

b) Placement Cell website (www.zhcetplacement.com) SDD, Version 1.1

The items to be tested are as follows:a) Contents of every module in the application.

b) Interfaces of the modules.

c) Navigations between the web pages.Since it won’t have multiple versions, thus complete features of the website will be checked at once.

5. Software Risk Issue

There are several parts of the project that have direct impacts on the process and must be

checked as well. Some of the critical areas are:a) Have the customer been fully involved in the definition of the requirements and those

requirements are clear to developer.

b) Identify if any misunderstanding has occurred.c) Remove all unclear requirements.

http://www.zhcetplacement.com/


















d) The PC based software package installed at each location (both client & server).

e) Backup and Recovery of the files, local databases must be carefully checked.f) The ability to restart the application in the middle of the process is a critical factor to

application reliability. This is especially true in the case of the transmission files as once

the data is pulled from the databases; it is no longer available there and must be protected

locally.g) Database security and access must be defined and verified, especially for files shared

between the administrator/user for management and accessing/searching the database.

h) Make sure that none of the Government policies are broken.

6. Features to be Tested

The following is a list of the areas to be focused on during testing of the application.

Content Testing

Database Testing

Interface Testing Navigation testing

Function Testing

7. Features not to be Tested

Viewing Statistics, Company visiting will have no effect no network and databases. So, neitherwill it be checked nor anything related to it will be checked.

Retrieval from database will not be checked as it will solely depend on the query generated.

8. Approaches

8.1 Content Testing:Content Testing Objectives

1) Tests to uncover syntactic errors in text base documents, graphical representations.

2) Tests to uncover semantic errors in any content object presented as navigation occur.3) Tests to find error in the organization what structure of content that is presented to the end-

user. Database Testing

1) Tests to uncover errors made in translating the user’s request into a form that can be processed

by the DBMS.2) Tests that uncover errors in communication between the web application and the remote

database (server-side) should be developed.3) Tests that demonstrate the validity of the raw data received by the server should be developed.

4) A series of tests should be designed to uncover errors in the content object format and test

compatibility with different client environment configurations.

8.2 User Interface Testing:



Interface Testing Strategy

1) Tests to uncover errors related to specific interface mechanisms.

2) Tests to uncover errors in the way the interface implements the semantics of navigation, webapplication functionality, or content display.

3) The interface is tested within a variety of environments to ensure that it will be compatible.Testing Interface Mechanisms

1) Each navigation link is tested to ensure that proper content object or function is reached.

2) Tests are performed to ensure that labels correctly identify fields within the form and that

mandatory fields are identified visually for the user.Usability Tests

Tests required evaluating the degree to which users can interact effectively with the web

application and how it guides user’s actions and enforcing a consistent interaction approach.

8.3 Navigation Testing:

Tests required ensuring the navigation mechanisms and the functions associated with it. It

includes two features:

1) Navigation syntax testing2) Navigation semantic testing

8.4 Function Testing:

This testing focuses on a set of tests that attempt to uncover errors in the developed webapplication functions. It includes all input values and the expected output to be provided by the

component.

8.5 Configuration Testing:Server-side Issues

Tests required ensuring the configuration of the server which can support the web application

without any error.Client-side Issues

On the client side, configuration tests focus on web application compatibility withconfigurations.

9. Item Pass / Fail and Suspension Criteria

The test process will be completed once the initial set of test case has successfully passed. When

the administration staff is satisfied that the data is correct the initial set of clients will be set toactive.

At this point the next set of test case will begin the parallel process, if not already doing so, tocheck the proper integrated functioning. If cases run smoothly without any contradiction then itwill pass.

When a test case is ready, and their data is verified, they will then be passed.

If any unpredictable result is observed then testing can be suspended as such result may lead tosystem failure. Testing after a truly fatal error will generate conditions that may be identified as

defects but are in fact ghost errors caused by the earlier defects that were ignored.



If any test case, on which several other cases are dependent, goes wrong then the testing should

be stopped.

10. Test Deliverables

These deliverables fall into three basic categories: Documents, Test Cases / Bug Write-ups, andReports. These deliverables are:

Test plan

Test cases

Test design specifications.

11. Remaining Test TasksN\A

12. Environmental NeedsN\A

13. Staffing and Training NeedsN\A

14. Planning Risks and ContingenciesN\A

15 .Test Cases1. Test Module Name: HOME

1.1 Test Case: Verify connection

Precondition: There is no connection with the web portal

Input data: URL to browser

Expected result: The connection to the home page.

1.2 Test Case: Clicking on “Home” page link

Precondition: The connection is established

Input data: link selection

Steps: Check for the presence and location of logo, buttons and other images.Check for the spellings, semantics and functions.

Expected result: Corresponding Page is opened

1.3 Test Case: Clicking on “Login” button.


Input data: Username/Password field is empty

Steps: Check for the presence and location of logo, buttons and other images.

http://www.gerrardconsulting.com/tkb/guidelines/ieee829/main.html#12










Check for the spellings, semantics and functions.

Expected result: Display “Invalid Entry” and remain on the same page.



Input data: Username/Password is wrongSteps: Check for the presence and location of logo, buttons and other images.


Matches the password entered, from the database corresponding to the username.

Expected result: Display “USERNAME/PASSWORD DOESNOT MATCH” andremain on the same page.



Input data: Username/Password is correct.


Check for the spellings, semantics and functions.Matches the password entered, from the database corresponding to the username.

Expected result: Directs PO/Student to his/her page respectively.

1.6 Test Case: Clicking on “Registration” page link





Expected result: Corresponding Form is displayed to receive data.

1.7 Test Case: Clicking on “Events” page link






1.8 Test Case: Clicking on “Eligible Candidates” page link





Expected result: Corresponding List is displayed.

1.9 Test Case: Clicking on “GenStats” button link








1.10 Test Case: Clicking on “PreviousRecords” page link




Expected result: Year wise display of previous records.

1.11 Test Case: Clicking on “About us” page link






1.12 Test Case: Clicking on “Contact us” page link Precondition: The connection is established





2. Test Module Name: EVENTS

























2.5 Test Case: Clicking on “Stats” page link








Input data: link selectionSteps: Check for the presence and location of logo, buttons and other images.









2.8 Test Case: Clicking on “Contact us” page link






3. Test Module Name: EligibleCandidates















Precondition: The connection is establishedInput data: link selection








Check for the spellings, semantics and functions.Expected result: Corresponding List is displayed.


























4. Test Module Name: Stats












4.3 Test Case: Clicking on “Events” page link Precondition: The connection is established





































5. Test Module Name: PreviousRecords

















































6. Test Module Name: ABOUT US
















































7. Test Module Name: CONTACT US















Precondition: The connection is establishedInput data: link selection

































8. Test Module Name: REGISTRATION

8.1 Test case A required field is left blank

Precondition: The connection is established.



Expected result: error message is generated to fill the “REQUIRED FIELD SHOULD NOT

BE LEFT BLANK”

8.2 Test case All entries are filled and click “SUBMIT” button.





Expected result: a message is generated “ACCOUNT CREATES SUCCESSFULLY”

8.3 Test case password and confirm password does not match





Expected result: a message is generated “PASSWORD AND CONFIRM PASSWORD DOES

NOT MATCH”

8.4 Test case Clicking “reset” button.




Expected result: All the text fields are cleared.

9. Test Module Name: PO_HOME

9.1 Test case : Clicking on “Home” page

Precondition: The connection is established. PO must be logged in.





9.2 Test case : Clicking on “Request” page







9.3 Test case : Clicking on “SetEligibilty” page




Check for the spellings, semantics and functions.Expected result: Corresponding Page is opened

9.4 Test case : Clicking on “EventUpdate” page





9.5 Test case : Clicking on “MaintainStudentDetails” page

Precondition: The connection is established. PO must be logged in.Input data: link selection



9.6 Test case : Clicking on “GenStats” button





9.7 Test case : Clicking on “LogOut” button


Input data: Button click


Expected result: PO session is ended and display “SUCCESSFULLY LOGGED OUT”..

10. Test Module Name: Request














10.3 Test case : Clicking on “SetEligibilty” page Precondition: The connection is established. PO must be logged in.




















10.7 Test case : Clicking on check button


Input data: Student Details



Verified Students are checked.

Expected result: Entry is made in Database.

10.8 Test case : Clicking on check button


Input data: Wrong Student Details





Students with wrong details are unchecked.

Expected result: Ignore students



Input data: Button click Steps: Check for the presence and location of logo, buttons and other images.



11. Test Module Name: SetEligibility






































Input data: no entry in text field


Expected result: error message is generated to fill the “RE QUIRED FIELD SHOULD NOT

BE LEFT BLANK”

11.8 Test case All entries are filled and click “SUBMIT” button


Input data: entries in text fields


Expected result: a message is generated “ ELIGIBILTY SET ”.





Expected result: All the text fields are cleared.







12. Test Module Name: EventUpdate


Precondition: The connection is established. PO must be logged in.Input data: link selection











12.3 Test case : Clicking on “SetEligibilty” page Precondition: The connection is established. PO must be logged in.






















Input data: no entry in text field



Expected result: error message is generated to fill the “REQUIRED FIELD SHOULD NOT

BE LEFT BLANK”

12.8 Test case All entries are filled and click “SUBMIT” button


Input data: entries in text fields



Expected result: a message is generated “UPDATED”.







Check for the spellings, semantics and functions.Expected result: All the text fields are cleared.






13. Test Module Name: MaintainStudentDetails 13.1 Test case : Clicking on “Home” page











































14. Test Module Name: GenStats












































15. Test Module Name: STUDENT_HOME


Precondition: The connection is established. STUDENT must be logged in.





15.2 Test case : Clicking on “Apply” button


Input data: click on Apply button


Expected result: Students applies for the respective company.

15.3 Test case : Clicking on “Practice” page







15.4 Test case : Clicking on “PreviousRecords” page












15.6 Test case : Clicking on “Stats” button





15.7 Test case : Clicking on “AboutUs” page






15.8 Test case : Clicking on “ContactUs” page












16. Test Module Name: Practice









16.2 Test case : Clicking on “Practice” page

Precondition: The connection is established. STUDENT must be logged in.Input data: link selection




16.3 Test case : Clicking on “PreviousRecords” page








Input data: “Click on ProfileUpdate”



16.5 Test case : Clicking on “Stats” button






16.6 Test case : Clicking on “AboutUs” page





16.7 Test case : Clicking on “ContactUs” page







16.8 Test case : Clicking on “Score” button


Input data: button click



Expected result: Display “UR SCORE IS = ___”







17. Test Module Name DATABASE

17.1 Test case: Test the entriesPrecondition: The connection is established

Input data: database selection

Steps: Check for the presence of valid entries.


Expected result: all entries must be same as given by the user.

17.2 Test case: Test the field name


Input data: database selection

Steps: Check for the presence of valid fields.


Expected result: all entries must be same as mentioned in the design document.

17.3 Test case: New entries are given into database





Check for the type of data entered and the type of data allowed

Expected result: changes must be displayed at job seekers home page.

16. GlossaryAll terms and acronyms used in the document, and testing are general & have their own

meanings.



Software TestPlan

Documents

Transcript of Software TestPlan