Repository navigation
Drift detector rewards string-matching over meaningful tests #40
Description
Activity
🔗 Related PRs
#2 - Add drift detector command and close out cycle 0005 [merged]
#21 - Align test taxonomy fixtures with live legends [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Migrated from Method backlog
This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.
Source backlog:
docs/method/backlog/cool-ideas/PROCESS_drift-detector-rewards-string-matching-over-meaningful-tests.mdOriginal lane:
cool-ideasOriginal legend:
PROCESSOriginal backlog card
Drift detector rewards string-matching over meaningful tests
Tests were written this session whose only purpose was to string-match a playback question — adding zero value beyond satisfying the drift detector. The drift detector should evaluate whether behavior is tested, not whether a test description matches a question string. Consider: if the playback question is 'Does the build clean dist?' and a test named 'build hygiene' asserts rm -rf dist in the script, that should count.