anand

• May 15th, 2006

 

test plan is a documents which consist of details of application, its ample scope, objective and detail information of the features or modules and it explains the flow of application and gives all the materials to prepare a detailed test cases

raghuramsuravarapu

 Profile Answers by raghuramsuravarapu Questions by raghuramsuravarapu

• Jun 17th, 2006

 

I think there is a lot of confusion between a test plan and test case.

Test Plan:Test Plan is a document consisting of scope,objective,approach,schedule of the testing activities for the specific project.It mainly consist of who to test?,when to test?,why to test?,where to test?

IEEE 829-1983 standard test plan consists of different fields like,Test plan ID,Introduction,Test Items,Features to be tested,Features not to be tested,Testing tasks,Schedules,Tranining and Environmental needs,Test Approach,Deliverables,Item pass/fail criteria,test suspension criteria,human resources.

For login screen,test plan can be created.But it is not important to create test plan for login screen alone.A test plan will be created for the whole project.For Login screen,test case's can be created and executed to find defects.

Test case is a document consists of Serial Number,Steps Description,Expected,Actual,Test Data,etc.A test case is derived from SRS,FDS,Use Case's etc.For login screen ,A user interface test case can be created to check the spelling and location of user name,password,text boxes and for buttons ok and cancel and any remaining items on that screen.

Input domain test cases can be created for User Name and Password.Techniques like equivalence partitioning and boundary value analysis is used to create test data.Test data is divided into valid boundaries and invalid boundaries.For all valid boundaries positive tests and for each invalid boundary negative test can be created.

sudhakar2068

 Profile 

• Sep 8th, 2006

 

After completion of testing team formation and Risks analysis, Test lead category people are preparing test plan documents. In this Test lead is developing masterplan and then goes to detailed plan.Test plan inculdes what to test ? How to test ? who to test ? when to testing?

Test plan ID.

Introduction.

Test Items.

Features to be tested.

Features not to be tested.

What to test ?

Test approach.

Test environment.

Entry criteria.

Suspension criteria.

Exit criteria.

Test deliverables.

How to test ?

Staff and Training needs.

Responsibilites.

Who to test ?

Schedule.

when to test?

Risks and Assumption.

Purpose:Short sentence or two about the aspect of the system is being tested. If this gets too long, break the test case up or put more information into the feature descriptions.

Prereq:Assumptions that must be met before the test case can be run. E.g., "logged in", "guest login allowed", "user testuser exists".

Test Data:List of variables and their possible values used in the test case. You can list specific values or describe value ranges. The test case should be performed once for each combination of values. These values are written in set notation, one per line. E.g.: loginID = {Valid loginID, invalid loginID, valid email, invalid email, empty}

password = {valid, invalid, empty

}

 steps: Steps to carry out the test. See step formating rules below

 

 1.visit the login page.

 2.enter userID .

 3.enter password .

4.click login .

5.see the terms of use page .

6.click agree radio button at page bottom .

7.click submit button .

8.see PersonalPage.

9.verify that welcome message is correct username.

 sudhakar kolla

If you are having any doubt can ask me.

My Email:Kollasudhakar2005@yahoo.co.in

My number :09819859346

 

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• May 7th, 2009

 

TEST PLAN is a document which defines basically..
1) what to test?
2) how to test ?
3) when to test ?
4) who to test?

Documentation specifying the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, responsibilities, required, resources, and any risks requiring contingency planning
Test lead prepares this document. It is normally defined in IEEE829 format which is as follows
1 ) Test plan ID : Unique number or name
2) Introduction : About project
3) Test Items: Names of all modules in the project.
4) Features to be tested :
5)Features not to be tested:
6) Tessting approach: finalized TRM, selected testing techniques
7) Entry Criteria : When testing can be started
8) Exit Criteria : when testing can be stopped
9)Fail or Pass criteria:
10) Test Environment : The environment where the test is to be carried out.
11) Test Delivarables:
12) Staff and training
13) Roles and Responsibilities
14 ) Project starting and End dates
15) Risks and migitations.

pratheba86

 Profile Answers by pratheba86 

• Jun 21st, 2009

 

Test Plan is a document which describes the scope, test schedules, test items, features to be tested/features not be tested, man power required, tester independence.
It is a document prepared by the test lead.

mithr17

 Profile Answers by mithr17 

• Oct 20th, 2011

 

I agree many newbies confuse test plan with test case.
Test plan is used to document the over all QA efforts strategy. Test case on the other hand details the steps among other things to test a requirement or a piece of functionality in an application.