This tutorial covers area 1 of the Test Management Body of Knowledge (TMBOK) required for the Certified Test Manager (CTM) certification. This tutorial also counts as an elective towards the requirements of the Certified Software Test Professional certification.

For cost and cities where this course might be offered, check our Public Training Schedule.To bring this course to your test team at your location, contact our Education and Professionals Services Group.

Your testing process is the way testing is done in your organization and involves much more than merely procedures and paperwork, such as the people and organizational issues essential for support and success.  This interactive course describes key elements a testing process needs in order to be effective and efficient and explains how Proactive Testing™ can go well beyond traditional reactive testing to deliver higher quality systems quicker and cheaper.  Managing the testing process involves defining, monitoring, and actively guiding/adjusting how individual testing projects plan, design, organize, direct, and control testing of specific systems under test (SUT).  Techniques are shown to identify testing and necessary supportive tasks; estimate required time, effort, and resources; keep testing on track; and monitor and evaluate the testing process itself.  Exercises enhance learning by allowing participants to practice techniques.

WHO SHOULD ATTEND:  This course has been designed for test, system, and project managers, as well as testers, analysts, and others who plan, oversee, and/or carry out testing of systems and software.

• REAL vs. Presumed Process identification and elements a testing process should include
• Managing the testing process vs. managing individual testing projects
• A structured Proactive TestingÔ process that yields better software and also cuts development time
• Effective and efficient no-busywork methods for planning, designing, and organizing tests
• Cross-project components, roles, and tasks to provide adequate testing infrastructure environment
• Issues and techniques to gain support within the organization for suitable testing
• Measures to monitor both testing of particular software and overall test process effectiveness

• I DEFINING THE TESTING PROCESS
  • Defining and evaluating your current process
  • Relation of testing projects to testing process
  • Commonly-recognized test process issues
  • REAL vs. Presumed Processes
  • “How much process?” is mistaken question
  • Reactive testing—out of time, but not tests
  • Current status of defect injection, detection
  • Quality goals and the testing process
  • Models of test process maturity
  • Documentation of and from the process
  • Managing testing Key Process Areas
  • “Good practices” limitations on using alone
  • Life cycle involvement, iterative approaches
  • Static and dynamic testing, issues
  • CAT-Scan ApproachÔ to find more errors
  • Independent test group issues and strengths
  • Planning and designing tests
  • Test execution and status reporting
  • Defect categorization and analysis
  • Customs, beliefs, management practices
  • Measuring and managing the testing process
  • Secrets for overcoming resistance to testing
  • Proactive Testing better, quicker, cheaper
  • How testing can save the developer’s time
  • Caution:  “Emperor’s New Clothes” risk
  • Recognizing your REAL hidden issues
• II MANAGING THE TEST ENVIRONMENT
  • Establishing the testing infrastructure
  • Maintaining test beds, databases, labs
  • Automated tools for testing
  • Configuration management, defect tracking
  • Standards, policies, and procedures
  • Roles, staffing, training, and career paths
• III PLANNING AND DESIGNING TESTING
  • Risk elements, relation to testing
  • Proactive vs. reactive risk analysis
  • IEEE Standard for Test Documentation
  • Master Test Plan counterpart to project plan
  • Risk-based way to define test units
  • Letting testing drive development
  • Preventing major cause of overruns
  • ue agility, value vs. busywork
  • Regression tests, avoiding minefield effect
  • IEEE Standard on Unit Testing
  • Graphical technique to simplify integrations
  • Integration test plans prevent schedule slips
  • Avoiding the major cause of estimate errors
  • Top-down vs. bottom-up sizing techniques
  • Providing for ancillary and support tasks
  • Critical Path dependencies, concurrencies
  • Controlling test execution relative to plan
  • Earned value
  • Measuring and improving test effectiveness