Software Testing in the Real World: Practical Strategies for Software Testing

Guided by the ISTQB's seven key principles of software testing, this one day course explores software testing in the real world.

Course Features

  • Based on widely accepted software testing best practice
  • Best practice interpreted against a background of practical experience gained during the testing of large, complex software applications
  • Learning reinforced by quizzes, exercises and group activities

Participant Benefits

  • Understanding of software testing best practice
  • Ability to apply best practice to real world projects
  • Develop an awareness of some of the major potential testing pitfalls

Who Should Attend

  • Test Managers, Test Engineers, Testers, Quality Assurance Staff
  • Business Analysts, Business Systems Analysts, Systems Analysts, Functional Analysts
  • User Representatives, Subject Matter Experts, Project managers, Program Managers
  • Software Engineers, Developers, Requirements Engineers, Requirements Analysts, Human Factors Specialists
  • Process Engineers, Software Engineering Process Group (SEPG) Staff, Methodologists, Process Improvement Staff

Course Duration

  • 1 day

Course Agenda

What is Poor Quality Software?

What Causes Software Failures?

  • People
  • Environment

What is Software Testing?

  • Different Views of Quality
  • Gaps Between the Views of Quality
  • The Reason For Gaps
  • Closing the Gaps
  • Software Testing Objectives: Why Perform a Test?

What Software Testing is Not!

The Principles of Software Testing

Principle 1: Testing Shows Presence of Defects

  • Test to Pass vs. Test to Fail
  • Lessons Learnt in the Real World

Principle 2: Exhaustive Testing is Impossible

  • Risk Based Testing
  • Lessons Learnt in the Real World

Principle 3: Early Testing is Desirable

  • Efficency of Removing Defects
  • Preventing "Escaping" Defects
  • The Importance of "Testing" Requirements
  • Lessons Learnt in the Real World

Principle 4: Defects Tend to Cluster

  • Defects Cluster on Boundaries
  • Defects Cluster in Components
  • The Risk Paradox
  • Lessons Learnt in the Real World

Principle 5: Pesticide Paradox - Bugs Become Immune

  • Exploratory Testing
  • Automated Testing
  • Comparing Scripted, Automated and Exploratory Testing
  • Lessons Learnt in the Real World

Principle 6: Testing is Context Dependent

  • Test Items: What to Test?
    • The Problem With Traditional Test Levels
    • Component Integration
    • Feature Integration
  • Test Basis: How to Design Test Cases?
    • Skills and Experience
    • Testsing is Not Black and White!
    • Requirements Specification
    • Program Code
    • Other Test Bases
  • Test Method: How to Execute a Test?
    • Stand Alone Testing vs. End to End Testing
    • Running the Tests
      • Program Code
      • System Interface (API)
      • User Interface (UI)
  • Test Agent: Who (or What) Will Perform the Test?
    • Test Analyst
    • Technical Specialist
    • Developer
    • Business Analyst
    • Subject Matter Expert
  • Defining a Test Strategy
  • Lessons Learnt in the Real World

Principle 7: Absence of Errors Falacy

  • Revisiting the Software Testing Objectives
  • Lessons Learnt in the Real World