Sample Test Plan Document with Examples

By Swati

By Swati

I’m Swati. I accidentally started testing in 2004, and since then have worked with at least 20 clients in 10 cities and 5 countries and am still counting. I am CSTE and CSQA certified. I love my job and the value it adds to software…

Learn about our editorial policies.
Updated May 9, 2025
Edited by Vijay

Edited by Vijay

I'm Vijay, and I've been working on this blog for the past 20+ years! I’ve been in the IT industry for more than 20 years now. I completed my graduation in B.E. Computer Science from a reputed Pune university and then started my career in…

Learn about our editorial policies.

Do you wish to learn & download the Sample Test Plan? This tutorial is a perfect guide to those who have requested a Test Plan example.

In our previous tutorial, we have outlined the Test Plan Index. In this tutorial, we will elaborate on that index with more details.

A Test Plan reflects your entire test schedule and approach.

=> Click Here For Complete Test Plan Tutorial Series

Sample Test Plan Document

TEST PLAN DOCUMENT

This includes the purpose of the Test Plan i.e scope, approach, resources, and schedule of the testing activities. To identify the items being tested, features to be tested, testing tasks to be performed, personnel responsible for each task, the risks associated with this plan, etc.

We have included the link to download a PDF format of this Test Plan example at the end of this post.

Sample Test Plan

(Name of the Product)

Prepared By: 
(Names of those who Prepared)
(Date)

TABLE OF CONTENTS (TOC)

1.0 INTRODUCTION

2.0 OBJECTIVES AND TASKS
2.1 Objectives
2.2 Tasks

3.0 SCOPE

4.0 Testing Strategy
4.1 Alpha Testing (Unit Testing)
4.2 System and Integration Testing
4.3 Performance and Stress Testing
4.4 User Acceptance Testing
4.5 Batch Testing
4.6 Automated Regression Testing
4.7 Beta Testing

5.0 Hardware Requirements

6.0 Environment Requirements
6.1 Main Frame
6.2 Workstation

7.0 Test Schedule

8.0 Control Procedures

9.0 Features to Be Tested

10.0 Features Not to Be Tested

11.0 Resources/Roles & Responsibilities

12.0 Schedules

13.0 Significantly Impacted Departments (SIDs)

14.0 Dependencies

15.0 Risks/Assumptions

16.0 Tools

17.0 Approvals

Note: This Test Plan is provided as a PDF. For maximum flexibility, consider using a web-based test management tool like TestRail to develop your test plans.

Let’s explore each field in detail!!

1.0 INTRODUCTION

It is a summary of the product that is being tested. Outline all the functions at a high level.

2.0 OBJECTIVES AND TASKS

2.1 Objectives
Describe the objectives supported by the Master Test Plan, For Example, defining tasks and responsibilities, a vehicle for communication, a document to be used as a service level agreement, etc.

2.2 Tasks
List all the tasks identified by this Test Plan, i.e., testing, post-testing, problem reporting, etc.

3.0 SCOPE

General: This section describes what is being tested, which is new to all the functions of a specific product, its existing interfaces, integration of all functions, etc.

Tactics: List here how you will accomplish the items that you have listed in the “Scope” section.

For example, if you have mentioned that you will be testing the existing interfaces, what would be the procedures that you would follow to notify the key people to represent their respective areas, as well as allot time in their schedule to assist you in accomplishing your activity?

4.0 TESTING STRATEGY

Describe the overall approach to testing. For each major group of features or feature combinations, specify the approach that will ensure that these feature groups are adequately tested.

Specify the major activities, techniques, and tools that are used to test the designated groups of features.

The approach should be described with sufficient details to permit the identification of the major testing tasks and the estimation of the time required to do each one.

4.1 Unit Testing

Definition: Specify the minimum degree of comprehensiveness desired. Identify the techniques that will be used to determine the comprehensiveness of the testing effort (for example, determining which statements have been executed at least once).

Specify any additional completion criteria (for example, error frequency). The techniques to be used to trace requirements should be specified.

Participants: List the names of the individuals/departments who would be responsible for Unit Testing.

Methodology: Describe how unit testing will be conducted. Who will write the test scripts for Unit Testing, what will be the sequence of events for Unit Testing and how will the testing activity take place?

4.2 System and Integration Testing

Definition: List your understanding of System Testing and Integration Testing for your project.

Participants: Who will be conducting System and Integration Testing on your project? List the individuals who will be responsible for this activity.

Methodology: Describe how System & Integration testing will be conducted. Who will write the test scripts for Unit Testing, what would be the sequence of events of System & Integration Testing, and how will the testing activity take place?

4.3 Performance and Stress Testing

Definition: List your understanding of Stress Testing for your project.

Participants: Who will be conducting Stress Testing on your project? List the individuals who will be responsible for this activity.

Methodology: Describe how Performance & Stress Testing will be conducted. Who will write the test scripts for testing, what would be the sequence of events for Performance & Stress Testing, and how will the testing activity take place?

4.4 User Acceptance Testing

Definition: The purpose of the acceptance test is to confirm that the system is ready for operational use. During the Acceptance Test, end-users (customers) of the system compare the system to its initial requirements.

Participants: Who will be responsible for User Acceptance Testing? List the names of the individuals and their responsibilities.

Methodology: Describe how User Acceptance testing will be conducted. Who will write the test scripts for testing, what will be the sequence of events for User Acceptance Testing, and how will the testing activity take place?

4.5 Batch Testing

4.6 Automated Regression Testing

Definition: Regression testing is the selective retesting of a system or a component to verify that the modifications have not caused unintended effects and that the system or component still works as specified in the requirements.

4.7 Beta Testing

5.0 HARDWARE REQUIREMENTS
Computers
Modems

6.0 ENVIRONMENT REQUIREMENTS

6.1 Main Frame
Specify both the necessary and desired properties of the test environment.

The specification should contain the physical characteristics of the facilities, including the hardware, the communications, and system software, the mode of usage (For Example, stand-alone), and any other software or supplies that are required to support the test.

Also, specify the level of security that must be provided for the test facility, system software, and proprietary components such as software, data, and hardware.

Identify the special test tools that are required. Identify any other testing needs (for example, publications or office space). Identify the source of all needs that are not currently available to your group.

6.2 Workstation

7.0 TEST SCHEDULE

Include all test milestones identified in the Software Project Schedule as well as all item transmittal events.

Define any additional test milestones required. Estimate the time required to complete each testing task. Specify the schedule for each testing task and test milestone. For each testing resource (that is, facilities, tools, and staff), specify its periods of use.

8.0 CONTROL PROCEDURES

Problem Reporting
Document the procedures to be followed when an incident is encountered during the testing process. If a standard form is going to be used, attach a blank copy as an “Appendix” to the Test Plan.

In the event that you are using an automated incident logging system, write the procedures.

Change Requests
Document the process of modifications to the software. Identify who will sign off on the changes and what would be the criteria for including the changes to the current product.

If the changes will affect the existing programs, then these modules need to be identified.

9.0 FEATURES TO BE TESTED

Identify all the software features and combinations of the software features that will be tested.

10.0 FEATURES NOT TO BE TESTED

Identify all the features and significant combinations of features that will not be tested along with the reasons.

11.0 RESOURCES/ROLES & RESPONSIBILITIES

Specify the staff members who are involved in the Test Project and what their roles are going to be (For Example, Mary Brown (User) compile Test Cases for Acceptance Testing).

Identify the groups responsible for managing, designing, preparing, executing, and resolving the test activities as well as related issues.

Also, identify the groups responsible for providing the test environment. These groups may include developers, testers, operations staff, testing services, etc.

12.0 SCHEDULES

Major Deliverables: Identify the deliverable documents.

You can list the following documents:

  • Test Plan
  • Test Cases
  • Test Incident Reports
  • Test Summary Reports

13.0 SIGNIFICANTLY IMPACTED DEPARTMENTS (SIDs)

Department/Business Area Bus. Manager Tester(s)

14.0 DEPENDENCIES

Identify significant constraints on testing, such as test-item availability, testing-resource availability, and deadlines.

15.0 RISKS/ASSUMPTIONS

Identify high-risk assumptions in the test plan. Specify contingency plans for each (for example, delays in delivery of test items might require increased night shift scheduling to meet the delivery date).

16.0 TOOLS
List the Automation tools that you are going to use. Also, list the Bug tracking tools here.

17.0 APPROVALS

Specify the names and titles of all the people who must approve this plan. Provide space for the signatures and dates.

Name (In Capital Letters) Signature Date:

1.
2.
3.
4.


Download: You Can Also Download This Sample Test Plan Template here.

We have also prepared a real Live Project Test Plan from this sample.

You can check and download it in the following tutorials:

  1. Simple Test Plan Template
  2. Test Plan Document (Download)

=> Visit Here For Complete Test Plan Tutorial Series

Was this helpful?

Thanks for your feedback!

Recommended Reading

  • Automation testing proof of concept poc

    In this article, we provide a detailed step-by-step guide on how to Implement Proof of Concept POC Document for Automation Testing. Every organization has different testing processes and procedures. Manual Testing is important and irreplaceable. However, automation is now picking up speed. Introducing automated testing to an organization is a…

  • How To Write Test Strategy Document (With Sample Test Strategy Template)

    Learn To Write Test Strategy Document Efficiently A strategy plan for defining the testing approach, what you want to accomplish, and how you are going to achieve it. This document removes all uncertainty or vague requirement statements with a clear plan of approach for achieving the test objectives. Test Strategy…

  • Software Testing Course Syllabus (1)

    Software Testing Course Syllabus and Training Plan Week 1 Brief introduction to software systems and SDLC Basic concepts Basic Testing Vocabulary Quality Assurance versus Quality Control The Cost of Quality Software Quality Factors How Quality is Defined Why Do We Test Software? What is a Defect? The Multiple Roles of…

  • 7. Find()

    MongoDB Query Document Using Find() with examples: Usage of Find by ID, Find in Array, Find all, Find and Update with examples We learned about ObjectId and its methods within MongoDB in our previous tutorial. In this tutorial, we will learn about the Usage of Find() in MongoDB. Read through…


READ MORE FROM THIS SERIES:



177 thoughts on “Sample Test Plan Document with Examples”

  1. I want to know the following things regarding Test Plan.

    1. When preparation of test plan start?
    2. How the resource, deadline gets estimated? Is there any sceintific approach or any technique used for estimation of all this things?

    Plaes reply on this as I want to understand the testplan in detail.

    Thanks in advance.

    Vishal

    Reply
  2. This is a template, not an example. Examples are meant to be what a finished document might look like, not a list of sections with descriptions of what each one should contain.

    Reply
  3. Hi,

    I wants to know about the Certification in software testing for beginners??

    Its duration,fees,how to apply,which website provide online training for the same.

    Reply
  4. Thank you for such a nice post very helpful.

    But what I want to know who work on Test Plan means Who make it. I am sure this is a work of QA Lead so my question is that WHETHER THE TEST PLAN CONTAINS THE NAME OF QC EXECUTIVE MEANS WHICH SOFTWARE TESTER WILL DO WHAT?

    Reply
  5. hi,
    i am planning to do software testing course from long back.but i am still in confusion which institute will be the best in bangalore. and which institute is giving placement assistance? can i do both manual and automation? what is the difference? pls let me know which will not involve programming. i dont want to get into programming.pls let me know which will suit me. or shall i concentrate only in one course.either manual or automation. thanks.

    Reply
  6. Anyone can help me? i need E Commerce based test plan document. If any one having please send me. this is my email id “panchal_alpesh78@yahoo.co.in”

    Reply
  7. “why we should prepare system & integration test plan?”

    First, System test plan is prepared to make our self ready to prepare the entire system which is being developed from the scratch. System test plan is prepared only if the application or product is completely new. And the application or product need to undergo all type of testing like Functional, Performance, Load, Certification, UAT etc.
    Second, Integration test plan is prepared if a product or application being developed by several team or several developers and if one complete module output is going to be as a input for another module, then this Integration Test Plan will be useful to plan accordingly. So when two systems being integrated the possibilities of issues are like software compatibility, input variable map etc. So these needs to be tested completed when its integrated. Hope its clear now.

    D. Viswanathan
    dviswa@gmail.com

    Reply
  8. Hi am i interesting in s/w testing field doing now manual testing and future which testing useful and weather information sharing for me..

    Reply
  9. Hi Deepesh
    At my company we have worked with various customers, some of whom use traceability matrices, and I don’t think there is any standard format. Some populate tables by hand in MS Word specifications containing requirement tags for example.
    We prefer to auto-generate a requirements traceability matrix using an in-house tool (www.pixref.com), and there are other tools on the market. Our tool trawls through the specification and implementation files searching for requirement tags, and automatically lists which match and which do not.
    Cheers

    Reply
  10. hi vishal

    Here are the answers for your questions

    1)Test plan should be started immediately after the requirements are available. It should be flexible enough so that if the requirements gets changed, then the plan should also be changed accordingly
    2)a)Scheduling is based on the project deadlines.
    b)Resource estimation is based on the project size. In general QA resources are half the development team size. Also you need to prepare Staffing matrix which can give you idea of how many resources are required for a particular module. For example, if there are 3 modules in a project then you can hire 3 persons, one for each module. Similarly you can also categorize by type of testing.

    Reply
  11. “Unit Testing”

    Unit Testing is usually done by developers, they don’t prepare exact test plan for Unit Testing. They will write high level test cases where the scope of the testing will be limited to within their module or functionality undergone changes. Unit Testing/White Box Testing is also done by experienced Test Engineers who has knowledge on coding in the respective platform. Unit Testing executed by testers are mostly to show the defect where exactly in the code it is affected.

    Reply
  12. Hi Satya, Go through requirements and understand the changes in the application. Download a simple test plan template and put your scope and test strategy in that test plan. For preparing test cases, understand the flow of the application and bring in to your imagination for different kind scenarios how application works, and start your test cases putting those scenarios in to as test cases. Let us know any one of here if you need any clarification. Writing test case is an art, build that skill within you and I am sure you will enjoy writing test cases.
    Thanks,
    Viswanathan D
    dviswa@gmail.com

    Reply
  13. Hi Vijay,
    I like the web-site very much. It is very useful.
    What I understand is that different interpretations are given by different professional :
    E.g :
    Test Strategy & Test Plan

    Test Strategy may be a higher level document where in it may contain various Test Plans (Strategy may include plans for integration testing, system testing, user acceptance testing, etc)

    E.g : Static Testing

    When I go through articles under static testing the entire life cycle activities such as various reviews, audits, etc are covered.

    I get confused. Is there any standard where in specific definitions are given so as remove ambiguity.

    Can you please define a role of QA in a Software Testing Service Orgn?

    Thank you for your immence service. Like to interact more.

    Regards
    Nagesh

    Reply
  14. Hi Guys,

    Anyone can help me? i need E Commerce based test plan document. If any one having please send me. this is my email id “ashokkumaramtex@gmail.com”

    Reply
  15. Hi,

    Test Plan : It contains all (like Introduction, scope, s/w req. h/w req, ,…etc…).
    But it is not necessary that all should be followed in TEST STRATEGY for any of the new project, where we can modify according to the Client or Project requirements.

    TESTPLAN: It is the set of rules made for the company
    TEST STRATEGY:By Modifying the testplan according to the Client, TEST STRATEGY comes into picture, here we may not follow all the rules. If you have still any doubts oe related to Manual testing., you can contact me @santoshpalvai@yahoo.com..

    Hope so, it cleared ur doubt..

    Reply
  16. I am not from s/w dev background; i am basically from quality assurance; can i get involved in software testing? what are the pre requisites .

    Reply
  17. Hi friends,
    I am doing manual testing and performing load test by using jmeter test tool. can u tell me how to prepare the performance- load test report..

    with regards
    sundar

    Reply
  18. Hi. anyone can help me? i don’t understand about SIGNIFICANTLY IMPACTED DEPARTMENTS (SIDs). Can anyone explain to me about it?

    Reply
  19. thanks
    i found the test plan which is very easy and understandable…
    can you please provide me bug tracking report format , so that i get how to submit bug to developer

    Reply
  20. hi,
    i am planning to do software testing course from long back.but i am still confusion to see lots of test…what will be the best for me.just i want get a job any how , can i do both manual and automation? what is the difference? or shall i concentrate testing course.plz szst me what will ve to do to find the testing job.
    thanks

    Reply
  21. Anyone can help me out?I had erp project to test.And i am only one tester in the company.Will you plz guide me how can i test the project.How can i maintain the documents.What strategy should i follow.

    Reply
  22. Hi Sujatha,

    Test Plan : It contains all (like Introduction, scope, s/w req. h/w req, ,…etc…).
    But it is not necessary that all should be followed in TEST STRATEGY for any of the new project, where we can modify according to the Client or Project requirements.

    TESTPLAN: It is the set of rules made for the company
    TEST STRATEGY:By Modifying the testplan according to the Client, TEST STRATEGY comes into picture, here we may not follow all the rules. If you have still any doubts oe related to Manual testing., you can contact me @santoshpalvai@yahoo.com..

    Hope so, it cleared ur doubt..

    Reply
  23. Hiii,

    First of all thanks…:), i found this site is very useful… Please send me some real time example of test cases & test data on my email..

    Reply
  24. hi i am sethuraman, presently i am doing a software testing courses in STC. I like to do some projects related in automation tools of Winrunner and QTP. thereby i am in need of some sample SRS. if u have any relevant SRS, send to me, thereby its useful to do some projects.

    Same time, can u give a weblink to take a model online exams in software testing.

    Reply
  25. I don’t know how to write scope for integration testing Besides, I somehow mix the objectives with acceptance criteria. Could anyone clear me about those please?

    Thanks in Advance

    Reply
  26. Can anyone help me regarding switching the software comapny.I want to know if anyone has experince in Junit and manual testing after 2 yrs of experience in software industry,is his knowledge enough to switch or need to gain more and then switch.

    Reply
  27. Test Plan and Test strategy documents are extremely important in any project. Both documents are usually frozen at the beginning of the test engagement, but do under constant changes and revisions. We can call both documents to be live documents.

    The basic difference between the two is as below:

    Test plan is a document that contains list of activities that would be a part of testing the application (AUT). A test plan contains the following details:

    1.Details on the Environment
    2.Details on the application and Scope of Testing
    3.Different phases of testing involved in the test project:
    i. Unit Testing – Responsibility & Exit criteria
    ii. System Testing – Responsibility & Exit criteria
    iii. Integration testing – Responsibility & Exit criteria
    iv. UAT / Business User Testing – Responsibility & Exit criteria
    4. Environment Cycle plan & Batch calendar plan
    5. Resource Requirement across each phases of testing
    6. Test Deliverables
    7. Test team skills, requirements, roles & responsibilities.
    8. Details on resource ramp up and ramp down
    9. Details of the availability of hardware and support software requirement.
    10. Details on training needs
    11. Risks and mitigation
    12. Contingency plan

    Test Strategy – Test Strategy is a document that talks about how the testing is to be carried out across each phase. Take for example, in Unit testing phase test strategy would define entry and exit criteria along with ways and means of how the module would be unit tested. Test Strategy would vary from phases to phase since same strategy cannot be followed for two phases keeping in mind no two phases of testing are similar.

    So, eventually Test Plan is a parent document the contain test strategy as a child document.

    The perception of test plan and test strategy would vary from organization to organization and even project to project.

    Regards,
    Arun
    http://www.focustesting.com

    Reply
  28. hi how to plan write the test cases in iam workig on mannual testing how can i start the test process iam new in testing please

    Reply
  29. Hi,

    I want to know how to get a job in s/w testing. I have 5+ years of s/w deveopment experience and after that I took a 6 year break from IT to handle family responsibilities. Now I want to comeback in IT field but not in the development. I feel testing/quality area would be little less consuming than mainstream development. Correct me if I am wrong.
    Can anybody send me details about testing job, some reading material and courses which can help getting a job in today’s demanding job mkt.
    thanks

    comeback.it.in.test@gmail.com

    Reply
  30. Hi,Can anybody pls let me know “what is the actual need for test strategy when there is test Plan?”Why is test plan needed?

    Reply
  31. Anyone can help me? i need E Commerce based test plan document. If any one having please send me. this is my email id “ashokkumaramtex@gmail.com”

    Reply
  32. Hi,
    Thanks a lot for the detailed test plan template.
    I would like to know the test strategy how to apply.
    And test estimation techniques.
    -Hareesh

    Reply
  33. I have seen test plan sample and test case but never seen regression plan or regression suite. Is it uncommon for tutorials helping us in this matter too.

    Reply
  34. thanks
    I gain idea about the basic test plan requirements. can you please provide me any basic application or system test plan example which is implemented in software companies, so that we get clear idea about the test plan ?

    Reply
  35. any one tell me.

    1) What is diff b/n unit testing and white box testing(WBT) and it have any related link and WB tester can test the unit testing and voice versa?.

    2)how can test acceptance testing without alpha and beta testing(that is end user)

    Reply
  36. Kindly gimme some help documents through whichi start automation testing, as i have good backgroung of programming languages

    Reply
  37. @ Pallavi

    Both severity and priority are related with bug.
    Severity shows “How sever Bug is” (i.e. if there is any bug found in any functionality then how it is impacting on system)
    Priority shows “Urgency of fixing the bug” (i.e. Seeting the priority for solving the bug, if any bug is more sever then it should be fix first.)
    There are levels of severity and Priority.
    Severity: Catastrophic, Sever, Medium, Low
    Priority: Blocker, High, Medium, Low

    Reply
  38. Suppose you have to test the following time coordination web application. The
    application has two pages: (User interface is shown below)
    Page A:
    i. User sets a time zone from the drop down
    ii. User selects a date and then selects a time.
    iii. The app generates a unique link to page B.
    Page B using the unique link from Page A:
    i. User sets a time zone from the drop down
    ii. The app shows the date and time that was selected on page A according to the time zone
    selected on pages B.
    For example:
    Page A: 2/4/213, 10:00am (IDT) (GMT+3)
    Page B: 2/4/2013, 8:00am (BST) (GMT+1)
    Please prepare a Test document with different test conditions/data that verifies the system
    converts the time correctly

    Reply
  39. Hi VIjay,

    i want to know i have 1.6 year experience in testing.But due to some reason i currently i am not working since last.
    6 months .Now i am again searching job in manual and automation testing .Is it possible can i get job again in testing field after 6 to 7 month gap .

    Reply
    • yes definately there are opportunities for you. Do skillset brushing like if you have manual experience then read and make a document that will contain all the end to end process of how manual testing is done. Likewise for Automation too. Just make sure you are thorough with the concepts and if you have sufficient time then at least pass ISQTB foundation level course certification! I have joined with a gap of 4 years due to maternity. and I had 1yr and 10 months of exp. So don’t worry, keep trying

      Reply
  40. Hi
    Still this is more usefull than the other ones but it’s great if you all can provide us template in dco or excel format.

    Thank you

    Reply
  41. @ manjunath – Thanks for making me to write article on Bug life cycle (https://www.softwaretestinghelp.com/bug-life-cycle/) This is actually base for my next article “Writing a good bug report”. I will write it soon.

    @ anjana – If you don’t want to go for Programming language then its useless to think about Automation testing. So you have only one option of Manual testing which may restrict your career.

    @ sricharan – Diff. In short- Test strategy describes the overall testing approach i.e how to test? Test strategy comes under test plan.
    Test plan defines Scope, approach and what to test?

    @ reddy – traceability matrix is used to map the user requirements with the deliverables. We can use traceability matrix for mapping user level requirements to functional requirements and also for verifying system specifications. You can use a simple excel sheet having two columns of requirement and traceability to maintain traceability matrix.

    Reply
  42. Hi

    I am pavani and have recently joined as tester. Presently I am testing a web based application where in I am assigned to do Funcional testing., I have some questions like

    1)is there any format we need to follow to prepare TRM
    2) how do we create Test beds for automating test cases?

    Reply
  43. Hey there! I simply would like to give you a huge thumbs up for your excellent info you’ve got right here on this post. I am coming back to your web site for more soon.

    Reply
  44. ———————–
    3 Principal Test Documents
    ———————–
    1. Test Policy (Organisation Level)

    – Very High Level Document
    – What “Testing” means for organisation
    – How organisation measures test success
    – Relatively static document (Changes when organisation’s focus changes)
    – Developed by IT department

    2. Test Strategy (Programme Level)

    – Applicable for a Programme/System which covers multiple projects
    – Objective/Scope of Testing
    – Inscope/Out of scope Items for testing
    – Test Levels (Unit/Module/System/Integration)
    – Test Types ( Functional/Non-Functional)
    – Entry/Exit/Stop/Resumption Criteria for testing (for different Levels/Phases)
    – Risks to be addressed
    – Test Environment
    – Test case design methodology (Specification driven/BVA/EQ Parttition)
    – Test methodology ( Top-down/bottom-up/risk based)
    – Test Automation Approach
    – Test Tools to be used
    – Defect Management approach
    – Defect classification
    – Retesting & regression approach

    3. Test Plan (Project Level)

    – All above points specific for this project
    – Test Estimation & Test schedule
    – Test Organisation/roles/responsibilities
    – Test deliverables
    – Test reporting

    Reply
  45. Hi Anuradha,

    Wht you see is what the testplan contains. Still if you feel that you are not satisfied with that , then i would def provide you the real time testplan.

    Thanks,
    Santosh Palvai
    anybody can reach me @ santoshpalavi@yahoo.com

    Reply
  46. Hi
    I AM HANSAL. LOOKING FOR A JOB IN TELECOM SOFTWARE TESTING FIELD. SO CAN ANYBODY GIVE ME SOME WEBSITES WHERE I CAN GET SOME GOOD PROJECTS .PLEASE HELP ME . I NEED SOME PROJECT DETAIL OF GSM,UMTS .

    Reply
  47. Sir i am new in this field, so i just want to know from where should i start learning software testing.
    Please help me.

    Best Regards,
    Aman Agrawal

    Reply
  48. Guys,

    Does anybody have a Project Classification documents… i.e. project falls on which category, it’s small or medium project…. etc.

    Please send the documents to – karthik@when.com

    Thanks in advance!
    Karthik

    Reply
  49. Hi Anadhan,

    1. Unit testing is usually done by developers where they will be testing every function point/unit which they are developing before it is being integrated to other application. White box testing can be conducted by a developer or a tester, white box testing is conducted with the motive of identifying/pointing a defect/bug exactly where inside the code.

    2. Alpha testing is usually called first phase of testing, where it will be tested within the project team like unit testing, FVT (functional verification testing), system testing. Beta testing is the one executed along with the end user, usually called User Acceptance Testing or Certification testing. It cannot be executed without the end user.

    Reply
  50. Hi friends,

    I advised to freshers like me… this is pretty site for learning Testing…
    I thank to who establish this site.

    Regards,
    Somanthan R.

    Reply
  51. *If my earlier message was posted please disregards this*
    Above template of the test plan was very useful.
    I am required to create an automation test plan.It would be very helpful if i can get a template of this automated test plan.
    Thanks in advance.
    JAS

    Reply
  52. Hi, My email Id is kalraharpreet@gmail.com

    Please send me different type of template to do TPA if you have different. Or If you can also send me the templates to have the High Level Estimations of Tsting…

    I really Appreciate.

    Thanks,
    Harpreet

    Reply
  53. Suppose you have to test the following time coordination web application. The
    application has two pages: (User interface is shown below)
    Page A:
    i. User sets a time zone from the drop down
    ii. User selects a date and then selects a time.
    iii. The app generates a unique link to page B.
    Page B using the unique link from Page A:
    i. User sets a time zone from the drop down
    ii. The app shows the date and time that was selected on page A according to the time zone
    selected on pages B.
    For example:
    Page A: 2/4/213, 10:00am (IDT) (GMT+3)
    Page B: 2/4/2013, 8:00am (BST) (GMT+1)
    Please prepare a Test document with different test conditions/data that verifies the system
    converts the time correctly

    Reply
  54. hi,
    i am planning to do software testing course from long back.but i am still in confusion which institute will be the best in bangalore. and which institute is giving placement assistance? can i do both manual and automation? what is the difference? pls let me know which will not involve programming. i dont want to get into programming.pls let me know which will suit me. or shall i concentrate only in one course.either manual or automation. thanks.

    Reply
  55. I have done my B.Sc.(Chemistry). & also done my software testing diploma in SQTL. I am fresher & wants jobs in testing.
    But please request to my all friends dont join SQTL.
    Because they dont have any placement. Don’t join SQTL.
    Don’t join SQTL.

    Reply
  56. What do you think are the advantages/disadvantages of having separate unit,
    integration, and system test plans as opposed to an inclusive test plan that contains
    all three in the same document?

    Reply
  57. I don’t know if copying chunks of text out of a well known standard is plaigarism, but at least citing it as a reference may make you look a little more legit.

    Best of luck.

    Reply
  58. Hi I want know what are the possible ways of testing Continuous ambulatory peritoneal dialysis since i am a fresher i dont have any idea regarding this please help me out .

    Reply
  59. Can anyone help me out with the templates for load testing, capacity planning and volume testing…??

    I need to knw the difference between them also..

    Reply
  60. can anyone tell me , which is the best Document Management Software in Tetsing means how we can maintain Release Note ,Testcases,traceability Template in One Software .its an Urgent Need .

    Reply
  61. Hi

    I wish to know about Master Test Plan (Strategic Test Plan) and how is it different from the normal test-plan that is made for each level 1) unit testing 2) Integration Testing 3) System Testing and 4) Acceptance Testing?
    Is Strategic/ Master Test Plan ever made in Practical Testing Environment? Why is Master Test Plan necessary? How is it different from Actual Test Plan? What are the different Criteria that go into the making of Master Test Plan? Who is involved in Making a Master Test Plan? How many Years of work-expereince in required before a Test-Engineer starts designing a Master Test Plan? Kindly email me the reply to

    email id : subu_scorpio@yahoo.com

    Reply
  62. Hi Divya,

    When you come across a defect and if it does not have a test case, then you need to update your test case accordingly through following change test case process. A defect need to have test cases, please tell this answer in your next interview.

    Thanks,
    Viswanathan D
    dviswa@gmail.com

    Reply
  63. im completed my mca in 2010 after that i have join teaching field due to some family problem ,but now days im interested in software testing what will be i do?

    Reply
    • Learn the some basic programming coding . like as the php,python and many more.after that apply the QA fresher requirements for the particular company and gotte the job and also make the experience the change the jobs.

      Reply
  64. Hi,
    Please can any one of u tel how to apply for ISTQB certification? Is there any course given for that?Where is it?
    Please give me details about ISTQB because i dont ve any idea. Please.

    Regards,
    Priya

    Reply
  65. preethi just put 6 month live project Experience in Testing recognized Training center or take One year fake Experience
    No problem ……….

    Reply
  66. @ Rupali,

    There is no difference between Functional and functionality testing. They are having same meaning To Test the functionality of the system.

    Reply
  67. Hi Kavitha,

    Static Testing: Testing the application without running the application. Nothing but testing the Documents like Business Requirement Specification, Functional Specifications and other testing documents whether the mentioned requirements and functionalities are complete or not. Ex: Testing the documents Test Case document for checking whether it covers the full functional flow of the applications or not.

    Dynamic Testing: Testing the application by running it currently. Ex: Testing the applications whether it meets all the functionalities mentioned in the Functional Specifications by running the Test Cases which are generated against the Requirements of the client.

    Reply
  68. Hi…. I am looking for a FVT Test plan template for a POS project. Can you please email me the template.
    Thanks a lot in advance.

    Reply
  69. Hi Rachna

    Beginner certificate in Testing would be ISTQB. Once you finish this, you can try for CSTE or CSQA

    Thanks
    Siva

    Reply
  70. Guys

    Can you please send me the template to do estimation using Test Point ANalysis. Harpeet or George, I see you both discussing on this as well.

    Thanks
    Selvan

    Reply
  71. Hey guys, anyone can help me? i’m struggling with my system documentation 🙁 please send me an realtime testing documentation of a sales and inventory system 🙁
    i will look after to that please help me 🙁

    Reply
  72. Hi,anyone can help me? I need core banking based functional test case plan document.
    What is the format of writting the test plan for UAT test cycle 1?
    If any one having please send me, this is my email id
    “myathephyu@fpb.com.mm”

    Reply
  73. Hi Venky,
    thank you for your reply. . .
    may i know the differnce between test strategy and test plan. . does test strategy comes within test plan?

    Reply

Leave a Comment