BiteSizedChunks.comLearn one small thing at a time.

Course contentsShow

Software Engineering

488The Red-Green-Refactor Loop
489Red: Writing the Failing Test First
490Seeing the Test Fail for the Right Reason
491Green: Making the Test Pass Quickly
492Refactor: Improving Without Breaking Tests
493Taking Small Steps in TDD
494Triangulation: Adding Tests to Drive Generalization
495The TDD Rhythm and Flow
496Common TDD Cycle Mistakes
497Starting with the Simplest Test
498The Fake It Pattern
499Triangulation: Adding Test Cases
500The Transformation Priority Premise
501Handling Edge Cases Incrementally
502Refactoring Test Code
503When to Delete or Merge Tests
504TDD Rhythm and Discipline
505Dealing with Uncertainty in TDD
506TDD and Performance Optimization
507TDD as a Design Tool
508Designing Testable Interfaces
509Discovering Abstractions Through Tests
510TDD and Dependency Injection
511Listening to Test Pain
512Emergent Design vs. Upfront Design
513TDD and Single Responsibility
514Growing Object-Oriented Software Guided by Tests
515Legacy Code Without Tests
516External Dependencies and Infrastructure
517UI and Presentation Layer Testing
518Exploratory and Spike Solutions
519Performance-Critical Code
520Uncertain Requirements and Prototypes
521Team Adoption and Learning Curve

Software Engineering

488The Red-Green-Refactor Loop
489Red: Writing the Failing Test First
490Seeing the Test Fail for the Right Reason
491Green: Making the Test Pass Quickly
492Refactor: Improving Without Breaking Tests
493Taking Small Steps in TDD
494Triangulation: Adding Tests to Drive Generalization
495The TDD Rhythm and Flow
496Common TDD Cycle Mistakes
497Starting with the Simplest Test
498The Fake It Pattern
499Triangulation: Adding Test Cases
500The Transformation Priority Premise
501Handling Edge Cases Incrementally
502Refactoring Test Code
503When to Delete or Merge Tests
504TDD Rhythm and Discipline
505Dealing with Uncertainty in TDD
506TDD and Performance Optimization
507TDD as a Design Tool
508Designing Testable Interfaces
509Discovering Abstractions Through Tests
510TDD and Dependency Injection
511Listening to Test Pain
512Emergent Design vs. Upfront Design
513TDD and Single Responsibility
514Growing Object-Oriented Software Guided by Tests
515Legacy Code Without Tests
516External Dependencies and Infrastructure
517UI and Presentation Layer Testing
518Exploratory and Spike Solutions
519Performance-Critical Code
520Uncertain Requirements and Prototypes
521Team Adoption and Learning Curve

← Software Engineering

Lesson 513 of 1,933·15. Test-Driven DevelopmentPro lesson

TDD and Single Responsibility

Using test setup complexity as a signal that a class or function has too many responsibilities.

This lesson is for subscribers

You've completed the free preview. Subscribe to unlock every lesson in every course.

See pricing Back to course