Test Plan in Software Testing

Test Plan

1. Introduction:

1.1 Objective : Our software is “test me .in” which provide a platform through which one will improve their skills either the logical skill, analytical skill, IQ test and the technical abilities .this product will be mainly used by two kinds of users either general users or other company for their references. It will be helpful to conduct interviews. To make Test Plan we follow IEEE Standards. The main reason behind testing is to detect bugs, to reduce the risk associated with residual bugs, to make a quality product, to save time, to save budget, to give the good product in competitive environment.

1.2 Scope: The system is highly flexible and well efficient for on line interviews and skill test. The key focus is given on data security; project is on line and will be transfer in network. Changes can be done very easily using the facility in DOT NET and SQL .It is suitable for all levels of peoples whether general users or any organization. it provide proper details about skill test i.e. by following what steps the person is able to test ourselves. Software company can also take advantages from this product. It can also provide voice test for call centers candidates. It generates report of skill test result. It provides proper time management by providing fixed duration for test.

1.3 Testing Strategies: We should use some security features to stop an unauthorized person to access it.

We will perform these testing:
a. performance testing: to check the execution time
b. regression testing: repeat test cases on software to find bugs
c. interface testing: Integrated testing +gui testing
d. Functional testing: to test the basic fun.
e. user friendliness testing: font, colors, design, should be proper
f. smoke testing: h/w should be friendly with s/w
g. recovery testing: after integrity failure of the software system should be recover not hang
h. adhoc testing: test the s/w randomly

1.4 Reference: This is the part of document which tells about references .The following on line references is–www.brainbench.com

2. Test Items and Test Approaches

2.1 Test Items: Test Items are those items in which we define how many modules and sub modules will be used in the project. There are two type of test items are used in this project.

1) Admin Module
2) User Module

1) Admin Module is divided in to different type of Sub Modules

a) Create Admin Member
b) Change password
c) Add Exam Subject
d) Add Test Skill type
e) Add Exam Question


a) Create Admin Member
In this sub module you can create, edit as well as update the Login Name and Password

b) Change Password
In this sub module you can change your Admin Password.

c) Add Exam Subject
In this sub module you can add, delete and cancel the selected exam subject

d) Add Test Skill Type
In this sub module you can add test name as well as update, edit and cancel the select test type

e) Add Questions
In this sub module you can easily add the questions and answer for user with the help level of exam subject name, test plane name and questions type

2) User Module is divided in to different type of Sub Modules

a) About Us
b) Products and Services
c) Partners
d) Profiles
e) Common Questions
f) Payment Options
g) Test Your Skills
h) Member Login


a) About Us
This Sub Module Contains details of the company

b) Products and Services
This Sub Module gives brief information about the products and services of the company

c) Partners
This Sub Module Contain partnership deed (agreement), terms and conditions between the partners

d) Profiles
This Sub Module contains the work detail of the company like capacity, infrastructure and also tell us about the company past experiences

e) Common Questions
This Sub Module Contain different type common Questions

f) Payment Option
This Sub Module contains different type of payment modes like Debit Card, Credit Card, Demand Draft and Cheque.

g) Test Your Skills
This Sub Modules contains different type of test skills for general users like IQ Test, Personality Test, Fun IQ Test and Aptitude Test.

h) Member Login
This Sub Module Contains Login Name and Password.

2.2 Test Approaches:In Test approaches we define what type of testing will be used for which type of module.

we use different types of testing approaches like

1) URL Testing
2) Form Testing
3) Functional Testing
4) Usability Testing
5) Link Testing
6) Navigation Testing
7) Page Content Testing
8) Regression Testing
9) Security Testing

3. Features to be tested include:

1. Display color of website
2. Tab key functionality on website
3. Tool tip
4. Sound
5. Accessibility of all links and clickable image

3.1 Admin Homepage:
1. Validation of Admin Login
2. Create Admin member
3. Change Password
4. Add Exam subject
5. Add test skill type
6. Add question

3.2 Main Index Homepage:

1. Validation of member Login
2. Checking of Test skills such as IQ tests, Personality test, Aptitude test, Voice skill test etc.
3. Signup user (Registration form)
4. Testing of links including Home, About us, Product and services, Partners, Profiles, Payment options, Contact us.

4. Feature not to be tested:

4.1 Main Index Homepage:
The following links are not mandatory to be tested
1. Book mark link.
2. Contact us.
3. Profile

The following fields in the registration form are not mandatory to be tested
1. Last Name.
2. Calling name
3. Address line 2.
4. Phone No.

5. Pass and Fail Criteria:

There are three types of criteria
1. Suspension criteria
2. Resuspension criteria
3. Approval criteria.

A. Suspension criteria: In Suspension criteria if there is a major bug than the process will be suspended for some period of time.
B. Resumption criteria: In resumption criteria when the bug is solved, then the process will be completed in the estimated time.
C. Approval

6. Environment Requirement

6.1 Software Requirements:


Operating System : Windows 98, 2000, ME, XP, NT
Web Browser : IE4 or Netscape 4x or upwards
Development tools : ASP.NET, C#, JavaScript, HTML, DHTML
Datatbase : Microsoft SQL Server 2000

6.2 Hardware Requirements:

Processor : Pentium 3,500 MHz (or above).
RAM : 128 MB (or above).
HDD : 20 GB (or Above).
Front End: For Designing ASP.net required at Front End but for Implementation only .net framework is sufficient.
Back End: SQL SERVER-2000 (Back End)

6.3 Tools
We are not using any type of tool in this application.


6.4 Security Requirements :

1. All Special facilities are only available to authenticated users. It means the user should be login through proper login id and password.
2. The system should protected by Antivirus.
3. The System should be connected with firewall.
4. The database should be connected properly and secured from unauthorized user.
5. The database must be follow integrity rule.



6.5 Risk & Assumptions :

The main Risks are
1: The hardware and software configuration are not match with the client site.
2: If suddenly changes are made in client requirement, the changes requirement must known by all the tester means all the information are available to all tester side by side.
3: The users do not have the proper knowledge of internet technology.
4: The network must be connected properly

The main assumptions are

1. Sql server(version2000) are already install in the
system.
2. The user must be familiar with internet technology.
3. Hardware and software configuration should be installed in the system.

7. Testing Process:

7.1 Test Deliverables:
• Software Requirement Specification
• Test Plan
• Test Cases
• Execute Test Cases
• Report Analysis
• Bug Analysis
• Bug Report

7.2 PLAN APPROVAL:

APPROVED BY: PROJECT LEADER

DATE:

SIGNATURE: