The Kluever Maneuver
Web page · https://jordi.inversethought.com/blog/the-kluever-maneuver
First seen by Oriel on .
AI summary
The article advocates the “Kluever Maneuver,” a two-commit bugfix workflow that first records buggy behavior, then fixes both code and test.
- Commit 1 adds a passing test that explicitly captures the defect, such as asserting that buggy addition returns 5.
- Commit 2 corrects the implementation and changes the test to assert the intended result, preserving CI success at every commit.
- An age-validation example shows how a test can pass before and after an ineffective fix when it tests the wrong boundary case.
- The article recommends referencing a bug tracker issue in the first commit and marking it fixed in the second.
- Kurt Kluever taught the technique and calls the initial assertions “terrible tests.”
#testing #bug fixing #continuous integration #bug tracking
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Lobsters: 55, latest observation ; +54 over observed period since
Comments
Comment count reported by the source.
- Lobsters: 34, latest observation ; +34 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Lobsters | rpiu3w | https://jordi.inversethought.com/blog/the-kluever-maneuver/ Read discussion |