You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- coverage-report: `dotnet tool run reportgenerator -reports:"artifacts/coverage/coverage.cobertura.xml" -targetdir:"artifacts/coverage-report" -reporttypes:"HtmlSummary;MarkdownSummaryGithub"`
93
96
94
97
### Rule Precedence
95
98
@@ -109,7 +112,7 @@ If no new rule is detected -> do not update the file.
109
112
110
113
- Keep the standardized workflow skills first; use the extra installed inventory only when the repository actually wires that tool into commands, CI, docs, or an explicit user request.
- Quality and maintainability: `mcaf-dotnet-quality-ci`, `mcaf-dotnet-complexity`, `mcaf-solid-maintainability`
115
118
- Governance and docs: `mcaf-solution-governance`, `mcaf-architecture-overview`, `mcaf-adr-writing`, `mcaf-feature-spec`, `mcaf-ci-cd`
@@ -199,6 +202,7 @@ If no new rule is detected -> do not update the file.
199
202
- Test framework in this repository is TUnit. Never add or keep xUnit here.
200
203
- This repository uses `TUnit` on `Microsoft.Testing.Platform`; never use VSTest-only flags such as `--filter` or `--logger`, because they are not supported here.
201
204
- For TUnit solution runs, always invoke `dotnet test --solution ...`; do not pass the solution path positionally.
205
+
- Coverage in this repository uses the local `coverlet.console` tool against the built test assembly, then renders human-readable output with the local `reportgenerator` tool.
202
206
- Every behavior change must include or update tests in `tests/ManagedCode.MCPGateway.Tests/`.
203
207
- Add tests only when they close a meaningful behavior or regression gap; avoid low-signal tests that only increase count without improving confidence.
204
208
- Keep tests focused on real gateway behavior:
@@ -211,7 +215,9 @@ If no new rule is detected -> do not update the file.
211
215
- Do not remove tests to get green builds.
212
216
- Keep `global.json` configured for `Microsoft.Testing.Platform` when TUnit is used.
213
217
- At the end of implementation work, run code-size and quality verification with `cloc`, `roslynator`, and the repository's strict .NET build/test checks, then fix actionable findings so oversized files and quality drift do not accumulate.
218
+
-`CSharpier` and `Stryker.NET` are installed as opt-in local tools for focused checks; they are not default formatter or default fast-path CI gates in this repository.
0 commit comments