Skip to content

Enhance coverage guidelines in copilot instructions #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nanonyme merged 1 commit into from
Feb 19, 2026
Merged

Enhance coverage guidelines in copilot instructions #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ Follow the development, linting, and testing process described in
the 79‑character limit.
- **Testing**: Run tests with
`pytest -v --cov=simplecpreprocessor --cov-config .coveragerc --cov-report=term-missing`
- **Coverage**: Maintain or improve test coverage; never decrease it.
- **Coverage**: Maintain or improve test coverage; never decrease it. This includew branch coverage.
- Failure handling in branches is expected to be handled by creating invalid C code. If it's not possible to cover branch with streaming input and hitting it requires direct manipulation, the branch needs to be marked as no cover.
- Evaluate earlier no cover cases as to whether they should be covered by tests when implementing new functionality.

When generating code, apply these rules before returning the final output.