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

wip(tools): targeted xunit runner helper

Browse Source 
Sprint SPRINT_20260419_028_Tools_targeted_xunit_runner_workflow
(TEST-RUNNER-001 DOING — sprint remains active).

- scripts/test-targeted-xunit.ps1: rebuild-and-invoke xUnit v3 in-process
  runner directly so targeted filters work under Microsoft Testing Platform
  (dotnet test --filter is ignored there).
- Register sprint file in implplan.

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

50
docs/implplan/SPRINT_20260419_028_Tools_targeted_xunit_runner_workflow.md Normal file
View File

@@ -0,0 +1,50 @@
# Sprint 20260419-028 - Tools Targeted xUnit Runner Workflow
## Topic & Scope
- Harden the repo-side targeted test workflow for xUnit v3 projects that run under Microsoft Testing Platform.
- Add a small helper so targeted verification uses one deterministic command instead of ad hoc build plus `dotnet exec` steps.
- Update QA and testing guidance so maintainers stop relying on `dotnet test --filter` where it is ignored.
- Working directory: `scripts/`.
- Cross-module touchpoints explicitly allowed for this sprint: `docs/qa/feature-checks/`, `docs/code-of-conduct/`, `docs/implplan/`.
- Expected evidence: runnable helper script, synced QA/testing docs, and a focused verification run against real Platform and Concelier test assemblies.
## Dependencies & Concurrency
- Follows `docs/implplan/SPRINT_20260418_001_Platform_advisory_setup_truthfulness_hardening.md`, which exposed the current xUnit v3 targeted-test mismatch while closing backend setup verification.
- Safe to execute in parallel with unrelated module work because the write scope is limited to repo-level scripts plus shared QA/testing docs.
## Documentation Prerequisites
- `docs/qa/feature-checks/FLOW.md`
- `docs/code-of-conduct/TESTING_PRACTICES.md`
- `scripts/test-stabilization/run-tests-batch.ps1`
- `docs/implplan/SPRINT_20260418_001_Platform_advisory_setup_truthfulness_hardening.md`
## Delivery Tracker
### TEST-RUNNER-001 - Add deterministic targeted xUnit helper and guidance
Status: DOING
Dependency: none
Owners: Developer, Test Automation, Documentation author
Task description:
- Some repo test projects expose the xUnit v3 in-process runner through Microsoft Testing Platform. In that configuration, `dotnet test --filter` can be ignored even when the caller expects a narrow subset, which makes targeted QA evidence misleading and wastes shell/process budget during investigation.
- Add a repo-level helper that rebuilds a specific test project when needed, resolves the produced DLL, and executes the xUnit runner directly with method/class/namespace/trait filters. Update shared QA/testing docs to make that workflow the default for xUnit v3 targeted verification and explicitly call out that unified exec saturation is an external agent-host concern, not a Stella Ops runtime defect.
Completion criteria:
- [ ] A repo-level PowerShell helper runs targeted xUnit v3 tests from a `.csproj` using direct DLL execution.
- [ ] QA flow guidance documents when `dotnet test --filter` is valid and when direct xUnit DLL execution is required.
- [ ] Testing practices document the targeted xUnit v3 workflow and expected evidence capture.
- [ ] Focused verification proves the helper works against the Platform and Concelier setup/advisory test projects.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-04-19 | Sprint created after the setup/advisory hardening verification exposed that several repo test projects use xUnit v3 under Microsoft Testing Platform, where `dotnet test --filter` does not provide trustworthy targeted execution. | Codex |
## Decisions & Risks
- Decision: fix the repo-side verification workflow with a helper script plus shared QA/testing guidance rather than per-module notes, because the runner behavior is infrastructure-wide and not specific to Platform or Concelier.
- Risk: a helper that assumes a single target framework may mis-handle multi-target test projects. The first version must either support explicit framework selection or fail clearly when the `.csproj` declares multiple target frameworks.
- External-note boundary: the repeated unified-exec session warnings come from the agent host process budget, not from Stella Ops application code. This sprint can reduce command churn by consolidating targeted test execution into one helper, but it cannot change the external host limit itself.
## Next Checkpoints
- Add the helper under `scripts/`.
- Update shared QA/testing docs with the exact invocation pattern.
- Verify the helper against the targeted Platform and Concelier setup/advisory methods.