Test-First OSS Patches: Write the Failing Fixture Before You Touch the Code

Description and use

Writing a failing test fixture before touching code turns vague bug reports into reproducible, minimal tests, enabling quick, small patches and faster reviews in open‑source projects.

Problem

Bug reports are often non-reproducible until a failing test is written, leaving maintainers unable to verify and fix issues efficiently.

Outcome

The workflow reduces maintainer effort by converting a bug report into a reproducible test fixture and a minimal patch, speeding review and ensuring the fix is guarded by code.

Workflow

• Create a branch and fixture directory, copy minimal input and expected output
• Write a single‑assertion test that reproduces the failure
• Run the test to confirm failure
• Extract failure signature from test output
• Patch the smallest code change to make the test pass
• Run the test again and the full suite to confirm success
• Commit the test and the fix in separate commits

Evidence

A bug report is not reproducible until a test fails on your machine. Before that moment it is just a story.

Source

The loop takes about twenty minutes on a small parser bug. It saves maintainer attention, which is the scarcest resource in open source.

Source

Two commits let a reviewer verify the test fails before the fix and passes after it. That is the whole argument, expressed as git history.

Source