stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

wip(tools): xunit runner helper + QA guidance iteration

Browse Source 
Follow-up to SPRINT_20260419_028 TEST-RUNNER-001.

- scripts/test-targeted-xunit.ps1: refinements to the helper.
- docs/code-of-conduct/TESTING_PRACTICES.md: default targeted xUnit v3
  verification to the new helper.
- docs/qa/feature-checks/FLOW.md: call out Microsoft Testing Platform
  filter-ignore behaviour and point to the helper.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
master
2026-04-19 14:48:48 +03:00
parent 333d894690
commit 3d14332609
3 changed files with 22 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/code-of-conduct/TESTING_PRACTICES.md
View File

@@ -28,6 +28,14 @@
- Avoid live network calls; rely on fixtures and local emulators only.
- Inject time and ID providers (TimeProvider, IGuidGenerator) for testability.
## Targeted xUnit v3 execution
- Some Stella Ops test projects expose the xUnit v3 in-process runner through Microsoft Testing Platform.
- On those projects, `dotnet test --filter ...` may be ignored even when the caller expects a narrow subset.
- For targeted verification on those projects, use `pwsh ./scripts/test-targeted-xunit.ps1 -Project <test-project>.csproj ...` or execute the produced test DLL directly with `dotnet exec`.
- Capture the exact targeted method/class/trait arguments in sprint evidence so reviewers can confirm the run was actually scoped.
- If the test assembly is stale, rebuild the specific `.csproj` first; prefer a scoped build over a solution-wide rebuild.
---
## Intent tagging (Turn #6)