docs: state test counts as floors, not snapshots - #59
Merged
Conversation
Every exact count in the README and SUBMISSION.md was stale. A day of work took unit 156 to 173, integration 100 to 142, the backend total 315 to 374, and the frontend 282 across 39 files to 340 across 43. None of the documents moved with them. That is the fourth time in one day the numbers drifted, so the fix is not to correct them again. Floors stay true as long as tests are only added, and the exact figures live in the linked CI run where they cannot go stale. The same reasoning was applied to the Devpost description earlier, where the one number that survived the whole day was the one written as "300+".
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.
Every exact test count in
README.mdanddemo/SUBMISSION.mdwas stale, because today's work added tests and no document moved with them.Why floors instead of corrected numbers
This is the fourth drift in a single day. Correcting them again just resets the clock on the same failure.
A floor stays true as long as tests are only added, and the exact figures already live in the linked CI run, where they cannot go stale by construction. The evidence for this is on the Devpost page: the one number that survived the entire day untouched was the one written as
300+.The same change was made to the live ClaimScene Devpost description earlier, where
289 backend tests plus 126 frontend testswas understating the real 569 and 375 by more than half, in a criterion that is scored.Docs only.