test: steel-man test suites to prevent Goodharting #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes by Priority
P0 - Critical (tests were testing mocks, not code)
export-import.test.ts: Replaced mocked import test with true integration testexport-import.test.ts: Added full-field assertions for diffResults round-trip (all fields including hashes, markers, timestamps)P1 - High (incomplete coverage)
export-import.test.ts: Converted diffResults/amendmentLogs export tests to real integration testsregistry.test.ts: Added HTTP error response tests (404, 500), timeout test, malformed JSON testP2 - Medium (edge cases)
registry.test.ts: Added incomplete data handling tests (missing fields, null values, empty URLs)comparisonService.test.ts: Added malformed response tests (empty choices, null content, truncated JSON)comparisonService.test.ts: Improved provider config verification (full client config instead of just URL)Test Metrics
Test plan
Why this matters
These tests were "Goodharting" - optimizing for passing tests rather than validating actual behavior:
ImportOps.importFullSessionDatathen checking the mock was called proves nothing about import logic🤖 Generated with Claude Code