Summary
The bundled mcp__drm-copilot__run_poshqc_test coverage capture writes artifacts/pester/powershell-coverage.xml with zero covered lines for every file in the repository, making the canonical repo-wide PowerShell coverage artifact unusable as a gate input.
Environment
- OS/version: Windows 11 Pro 10.0.26200
- Python version: n/a (PowerShell / Pester 5)
- Command/flags used:
mcp__drm-copilot__run_poshqc_test with scan_folders = ["scripts/vscode", "tests/scripts/vscode"]
- Data source or fixture:
artifacts/pester/powershell-coverage.xml, written 2026-08-10 22:58
Steps to Reproduce
- Run
mcp__drm-copilot__run_poshqc_test against a workspace whose Pester suite passes and demonstrably exercises production code.
- Read the generated
artifacts/pester/powershell-coverage.xml.
- Aggregate its JaCoCo
<counter> elements by type.
Expected Behavior
The emitted JaCoCo counters should reflect the lines actually executed by the passing suite. For the run in question, scripts/vscode/Invoke-MSTestWithCoverage.Helpers.ps1 was exercised by 19 passing tests and independently measured at 183/202 = 90.59% LINE coverage by a direct Invoke-Pester capture at the same head.
Actual Behavior
Every counter records zero covered. Aggregated over all 1227 <counter> elements in the file:
CLASS covered 0 / missed 168
INSTRUCTION covered 0 / missed 21800
LINE covered 0 / missed 16075
METHOD covered 0 / missed 1445
A reading of literal zero repo-wide, for a run whose suite passed and whose direct-Pester capture at the same head reports 90.59% on the primary file, is a measurement defect in the capture rather than a property of the code.
Logs / Screenshots
Impact / Severity
The canonical repo-wide PowerShell coverage artifact reads 0.00% against an >= 85% floor. Any gate that consumes it fails unconditionally, and any agent that trusts it will either report a false blocker or route around the canonical artifact. Discovered during feature review of #441 (recorded there as finding NF-2 and dispositioned non-blocking for that bugfix, because the defect is pre-existing and #441 changes no coverage-capture tooling, hook, or configuration).
Source
From: docs/features/potential/2026-08-10-poshqc-test-coverage-capture-records-zero.md
Summary
The bundled
mcp__drm-copilot__run_poshqc_testcoverage capture writesartifacts/pester/powershell-coverage.xmlwith zero covered lines for every file in the repository, making the canonical repo-wide PowerShell coverage artifact unusable as a gate input.Environment
mcp__drm-copilot__run_poshqc_testwithscan_folders = ["scripts/vscode", "tests/scripts/vscode"]artifacts/pester/powershell-coverage.xml, written 2026-08-10 22:58Steps to Reproduce
mcp__drm-copilot__run_poshqc_testagainst a workspace whose Pester suite passes and demonstrably exercises production code.artifacts/pester/powershell-coverage.xml.<counter>elements by type.Expected Behavior
The emitted JaCoCo counters should reflect the lines actually executed by the passing suite. For the run in question,
scripts/vscode/Invoke-MSTestWithCoverage.Helpers.ps1was exercised by 19 passing tests and independently measured at 183/202 = 90.59% LINE coverage by a directInvoke-Pestercapture at the same head.Actual Behavior
Every counter records zero covered. Aggregated over all 1227
<counter>elements in the file:A reading of literal zero repo-wide, for a run whose suite passed and whose direct-Pester capture at the same head reports 90.59% on the primary file, is a measurement defect in the capture rather than a property of the code.
Logs / Screenshots
artifacts/pester/powershell-coverage.xml(gitignored producer output via.gitignore:57, so it is not committed).Impact / Severity
The canonical repo-wide PowerShell coverage artifact reads 0.00% against an
>= 85%floor. Any gate that consumes it fails unconditionally, and any agent that trusts it will either report a false blocker or route around the canonical artifact. Discovered during feature review of #441 (recorded there as finding NF-2 and dispositioned non-blocking for that bugfix, because the defect is pre-existing and #441 changes no coverage-capture tooling, hook, or configuration).Source
From: docs/features/potential/2026-08-10-poshqc-test-coverage-capture-records-zero.md