Emily is the author of “Technical Agile Coaching with the Samman method”.
Emily is an independent Technical Coach and the chair of the executive board of the Samman Technical Coaching Society. You can find out more on her website.
Learning Hours:
- Approval Testing Intro
- Approval Testing with Combinations
- Architecture Decision Records
- Arrange - Act - Assert
- Asserting on Collections of Objects
- Beck's 4 rules of simple design
- Benefits of Arrange - Act - Assert
- Change Signature
- Characteristics of Unit tests
- Code Reading - Common Code Smells
- Code Reading - Scanning
- Code Smells - Introduction
- Code Smells - Summaries
- Combination Approvals needs a Pure Function
- Complexity / Collaborator quadrant analysis
- Cover the patient with tests
- Custom Assertions
- Data-Driven Testing with Approvals
- Decompose Conditional
- Design for Approval Testing
- Design in the Red step
- Discover and Formulate Scenarios for the Lift Kata
- Double-Loop TDD
- Example Mapping
- Example-guided design
- Extract and Override
- Faking Dependencies
- Filtering output that varies
- Fluency with TDD
- Four Pillars of a Good Test (Khorikov)
- Gherkin intro
- Gilded Rose Demo - Approvals with Coverage and Mutation testing
- Golden Rule of TDD
- Idiomatic Code
- Iterative or Incremental
- Keyboarding skills
- Leap Years with Approvals
- Lift Kata with Approvals
- Make a test list
- Misconceptions about Refactoring
- Mocking Dependencies
- Modelling vs Diagramming
- Move the patient into the surgery
- Narrow Integration Tests for Outbound Ports
- One function at a time, bottom up
- Outside-in TDD
- Overdesign
- Parameterized Tests
- Parameterized Tests in Doctest
- Peel - a strategy for difficult to test code
- Printer Design
- Refactor the Patient for Testability
- Refactoring Golf
- Refactoring Without Tools
- Replace Conditional With Polymorphism
- Return the patient
- Roll Up Loop
- Sandboxing Introduction
- Selecting and ordering test cases
- Simon Brown's C4 model - Container diagrams
- Simon Brown's C4 model - Intro
- Simplify Conditional
- Slicing a task using ZOMBIES
- Split Loop
- Split Phase
- Split Variable
- Start with the Assertion
- Strangler Fig Pattern
- Strategy - Slice
- Stubbing Dependencies
- Supplying User Input via stdin
- TDD cycles
- TDD with TextTest
- TDD with a list
- Take Smaller Steps
- Talking with Intent, Typing Syntax
- Test Doubles Intro
- Test Fixture design
- Test Fixtures - Readability vs Duplication
- Test Names - the Osherove pattern
- Test Order
- Test maintenance
- Testing Private Methods
- Text-Based Testing
- Text-based Approval Tests for Yatzy
- The Dependency Inversion Principle
- The Divio Documentation System
- Three parts of a test
- Unit Test FIRST properties
- Unit Tests Should Find Bugs
- User Documentation and code snippets
- Using TDD to write a Leap Years function
- Using coverage when adding tests to existing code
- Vocabulary for Refactoring
- When to use a Test Double
- When you need a mock
- Writing tests for pure functions
Co-authored Learning Hours:
- Designing a Harness for Agentic Autonomy (Part 1)
- Designing a Harness for Agentic Autonomy (Part 2)
- Fixture Object Pattern
- From Ask Mode to Agent Mode
- Identify Paragraphs in Long Methods
- Invasive Critical Aggregator
- Mending Law of Demeter Issues with Refactoring Tools
- Parallel Change
- Primitive Obsession
- Test Fixture Introduction
- When you need a fake
- When you need a spy
- When you need a stub