Thks for the information about Testcase template

thanx to all..

Test plan are the documents made by the tester by refering the Business Requirement Specification and Functional Requirement Specification. It specify all the guidelines that are needed to perform the testing activities.

According to IEEE standards:

Title: Name of the test plan


Revision History : Records all the changes made to the test plan


Table of Contents: List the chapters inside the Test plan


Purpose of the document and Intended audience: Purpose is to understand the objective, scope of the test plan and who so ever refers to the test plan becomes the audience


Feature to be tested and not to be tested : it specifies for that particular release what are the items that are to be tested and what we can left for the next release


Suspension and Restart criteria: it specifies the conditions that stops the testing and conditions that restart it.


Tracebility Matrix: its a document used to map the test cases with Use cases


Related Documents: it specifies the documents that you refer while making test cases.


Test scenario: it specifies all the functionalities of the application that need to be tested


Enter and ecit criterai: it speicify when to enter and when to exit


Hardware Requirements


Software Requiremets

1.1 purpose of the document 1.2 scope of stp 1.3 acronyms and definitions 2 scope of testing 2.1 features to be tested 2.2 features not to be tested 3 test environment 3.1 hardware 3.2 software 4 test strategy 4.1 testing process 4.2 build process 4.3 type of testing 5 defect tracking 6 resource management 6.1 roles and responsibilities 6.2 test schedule 7 assumptions 8 risks management 9 dependencies 10 test deliverables 11 software test plan updation appendix 1: defect classification appendix 2: defect lifecycle and stakeholders:

does any one have a test plan template.?

hai,

You can view test plan template here
http://www.geekinterview.com/talk/14...-template.html (Test Plan Template)

Thanks
Deepa

1. Introduction description of this document related documents schedule and milestones 2. Resource requirements hardware software o test tools staffing o responsibilities o training 3. Features to be tested / test approach new features testing regression testing 4. Features not to be tested 5. Test deliverables 6. Dependencies/risks 7. Entrance/exit criteria

1. Introduction description of this document related documents schedule and milestones 2. Resource requirements hardware software o test tools staffing o responsibilities o training 3. Features to be tested / test approach new features testing regression testing 4. Features not to be tested 5. Test deliverables 6. Dependencies/risks 7. Entrance/exit criteria