Planning Effective Software Testing

Live Classroom
Duration: 3 days
Live Virtual Classroom
Duration: 3 days
Pattern figure


This course familiarizes participants the test planning process, identifying the inputs required, and what needs to be produced. The course guides the participants how to plan or test case creation, defect tracking, status monitoring and progress reporting. The course equips participants with the skills and knowledge required to create a test plan that will serve all needs.

What You'll Learn

  • Objectively identify when testing is complete so you can eliminate ambiguity and disagreements
  • Clearly describe the importance and role of the Test Plan so other stakeholders embrace it as important
  • Understand how to list the content of a complete Test Plan so you never miss any important components
  • Obtain key facts & data you need for accurate Test Planning
  • Identify necessary testing-related activities so everyone understands exactly what needs to be done
  • Use a requirements-to-test traceability matrix to assure nothing has been overlooked
  • Prioritize testing-related activities so tradeoffs can be done with confidence
  • Estimate resources required for testing—be assured that you have what you need, when you need it
  • Define a comprehensive testing calendar

Assure the completeness of your tests and eliminate surprises for your customers


  • Understand how testing fits within the software development lifecycle
  • Understand the role and use of a test plan
  • See how the test plan relates to other plans
  • List the inputs to test planning
  • List the outputs from test planning
  • Perform peer reviews of the test plan
  • Obtain organizational commitment to the test plan
  • Track progress against the test plan, report status and re-plan

  • Identify the requirements against which the testing will be done
  • Define the goals and objectives for testing
  • Identify boundaries – what will and will not be tested
  • Enumerate the phases and steps in the testing lifecycle
  • Define specific entry criteria – how you know when testing can begin
  • Define specific exit criteria – how you know when testing is complete
  • Identify testing services that will be purchased rather than done in-house

  • List every requirement and goal or objective in one place
  • List every test and test case in one place
  • Map requirements to test cases
  • Assure that every requirement has at least one test case
  • Assure that every test case responds to at least one requirement
  • Avoid overkill or under emphasis in testing
  • Determine the impact of skipping test cases

  • Identify tests for functional requirements
  • Identify tests for performance requirements
  • Identify tests for security and safety requirements
  • Identify tests for usability, maintainability and other requirements
  • Define objectives and success criteria for each test
  • Document each test in the traceability matrix
  • Use the traceability matrix to assure complete coverage

  • Enumerate the test cases required to satisfy the objectives for each test
  • Identify positive, negative, boundary and special test cases
  • Define objectives and success criteria for each test case
  • Document each test case in the traceability matrix
  • Use the traceability matrix to assure complete coverage

  • Test case description and instructions
  • Input data and/or database records required by the test case
  • Output data and/or database records the test case will produce
  • Special resources required by the test case
  • Execution time for the test case

  • Identify the testing and test case development environment (e.g. Hardware, Operating Systems, Networks, Software, Databases)
  • Specify any special systems (e.g. Test Automation, Defect Tracking)
  • Enumerate knowledge and skills needed
  • Plan for hiring, contracting and training

  • Identify the activities required to produce and execute all of the test cases, track defects, retest and do all of the other tasks associated with the testing lifecycle
  • Estimate the effort required based on the size estimates and identified activities
  • Identify all costs (e.g. Labor, Equipment, Software Contracted Work)
  • Establish a schedule for all testing-related activities
  • Spread the costs across the schedule to produce a budget
  • Validate budget and schedule against project constraints
  • Resolve budget or schedule issues

  • Brainstorm a testing-related risk list
  • Group and consolidate risks
  • Quantify risk probability and impact
  • Make risk tracking plans
  • Make risk mitigation plans
  • Make risk contingency plans

  • Identify measurements that will be used in tracking and managing the testing activities
  • Determine how the data and reports that are generated by the testing process will be stored, managed and made available
  • Determine how often testing status will be checked and who will participate in status checking activities
  • Identify triggers for corrective actions when the testing activities deviate from the plan Determine what must happen when the test plan must be updated
  • Identify all individuals and groups that have a stake in the testing activities
  • Determine how the stakeholders will be involved and kept informed about testing-related activities
Ripple wave

Who should attend

The course is highly recommended for –

  • Quality analysts
  • Quality engineers
  • Testers
  • Quality managers
  • Project managers
  • Software engineers
  • Testing leads


There are no prerequisites for this course.

Interested in this Course?

    Ready to recode your DNA for GenAI?
    Discover how Cognixia can help.

    Get in Touch
    Pattern figure
    Ripple wave