Test Result Analyzer fails if no stack trace is available

[FreundDK]

❔What, Why & How

Fixes #2256

TestResultAnalyzer uses "#Text", which might be null instead of InnerText
This code shows what is wrong with that:

# Demonstrates the bug fixed by this PR:
# ."#text" returns $null on empty XML elements, causing .Trim() to throw.
# .InnerText returns "" instead, handling empty nodes safely.

[xml]$xml = @"
<nodes>
  <node message="1">Content</node>
  <node message="2"></node>
</nodes>
"@

Write-Host -ForegroundColor Yellow "FAILING:"
try {
    foreach ($node in $xml.nodes.node) {
        Write-Host "$($node.message)"
        Write-Host "Content: '$($node."#text".Trim())'"
    }
}
catch {
    Write-Host -ForegroundColor Red "ERROR"
}
Write-Host
Write-Host -ForegroundColor Yellow "WORKING:"
foreach ($node in $xml.nodes.node) {
    Write-Host "$($node.message)"
    Write-Host "Content: '$($node.InnerText.Trim())'"
}

[Copilot]

Pull request overview

Fixes a crash in the AnalyzeTests action when a <failure> XML element has no stack trace content by switching from the XML "#text" accessor (which can be $null) to InnerText (empty string for empty nodes).

Changes:

• Replace $failure."#text" with $failure.InnerText when rendering and storing stack traces in GetTestResultSummaryMD.

[aholstrup1]

LGTM. Missing a releasenote though

[freddydk]

@aholstrup1 - any chance we can get this small bugfix in?

[aholstrup1]

Of course @freddydk - Sorry about the wait :)

We just shipped v9.1. Can I get you to update the release note in this PR? Once it's updated we'll get it merged

[FreundDK]

Of course @freddydk - Sorry about the wait :)

We just shipped v9.1. Can I get you to update the release note in this PR? Once it's updated we'll get it merged

Done

[aholstrup1]

@FreundDK Looks like there is a merge conflict somewhere (I'm guessing in the releasenotes) 🙃

[FreundDK]

@FreundDK Looks like there is a merge conflict somewhere (I'm guessing in the releasenotes) 🙃

Resolved, please approve and merge

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

Actions/AnalyzeTests/TestResultAnalyzer.ps1:195

• Please add a Pester regression test that passes a failing test case with an empty <failure> element to GetTestResultSummaryMD and verifies that analysis completes with an empty stack trace. The current suite tests other analyzer functions but never exercises this function, so this exact bug could regress unnoticed.

                                        Write-Host "        $($failure.InnerText.Trim().Replace("`n","`n        "))"