Monday, May 09, 2005

Test Driven Development Articles and Tutorials

I expect that we could invest what is in effect a week of training in just teaching unit testing techniques and tools. At the end of the week some coverage of TDD, the benefits, approaches, and how the unit testing fits in could be delivered. I skimmed through a Unit Testing Patterns description that someone sent a link to recently. If their were 12 patterns, and an hour was spent discussing the unit testing pattern and another was spent performing a lab to apply the pattern then 24 out of the 40 hours would be consumed. Here is a list of the patterns described in that one article:

Pass/Fail Patterns
  • The Simple-Test Pattern

  • The Code-Path Pattern

  • The Parameter-Range Pattern

  • Data Driven Test Patterns
  • The Simple-Test-Data Pattern

  • The Data-Transformation-Test Pattern

  • Data Transaction Patterns
  • The Simple-Data-I/O Pattern

  • The Constraint-Data Pattern

  • The Rollback Pattern

  • Collection Management Patterns
  • The Collection-Order Pattern

  • The Enumeration Pattern

  • The Collection-Constraint Pattern

  • The Collection-Indexing Pattern

  • Performance Patterns
  • The Performance-Test Pattern

  • Process Patterns
  • The Process-Sequence Pattern

  • The Process-State Pattern

  • The Process-Rule Pattern

  • Simulation Patterns
  • Mock-Object Pattern

  • The Service-Simulation Pattern

  • The Bit-Error-Simulation Pattern

  • The Component-Simulation Pattern

  • Multithreading Patterns
  • The Signalled Pattern

  • The Deadlock-Resolution Pattern

  • Stress-Test Patterns
  • The Bulk-Data-Stress-Test Pattern

  • The Resource-Stress-Test Pattern

  • The Loading-Test Pattern

  • Presentation Layer Patterns
  • The View-State Test Pattern

  • The Model-State Test Pattern
  • 0 Comments:

    Post a Comment

    << Home