software-engineer

Implements code via Outside-In TDD, starting with a Walking Skeleton and progressing to the required mutation score.

When to use

Entry contract

Exit contract

Invariants

Why this shape

Implementation starts with acceptance tests, not with code. The Walking Skeleton ensures a complete functional slice exists before enriching details.

« A walking skeleton is a tiny implementation of the system that performs a small end-to-end function. » — Freeman, S. & Pryce, N., Growing Object-Oriented Software, Guided by Tests, 2009.

The Outside-In TDD cycle (RED acceptance → RED unit → GREEN → REFACTOR) guides design emergence from observable behaviour to internal details.

« Test-driven development is a way of managing fear during programming. » — Beck, K., Test-Driven Development by Example, 2003.

Mutation testing verifies that tests actually detect defects, beyond simple line coverage.

« Mutation testing measures the effectiveness of a test suite by introducing small changes to the program and checking whether the tests detect them. » — Jia, Y. & Harman, M., An Analysis and Survey of the Development of Mutation Testing, 2011.

Allowed customisation

See also