Test Double

Test Double Coffee Time AI Harnesses

Test Double

Get in the Box Joé Dupuis demos Claude Code sandbox set up

Test Double

Test failures as a scientific experiment

Test Double

Software testing strategies How to decide on test coverage options

Test Double

Tests as Living Documentation

Test Double

Using tests in legacy app migrations

Test Double

The time is money rule of test coverage

Test Double

Software testing strategies From the outer edges in

Test Double

Considerations for end to end vs unit tests in software development

Test Double

Code you don't touch doesn't really break—what happens when you touch it

Test Double

What the heck is test concrete

Test Double

When software test coverage goes wrong

Test Double

Why AI is not good at testing

Test Double

The 8020 rule for software test coverage

Test Double

Tests as Onboarding Tools

Test Double

The context of why a software test failed can help you learn how the code works

Test Double

The misconception that software tests slow you down

Test Double

Testing is about confidence (especially automated tests)

Test Double

Failing tests are a success story (no seriously)

Test Double

Why automated tests are non negotiable for legacy systems

Test Double

Don't shy away from ambiguity of legacy software

Test Double

Legacy rewrite or refactor Cutting the scope of the system

Test Double

When a legacy software rewrite makes sense

Test Double

Legacy modernization What happens when seams are at cross purposes

Test Double

Legacy modernization seams path or value path

Test Double

Why developers should detach from their code

Test Double

Cutting features reveals cascading failures in legacy software apps

Test Double

The old, legacy system probably works fine

Test Double

Technical fixes are not magic cures if your org is failing

Test Double

3 Stages to evaluate code

Test Double