docs(testing): extraction verification strategy paper#210
Merged
Conversation
How to verify Clio's batch extraction: test against real DOM, diff every conversation against the site's data-API export as an independent oracle (how the '10 vs 18' turn-drop was caught), five verification layers, each of the six anomalies (#204-#209) mapped to a regression assertion, a proposed reusable tools/verify_export harness, and a concrete definition of 'verified' vs 'it ran'. No-Issue: operator-requested testing-strategy paper Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
![cerberus-az[bot]](https://avatars.githubusercontent.com/u/1158095?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
How I would test Clio's batch extraction: real-DOM fixtures, an oracle diff against the site's data-API export (the method that caught the 10-vs-18 turn drop), five verification layers, each of the six anomalies (#204-#209) mapped to a regression assertion, a proposed reusable verify harness, and a concrete definition of verified.
No-Issue: operator-requested testing-strategy paper