Post test result summary as PR comment

[MariusStorhaug]

Context

When tests run in the CI pipeline, the results are available in the workflow logs but are not surfaced directly on the pull request. Posting a test summary as a PR comment gives reviewers immediate visibility into test outcomes.

Request

The test step should post a summary comment on the PR with key test results:

• Operating systems tested
• PowerShell edition(s)
• Code coverage percentage
• Errors (if any)
• Number of tests succeeded, failed, and skipped

Acceptance criteria

• A summary comment is posted on the PR after tests complete
• The comment includes OS, PS edition, coverage, and pass/fail counts
• The comment is updated (not duplicated) on subsequent runs
• Failed tests include relevant error details

---

Technical decisions

To be determined during implementation planning.

See inspiration: Pester Tests Report GitHub Action

---

Implementation plan

• Design the PR comment template with test result summary
• Extract test results from Pester output (XML or console)
• Post or update the PR comment via the GitHub API
• Include code coverage data if available
• Test with passing, failing, and mixed test results

[MariusStorhaug]

Restructured issue description into the standard three-section format.

• Rewrote from brief notes into a proper context/request structure
• Updated title to imperative mood (removed emoji prefix)
• Added link to Pester Tests Report action for inspiration
• Created implementation plan with 5 tasks
• Applied Minor label (new feature)