Last updated: Jan 30, 25 16:02 UTC | Permalink

3 - Test Adequacy

Learning Objectives:

By the end of this lesson, you should be able to:

• Explain different reasons why you might want to test
• Design a TDD test suite by identifying equivalence classes of inputs
• Explain the following measures of code coverage, and how they differ:
  • Statement or line coverage
  • Branch coverage
  • Path coverage
• Use mutation testing to judge the completeness of a test suite

Important Dates:

• Individual Project 1 Due Wednesday, January 22 by 12pm (Noon)

  Lecture Slides:

• When have I written enough tests? Slides PDF, PPT

Activity

• Activity: Transcript Server Test Adequacy

Resources

• Software Engineering at Google: “Testing”
• ComAir crew scheduling example
• A Decade of Software Model Checking with SLAM
• CrowdStrike Chaos Explained
• StrykerJS - Mutation Testing Tool
• Are mutants a valid substitute for real faults in software testing?