docs: add contributor note on where tests live#25
Merged
Conversation
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
2 participants
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
Adds a short contributor-facing note to the Checks section of CONTRIBUTING.md,
pointing to where the harness tests live (
harness/tests/, including theHypothesis property tests) and how to run just that suite while iterating.
Why
The Checks section documents
harness preflightandharness gate, but nothingtells a new contributor where the tests actually are or how to run only them.
Checks run
uv run pytest harness/tests— 196 passeduv run harness gate— lint, pylint, complexipy, security and pytest all passed(the pyright phase failed locally only, due to a missing
libatomic1in my WSL2 environment)Notes
Docs-only, no test implementation, per the acceptance criteria.
Closes #20