Uncle Bob's Advanced TDD

Topics covered at TDD-ADVANCED-02-02
View Schedule & Book More dates available

Next up:

This two-day, hands-on Advanced Test Driven Development will explain the principles and practices of Test Driven Development as described in Agile Software Development, Principles, Patterns, and Practices, by Uncle Bob. You will also receive this book as part of the course materials.

This is an intense, hands-on and exercise driven Advanced TDD course that is written and delivered by Uncle Bob Martin, and which focuses on the design of clean, robust, and maintainable unit and acceptance tests. You will learn the principles of test design, and the practices of keeping tests clean. More importantly, you will learn the principles of designing applications for testability. Exercises include the refactoring of bad tests, the writing of clean tests, and the design and refactoring of applications to make them testable.

Exercises are in Java, but are applicable to C#, C++, and other object oriented languages.

Learn how to:

  • The professional’s attitude towards TDD
  • Coping with a non-TDD organization
  • The Principles of Clean Tests
  • Conventions for well written tests
  • Avoiding and repairing fragile tests
  • Testing with GUIs, Databases, Web Containers, and external resources
  • Stubbing, Mocking, and Test Doubles
  • Metrics and Tools
  • BDD
  • Acceptance Testing

About the Author

Uncle Bob (Robert C. Martin)

Robert Martin (@unclebobmartin) has been a programmer since 1970. He is the Master Craftsman at 8th Light inc, an acclaimed speaker at conferences worldwide, and the author of many books including: The Clean Coder, Clean Code, Agile Software Development: Principles, Patterns, and Practices, and UML for Java Programmers.

Thanks to our partners

Moderated Discussion of:

  • Fears, concerns, confounds & blockages
  • Professionalism, Clean Code, and TDD
  • Push-back: What Managers really want
  • Why TDD?
    • The Three Laws of TDD.
    • Understanding the Costs and Benefits.
  • Clean Tests

    • Test Smells
    • Multiple Logical Asserts
    • Accidental Complexity
    • Too Slow
    • Scope Too Wide
    • Slang
    • Cleaning Tests
    • Composed Asserts
    • Composed Results
  • Testing Behaviour vs. State

    • Mocking and Stubbing
    • Ontology of Test Doubles
  • Exercises

    • Initial Setup
    • Coverage
    • Critiquing some good and bad tests
    • Cleaning Tests
    • Review The Presenter Model for UI testability
  • Coding Dojo

    • Group Exercise
    • TDD under the microscope

F.I.R.S.T Principles

  • Making Tests Fast
  • Database Isolation
  • Web Container Isolation
  • Impact Analysis
  • Isolating Tests
  • Repeatable Tests
  • Hosting, Mocking
  • Test Hierarchies
  • Self Validating Tests
  • Testing Tools, the good and the bad
  • Timely Tests

  • Test Conventions and Heuristics

    • Naming Conventions
    • Statistical Testing
    • Principles of Test Encapsulation: Testing Private Methods
    • Testing Inheritance Hierarchies
    • Test Per Class
    • Splitting Test Files
  • Writing Maintainable Tests

    • The Fragile Test ''Problem''
    • Interface Sensitivity
    • Abstract API's
    • Behaviour Sensitivity
    • Data Sensitivity
    • Context Sensitivity
    • Sensitive Comparison and Equality
    • Test Sensitivity
  • Preserving Tests

    • When are Tests Discarded
    • Solutions
  • Exercises

    • Fitnesse
    • Wiki
    • Tests
    • Fixtures
    • Setup
    • Acceptance Tests Smells
    • Critiquing Acceptance Tests
  • Metrics

    • Coverage
    • Combining Cyclomatic Complexity and Coverage
    • Braithwaite's Correlation
    • Wall Metrics
  • S.O.L.I.D The Principles of TEST design

    • How the principles of OO are used to design good tests
  • Static Analysis Tools

  • Behaviour Driven Development (BDD)

  • GUI Testing

  • Testing Through the GUI

  • Testing Around the GUI

  • Stubbing the GUI

    • Stubbing the applications
  • The Levels of Testing

  • The Dilemma of Manual Testing

  • Unit Tests

  • Component Tests

  • Integration Tests

  • System Tests

    • Exploratory Tests
  • Functional and Performance Testing

  • Legacy Code

  • Convincing Others

  • Exercises

  • Refactoring applications to Seperate GUI

  • Testing the GUI seperately

  • Applying the Principles

    • Applying the Levels



For this Advanced Test Driven Development course, you need to be a developer with one or more years experience with TDD.

Bring your own hardware

For this Clean Code workshop, you are required to have your own laptop with the following:

  • Preferred IDE
    • 2GB ram
    • Your preferred Browser

Please contact our team at any time if you need any assistance!