📖 [Docs]: Module test layouts aligned with Process-PSModule

[Marius Storhaug (MariusStorhaug)]

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

• Documents live Process-PSModule directory discovery and first-dot TestName derivation.
• Aligns Pester 6 requirements, locally runnable tests, and module-owned mocking boundaries with MSX guidance.
• Clarifies root-only BeforeAll.ps1 and AfterAll.ps1 workflow phases.
• Validation passed: Zensical build, Super-Linter, CodeQL, and diff checks.

Relevant issues (or links)

• Fixes Align test-layout guidance with grouped public command tests #87

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITHUB_ACTIONS_ZIZMOR	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
HTML	Pass ✅
JAVASCRIPT_ES	Pass ✅
JAVASCRIPT_PRETTIER	Pass ✅
MARKDOWN	Pass ✅
NATURAL_LANGUAGE	Pass ✅
POWERSHELL	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter