Skip to content

docs(release-readiness): resolve 05 Pester tests vs artifact layout - #13

Open
jakehildreth wants to merge 1 commit into
mainfrom
docs/release-readiness-05
Open

docs(release-readiness): resolve 05 Pester tests vs artifact layout#13
jakehildreth wants to merge 1 commit into
mainfrom
docs/release-readiness-05

Conversation

@jakehildreth

@jakehildreth jakehildreth commented Aug 17, 2026

Copy link
Copy Markdown
Owner

Decision

Update the tests to the real artifact layout. The Output/<Module>/<version>/ contract died with the PSStucco/BuildHelpers build system in 7b8c203 and is not restorable.

The rewrite (when executed)

  1. Manifest.tests.ps1 + Help.tests.ps1 derive paths from $PSScriptRootArtefacts/Unpacked/ADCSGoat/ADCSGoat.psd1 (canonical layout per ticket 03). BuildHelpers BH* env vars deleted — nothing has set them since the PSPublishModule migration; both files currently fail before their first assertion.
  2. The changelog-version-match assertion is deleted from the always-on suite: under ticket 01 the changelog regenerates at release time, and version consistency is already enforced by 04's post-build assertion and 11's publish gate. The already-skipped Git tagging block stays skipped.
  3. Build-required guard: artifact tests skip with a clear reason ("run Build/Build-Module.ps1 first") when no artifact exists, instead of failing. A fresh-clone Invoke-Pester runs green; Meta.tests.ps1 is unaffected (it lints source, runs standalone).

- Rewrite tests to PSScriptRoot-relative path: Artefacts/Unpacked/ADCSGoat/ADCSGoat.psd1
- Drop dead BuildHelpers BH* env vars (PSStucco scaffolding fossils, unset since 7b8c203)
- Delete changelog-version-match assertion: release-time concern, enforced by 04's post-build assertion and 11's publish gate
- Artifact tests skip with a clear reason when no build exists, keeping fresh-clone Invoke-Pester green
@jakehildreth
jakehildreth force-pushed the docs/release-readiness-05 branch from f3a9381 to f42251a Compare August 17, 2026 15:37
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