#2257 Test Result Analyzer fails if no stack trace is available
Fixed Test Result Analyzer to handle XML elements without stack traces by using InnerText instead of the potentially null text property.
- 2files
- 1AL files
- 0objects
Pull request · merged into main on 2026-07-29 by FreundDK · 2 files (+3 -2), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Switched from #Text to InnerText for XML element content retrieval
- Prevents null reference errors when analyzing test results with empty stack traces
- Ensures the analyzer handles edge cases in test failure reporting
- Uses safer XML property access pattern
- Behaviour changes for users or extensions.
AL objects touched
Actions/AnalyzeTests/TestResultAnalyzer.ps1: modified, not in the BC? snapshot
Context
- Fixes: #2256 [Bug]: Test Result Analyzer fails if no stack trace is available (closed)
- Systems: development, platform
- From the description: “TestResultAnalyzer uses “#Text”, which might be null instead of InnerText”
Source: metadata of a merged pull request in microsoft/AL-Go (al-go): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).