DEV Community

Cover image for Overview of the test plan in manual testing

Posted on

Overview of the test plan in manual testing

What is Test Plan?
A project's test plan is a document that is created at the project level. It dictates which work items will be tested, how they will be tested, and how test types will be distributed among testers.

A test plan is a document that describes a software testing effort's scope, approach, objectives, resources, and schedule.
It's the document that defines out a testing project's what, when, how, and who.

Activities for Test Planning:

  1. To define the scope and dangers that must be examined, as well as those that must not be examined.
  2. Creating a Test Strategy Document
  3. Taking a look at the test estimate.
  4. Planning when and how to test, selecting how to evaluate test results, and setting a test exit criterion.

Test Plan components:

  1. Test plan identifier: Unique identifying reference.
  2. Introduction: A brief overview of the project as well as the document.
  3. Test items: A test item is a software program that represents the application being tested.
  4. Features to be tested: A feature that needs to be tested on the software.
  5. Features not to be tested: Identify the features and the reasons why they were not included in the testing.
  6. Approach: Details on the overall testing strategy.
  7. Item pass/fail criteria: Everything was documented whether a software program passed or failed its test.
  8. Test deliverables: Test plans, test specifications, and test summary reports are examples of deliverables that are delivered as part of the testing process.
  9. Test Environment: Defining the environment's requirements, including hardware, software, operating systems, network setups, and tools.
  10. Responsibilities: Lists the team members' duties and responsibilities.
  11. Staffing and training needs: The actual workforce requirements, as well as any specialized skills and training requirements, are captured.
  12. Schedule: Indicates major project deadlines and critical milestones.
  13. Risks and Mitigation: High-level project risks and assumptions, as well as a plan to reduce each risk.
  14. Approvals: All document evaluated and the results, their titles, and the sign-off date are recorded.

Top comments (0)