hi
I know test plans differ from projects to projects ....
but was just wondering if I can get a template for test plan which I can refer while writing my first test plan...
I have got withme the general template that I got after googling...
If anyone has got template...help me out...
thanks

Test Plan Format:
Test Plan ID: Unique number of name for future reference.
Introduction: About Project & Testing
Test Items: Names of all modules in that project
Features to be Tested: Names of modules to prepare test cases for testing.
Features not to be Tested: Names of modules to copy test cases from test case data base.
3, 4, 5 specifies "what to test?"
Approach: Selected list of test factors by Project Manager and select list of testing techniques to be applied.
Entry Criteria:
Testing environment establised
Test cases prepared
Received build from developers
Suspension Criteria:
Testing environment is not working due to repair
sudden changes in customer requirements
pending defects are more
Exit Criteria:
all modules tested
all types of tests applied
all major bugs resolved
Test Environment: Required software and hardware to conduct testing on this project including testing tools.
Test Deliverables: List of documents to be prepared by testing engineers.
6 to 11 specifies "how to test?"
Staff & Training Needs: Names of selected test engineers and required number of training sessions.
Responsibilities: Work allotments to above selected test engineers
12 & 13 specifies "who to test?"
Schedule: Dates and time
14 specifies "when to test?"
Risks & Mitigation: The list of risks and solutions to overcome.
Approvals: Signatures of test lead and project manager.

Hi all!
can u please tell me what is Agile testing?
thanx in advance

Hi Team,

I Read Article on Agile Testing please have a glance to sharpen the concept on Agile testing.

Testing from the beginning of the project and continually testing throughout the project lifecycle is thebasis of agile testing. If we can work with the customer to help him specify his requirements in terms oftests it makes them completely unambiguous, the tests either pass or they don’t.

If our coders only writecode to pass tests, we can be sure of one hundred percent test coverage. Most of all, if we keep ourtesters, developers and customers (or customer representatives) in constant face-to-face communicationwith each other, we can eradicate most of the errors caused by us climbing the ladder of inference.

Breaking our projects into smaller chunks of work and iterating them will give us frequent feedback on the current state of the project.There are many teams now using agile testing techniques to improve the quality of their products andhaving great success.

There is some investment in training required and changes to the workspace are necessary to allow customers, testers, and developers to work side-by-side but these are a small price to pay for the advantages gained.The most difficult thing for most teams is shifting the perception of the test team competing with thedevelopers where their focus is detecting faults and preventing poor quality products from being released.The new, agile testing, paradigm is the test team collaborating with the developers to build quality in from the start and release robust products that deliver the best possible business value for the customer.

Hope this helped

Regards,
Sridevi

Just to start with, you can try with the simple test plan template given below-

-----------------------------------------



1. Purpose
2. Outline
2.1 Test Plan Identifier
2.2 Introduction
2.3 Test Items
2.4 Features to be tested
2.5 Features not to be tested
2.6 Approach
2.7 Item Pass / Fail Criteria
2.8 Suspension Criteria and Resumption Requirements
2.9 Test Deliverables
2.10 Testing Tasks
2.11 Environmental Needs
2.12 Responsibilities
2.13 Staffing and Training Needs
2.14 Schedule
2.15 Approvals

I have included the test plan template in this post..
http://software-testing-askme.blogsp...-template.html

You can note the detail points under each test plan step..

If you want sample Test plan query me on
shindevijaykr@gmail.com

a software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. A test plan states what the items to be tested are, at what level they will be tested, what sequence they are to be tested in, how the test strategy will be applied to the testing of each item, and describes the test environment. A test plan should ideally be organisation wide, being applicable to all of an organisations software developments. The objective of each test plan is to provide a plan for verification, by testing the software, the software produced fulfils the functional or design statements of the appropriate software specification. In the case of acceptance testing and system testing, this generally means the functional specification. The first consideration when preparing the test plan is who the intended audience is – i.e. The audience for a unit test plan would be different, and thus the content would have to be adjusted accordingly. You should begin the test plan as soon as possible. Generally it is desirable to begin the master test plan as the same time the requirements documents and the project plan are being developed. Test planning can (and should) have an impact on the project plan. Even though plans that are written early will have to be changed during the course of the development and testing, but that is important, because it records the progress of the testing and helps planners become more proficient.
1. Test plan identifier
2. References
3. Introduction
4. Test items
5. Software risk issues
6. Features to be tested
7. Features not to be tested
8. Approach
9. Item pass/fail criteria
10. Suspension criteria and resumption requirements
11. Test deliverables
12. Remaining test tasks
13. Environmental needs
14. Staffing and training needs
15. Responsibilities
16. Schedule
17. Planning risks and contingencies
18. Approvals
19. Glossary

__________________
Brijesh Jain
brijesh.tester@gmail.com
http://softwaretestingexpertise.blogspot.com

Test plan: a software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. Objective product overview relevant document, standards, legal requirements traceability requirement overall project organization and personnel contact-info/responsibility assumption and dependencies risk analysis testing priorities and focus scope and limitation test outline: decomposition of test approach by test type, feature, functionalities, modules etc. Test environment configuration management process test tools to be used including version, patches etc problem tracking and resolution project test metrics entry and exit criteria test suspension and restart criteria. Personnel allocation and pertaining needs outside test organizations to be utilized with purpose, responsibilities, deliverables etc. Etc. Open issues

Thanks guys! Ima new member. Even i am looking for all agile testing... Good answers.

i know dat test paln templates r differs from projects to projects.can u send me a sample thats y i understand to write test plan first time.

Test Plan is the doc. how toperform complete testing onan app in more efficient, effective and optimize way.
Contents of test Plan:-
1.Identifier
2.Introduction
3.Test Items
4.Function tobe tested
5.Function not to be tested
6. Item Pass/Fail
7.Test Approach
8.Test Environment
9.Test Schedule:
10.Test Stragegy
11.Roles and Responsibilies
12.Staffing and Training
13.Suspension and Resumption criteria
14.Test Approvals
15.Test Deliverables
16.Test Tasks

yes rose,testplan varies from project to project and from company to company..most of the time u find same common terms are used everywhere.

i am enclosing an attachment of testplan..just check this.

Hi Gouthami ,

Still the attachment is missing. I think you have some problems regarding uploading. Logout and then re login and try uploading it may work.

Table of Contents
1.1 Introduction:
1.2 Scope:
1.3 Features to be tested:
1.4 Features not to be tested:
1.5 Test Strategy
1.5.1 Black box testing:
1.5.2 Smoke/sanity testing
1.5.3 Functional testing
1.5.4 Compatibility testing:
1.5.5 Web testing:
1.5.6 System testing:
1.5.7 Recovery testing:
1.5.8 Security testing:
1.5.9 Load testing:
1.5.10 Volume testing:
1.5.11 Stress testing:
1.5.12 Performance testing:
1.5.13 Retesting
1.5.14 Regression testing
1.5.15 GUI testing
1.5.16 Cofiguration testing
1.5.17 Database testing
1.5.18 Ad-hoc testing
1.5.19 Exploratory testing
1.5.20 User interface testing
2.1 Suspension
2.2 Resumption Criteria:
2.3 Entry criteria
2.4 Exit criteria
3.0 Environment
3.1.1 Workstation
3.1.2 Application Server
3.1.2 Database server
3.2 Software Required
3.3 Roles and Responsibilities:
3.4 Test schedule:
3.5 Deliverables:
3.6 Training plan:
4.1 Risk Management:
4.2 Control Procedure:
4.2.1 Reviews:
4.2.3 Defect Reporting:
4.2.4 Defect Prevention Meeting:
4.3 Dependency:
4.3.1 Personal
4.3.2 Software:
4.3.3 Hardware:
4.3.4 Test Data:
4.4 Approval:

Table of Contents
1.1 Introduction: 5
1.2 Scope: 5
1.3 Features to be tested: 5
1.4 Features not to be tested: 5
1.5 Test Strategy 6
1.5.1 Black box testing: 6
1.5.2 Smoke/sanity testing 7
1.5.3 Functional testing 7
1.5.4 Compatibility testing: 7
1.5.5 Web testing: 7
1.5.6 System testing: 7
1.5.7 Recovery testing: 8
1.5.8 Security testing: 8
1.5.9 Load testing: 8
1.5.10 Volume testing: 8
1.5.11 Stress testing: 8
1.5.12 Performance testing: 9
1.5.13 Retesting 9
1.5.14 Regression testing 9
1.5.15 GUI testing 10
1.5.16 Cofiguration testing 10
1.5.17 Database testing 10
1.5.18 Ad-hoc testing 10
1.5.19 Exploratory testing 11
1.5.20 User interface testing 11
2.1 Suspension 11
2.2 Resumption Criteria: 11
2.3 Entry criteria 12
2.4 Exit criteria 12
3.0 Environment 13
3.1.1 Workstation 13
3.1.2 Application Server 13
3.1.2 Database server 13
3.2 Software Required 13
3.3 Roles and Responsibilities: 14
3.4 Test schedule: 14
3.5 Deliverables: 15
3.6 Training plan: 16
4.1 Risk Management: 16
4.2 Control Procedure: 16
4.2.1 Reviews: 16
4.2.3 Defect Reporting: 16
4.2.4 Defect Prevention Meeting: 17
4.3 Dependency: 17
4.3.1 Personal 17
4.3.2 Software: 17
4.3.3 Hardware: 17
4.3.4 Test Data: 17
4.4 Approval: 18

Test plan template, based on ieee 829 format test plan identifier (tpi). References introduction test items software risk issue features to be tested features not to be tested approach item pass/fail criteria entry & exit criteria suspension criteria and resumption requirements test deliverables remaining test tasks environmental needs staffing and training needs responsibilities planning risks and contingencies approvals