📖 [Docs]: Module test layouts aligned with Process-PSModule#88
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Marius Storhaug (MariusStorhaug)
marked this pull request as ready for review
July 26, 2026 00:22
This was referenced Jul 26, 2026
Marius Storhaug (MariusStorhaug)
added a commit
to MSXOrg/docs
that referenced
this pull request
Jul 26, 2026
Module authors can now distinguish the two root-only workflow phase scripts from recursively discovered module-local test entries. ## Fixed: Setup and teardown discovery is unambiguous `tests/BeforeAll.ps1` and `tests/AfterAll.ps1` are documented as exact, non-recursive paths that run once around the module-local test matrix. Ordinary Advanced test entries remain separately eligible for recursive discovery under `tests/`. --- <details> <summary>Technical details</summary> - Corrects `src/docs/Frameworks/Process-PSModule/pipeline-stages.md` to match the exact `Test-Path` checks in Process-PSModule main. - Separates workflow phase detection from recursive configuration, container, and test-file discovery. - Implementation plan progress: all tasks in #99 are complete. - Validation passed: documentation indexes, links, Zensical build, Super-Linter, and diff checks. - Copilot review converged after the clarity feedback was addressed; the final round added no comments. </details> <details> <summary>Relevant issues (or links)</summary> - Fixes #99 - PSModule/docs#88 </details> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Module authors can now choose a test layout that matches their module's size while preserving behavior coverage for every public command.
Changed: Test suites can follow Simple, Standard, or Advanced layouts
Simple modules use one root suite, Standard modules group root suites by public function domain, and Advanced modules use recursive directories with Process-PSModule's configuration, container, and test-file precedence. Grouped suites are explicitly supported without weakening the requirement to test every public command's behavior.
Technical details
TestNamederivation.BeforeAll.ps1andAfterAll.ps1workflow phases.Relevant issues (or links)