Skip to content

Seed coverage+link gates, ADR/RTM seeds, and CI artifacts for rc0.1.0#15

Draft
svelderrainruiz wants to merge 6 commits into
LabVIEW-Community-CI-CD:developfrom
svelderrainruiz:feat/release-rc-gates-and-trace
Draft

Seed coverage+link gates, ADR/RTM seeds, and CI artifacts for rc0.1.0#15
svelderrainruiz wants to merge 6 commits into
LabVIEW-Community-CI-CD:developfrom
svelderrainruiz:feat/release-rc-gates-and-trace

Conversation

@svelderrainruiz
Copy link
Copy Markdown

@svelderrainruiz svelderrainruiz commented Nov 14, 2025

Default branch: develop
Test framework: Pester (PowerShell 7) with workflows installing ≥6.0.0
Workflows touching tests/docs: coverage.yml, docs-link-check.yml, ci-ubuntu-minimal.yml, psscriptanalyzer.yml
ADR paths: adr/ADR-0001.md, architecture/adr/**
docs/RTM.md present with seed table
CI gate expectations:

Coverage job uploads artifacts/coverage/coverage.xml and artifacts/test-results/results.xml, failing <75% total or <75% per-file for src/Core.psm1/tools/Build.ps1 (skipped if missing).
Docs link-check uploads .lychee/** artifacts even on failure.

## Summary
- Enforce the RC coverage gate on Windows by running Pester ≥6, producing Cobertura + JUnit artifacts, and failing fast below 75% total or per-file coverage.
- Add a lychee-based docs link check that retries/time-limits scans and preserves its `.lychee` report.
- Seed root-level ADR/RTM files for traceability and document how to run the full PowerShell test suite locally.

## Diagnostics
- Default branch: `develop`
- Test framework: Pester (PowerShell 7, workflows install Pester ≥6)
- Existing workflows touching tests/docs: coverage.yml, docs-link-check.yml, ci-ubuntu-minimal.yml, psscriptanalyzer.yml
- ADR paths: `architecture/adr/` (existing) plus new `adr/ADR-0001.md`

## What's in this PR
- Windows coverage workflow emitting `artifacts/coverage/coverage.xml` and `artifacts/test-results/results.xml`, enforcing ≥75% total coverage and 75% per-file floors for `src/Core.psm1`/`tools/Build.ps1` when present, and uploading artifacts via `junit-results` / `coverage-xml` on every run.
- Ubuntu docs link-check workflow using `lycheeverse/lychee-action@v1` with `--no-progress --retry 2 --timeout 20s`, persisting `.lychee/report.md`, and always uploading `lychee-report`.
- Root ADR seed (`adr/ADR-0001.md`) plus `docs/RTM.md` in the requested seed layout.
- README instructions for running `pwsh -NoLogo -Command "Invoke-Pester -Path tests -CI"` locally, mentioning the coverage + link-check gates.

## Gates
- Coverage ≥75% (global) with per-file floors for `src/Core.psm1` and `tools/Build.ps1` if they exist.
- Link-check job uploads `.lychee/**` artifacts each run.

## Artifacts
- `coverage-xml` → `artifacts/coverage/coverage.xml`
- `junit-results` → `artifacts/test-results/results.xml`
- `lychee-report` → `.lychee/**`

## Acceptance Checklist
- [x] Coverage job ran and uploaded artifacts
- [x] Coverage ≥ 75% line total (enforced in workflow)
- [x] Critical file floors ≥ 75% when the files exist
- [x] Docs link-check job ran and uploaded `.lychee` report
- [x] `adr/ADR-0001.md` present with the required header
- [x] `docs/RTM.md` present with the seeded table
- [x] README documents local test instructions
@svelderrainruiz
Copy link
Copy Markdown
Author

trigger: v4.9
rc_tag: rc0.1.0
right_source: RIGHT_REF
right_ref: refs/tags/v15
allow_right_ref: on
toggles:
runner: local
mode: orchestrate
depth: deep
merge_baseline: on
link_mode: paths
evidence_source: runbook-only
timestamp_mode: at-run
runbook_ready: true
return_payload_schema: ready

@svelderrainruiz svelderrainruiz changed the title Feat/release rc gates and trace Seed coverage+link gates, ADR/RTM seeds, and CI artifacts for rc0.1.0 Nov 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant