🪲 [Fix]: Improve test results failure handling and reporting

[Marius Storhaug (MariusStorhaug)]

The action now provides more detailed and actionable error messages when test results fail. When tests don't execute properly or result files are missing, you'll receive specific information about what went wrong, making it easier to diagnose and fix issues with your test suites.

• Fixes [Fix]: Improve test results failure handling and reporting Process-PSModule#223

Improved Error Reporting

The action now generates specific error messages for each type of test failure, including:

• Missing result files
• Tests that weren't executed
• Failed test results
• No tests reported
• No tests passed
• Inconclusive tests
• Tests that weren't run

Each error message clearly identifies which test suite and result file is affected, helping you quickly locate and resolve issues.

Safer Property Access

The action now checks for null values before accessing test result properties (Tests, Passed, Failed, Inconclusive, NotRun). This prevents errors when processing incomplete or malformed test result files.

Better Categorization

Missing result files are now tracked separately from unexecuted tests, providing clearer insight into whether a test file wasn't found in the artifacts or if it was present but marked as not executed.

[Copilot]

Pull Request Overview

Enhances test result failure handling by adding granular error categorization and safer null checks, aiming to provide clearer diagnostics in CI runs.

• Adds per-condition failure reason collection and reporting (missing files, not executed, failed, inconclusive, etc.).
• Introduces null-guard variables before numeric property access.
• Changes behavior of exit code to increment per failure reason instead of per failing test file.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}