Lecture Notes for Extreme Programming

31 May 2001 - Acceptance Testing


  1. why test

    1. customer assurance

    2. developer's feedback

    3. establish baselines for further development and maintenance - regression

  2. motivations

    1. programming is hard, programmers are dumb

    2. earliest detection is cheapest

    3. clarify specifications - dangerous

  3. method

    1. customer specifies tests

    2. programmer designs, implements, executes and archives tests

    3. automation - no guru checks output

      1. testing is a non-human activity

      2. good testing is hard

      3. testing must be repeatable

      4. automated testing development - deja gnus, xUnit

    4. what kind of testing

      1. unit testing

      2. acceptance testing


This page last modified on 3 July 2001.