Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

What is Test Plan? Edureka

47 views

Published on

YouTube Link: https://youtu.be/S2_AJP9Oeg0
**Test Automation Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training **
This Edureka PPT on "Test Plan in Software Testing" will give you in-depth knowledge on how to create a Test Plan in Software Testing and why it is important. The following are the topics covered in the session:
Software Testing Documentation
What is Test Plan?
Benefits of Using Test Plan
Types of Test Plan
How to Write a Test Plan?
Test Plan Template / Test Plan Document

Software Testing Blog playlist: http://bit.ly/2UXwdJm
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR

Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in

Published in: Technology
  • Be the first to comment

What is Test Plan? Edureka

  1. 1. SOFTWARE TESTING DOCUMENTATION WHAT IS TEST PLAN? BENEFITS OF USING TEST PLAN TYPES OF TEST PLAN TEST PLAN TEMPLATE HOW TO WRITE A TEST PLAN? www.edureka.co
  2. 2. www.edureka.co
  3. 3. YES! Documentation plays a critical role in Software Testing. Let me share my experience… www.edureka.co Documentation in Software Testing A Project….unknown technical issue…angry client.... requirement not documented.. Is documentation necessary in Software Testing?
  4. 4. Test Case TestScenario Traceability Matrix Types of Documented Artifacts in Software Testing Test Plan Test plan is a document prepared at the project level. In general it defines work products to be tested, how they will be tested and test type distribution among testers www.edureka.co
  5. 5. Test Scenario Traceability Matrix Types of Documented Artifacts in Software Testing Test case is a complexity of inputs, serious of steps, and conditions that can be used during the process of testing. Test Plan www.edureka.co Test Case
  6. 6. Test Case Traceability Matrix Types of Documented Artifacts in Software Testing Test scenario can be considered as a single line statement which notifies the area in which your application will experiment. This artifact is needed for ensuring the overall procedure tested from start to finish. Test Plan Test Scenario www.edureka.co
  7. 7. Test Case Test Scenario Types of Documented Artefacts in Software Testing Traceability Matrix (also referred to as Requirement Traceability Matrix - RTM) is a table that is used to trace the requirements during the Software Development Life Cycle Test Plan Traceability Matrix Traceability Matrix www.edureka.co
  8. 8. www.edureka.co
  9. 9. A test plan is a document describing the scope, approach, objectives, resources, and schedule of a software testing effort. It is the document that outlines the what, when, how, who, and more of a testing project. Why Where When HowWho What www.edureka.co
  10. 10. www.edureka.co Acts as a quick guide for testing process Helps avoid effort in ‘Out of Scope’ functionalities Determines time, cost & efforts needed Defines roles & responsibilities for tester Provides schedule for testing activities Outlines resource requirements & equipment Acts as source of proof if need in future
  11. 11. www.edureka.co 01 Misunderstandings about roles & responsibilities 02 Test team will have not so clear test objectives 03 No surety about when the test process ends 04 Undefined test scope misleads testers & users
  12. 12. www.edureka.co
  13. 13. www.edureka.co A single high-level test plan for a project/product that unifies all other test plans Intermediate plans specifically related to a level of software testing Plans for major types of testing like Performance Test Plan and Security Test Plan Master Test Plan Level Specific Test Plan Type Specific Test Plan Test Plan Types
  14. 14. www.edureka.co
  15. 15. www.edureka.co Q. Can you test a product without any information about it? As first step tester must learn about the product thoroughly before testing it. ➢ Who will use the software ➢ What is it for? ➢ How will it work? Interview client, designer & developer Review product & project Perform product walkthrough Analyse the product Develop Test Strategy Define Test Objectives Resource Planning Schedule & Estimation Determine Test Deliverables www.edureka.co
  16. 16. www.edureka.co The tester should design a strategy which can assist him/her in defining the scope of testing Test Strategy defines ➢ The project’s testing objectives and the means to achieve them ➢ Determines testing effort and costs Define the scope of testing2.1 Step 2 2.2 2.3 2.4 Identify the testing type Document risks & issues Create the test logistics Analyse the product Develop Test Strategy Define Test Objectives Resource Planning Schedule & Estimation Determine Test Deliverables www.edureka.co
  17. 17. www.edureka.co A good test plan clearly defines the testing scope and its boundaries. The basic goal of any software project is to ensure that software is bug free. Tester can do the following to define scope: ➢ List features to be tested ➢ List features not to be tested ➢ Define the goal based on above features Analyse the product Develop Test Strategy Define Test Objectives Resource Planning Schedule & Estimation Determine Test Deliverables www.edureka.co
  18. 18. www.edureka.co Analyse the product Develop Test Strategy Define Test Objectives Resource Planning Schedule & Estimation Determine Test Deliverables Resource plan is a detailed summary of all types of resources required to complete project task. It includes: ➢ Different software & hardware requirements (sever, computers, network, test tools etc) ➢ Employees requirement (test manager, testers, developers, test admin etc) www.edureka.co
  19. 19. www.edureka.co Analyse the product Develop Test Strategy Define Test Objectives Resource Planning Schedule & Estimation Determine Test Deliverables A good test plan clearly lists down the ‘roles and responsibilities’ of testing team along with ‘schedule’ and tells everyone what to do and when to do. A schedule usually has multiple components like: ➢ Tasks ➢ Members responsible for tasks ➢ Estimated effort ➢ Employee & project deadline’ ➢ Project estimation ➢ Possible project risks www.edureka.co
  20. 20. www.edureka.co Analyse the product Develop Test Strategy Define Test Objectives Resource Planning Schedule & Estimation Determine Test Deliverables Test Deliverables is a list of all the documents, tools and other components that has to be developed and maintained in support of the testing effort. ➢ Test plan documents ➢ Test cases documents ➢ Test design specifications ➢ Test scripts ➢ Simulators ➢ Test data ➢ Test matrix ➢ Error Logs ➢ Execution Logs ➢ Test Results ➢ Defects report ➢ Release notes Before Testing During Testing After Testing www.edureka.co
  21. 21. www.edureka.co
  22. 22. www.edureka.co Uniquely identifies the test plan & may include version number Parameter Description Test Plan Identifier Standard for Test Plan Documentation Introduction Sets objectives, scope, goals, resource & budget constraints Lists the systems and subsystems which be tested All the features & functionalities to be tested are listed here Lists the characteristics of products that need not be tested Has sources of test data, inputs and outputs, testing priorities Describes a success criteria for evaluating the test results Has criteria that may result in suspending testing activities Test Items Features to be tested Features not to be tested Approach Item pass/fail Suspension Criteria www.edureka.co
  23. 23. www.edureka.co Includes test cases, sample data, test report, issue log Parameter Description Test Deliverables Standard for Test Plan Documentation Testing Tasks Describes dependencies between tasks & resources needed Lists software, hardware or other testing requirements Lists roles and responsibilities assigned to the testing team Describes the additional training needs for the staff Details on when the testing activities will take place are listed Lists overall risk of the project as it pertains to testing Contains signature of approval from stakeholders Environmental Needs Responsibilities Staffing Needs Schedule Risks Approvals www.edureka.co
  24. 24. Copyright © 2017, edureka and/or its affiliates. All rights reserved. www.edureka.co
  25. 25. www.edureka.co

×