No separate stack trace in Azure Pipelines results

When using xUnit, my failing tests show a dedicated stack trace below the error message in Azure Pipelines, allowing me to click it to go straight to the relevant line in the repo:

However, when using Expecto, the stack trace is printed in the output message, but not available in the UI:

I am using Unquote for assertion, but the same happens with Expecto’s own failtestf.

I am using YoloDev.Expecto.TestSdk 0.8.0 and my tests are invoked on the CI server using

dotnet test path/to/project --logger trx --results-directory d:\a\_temp -c Release --no-build

This command “just works” with xUnit, but apparently not Expecto.

Is there any way to make Expecto stack traces available to Azure Pipelines? Is this something that must be implemented by Expecto, or something I must configure? If the latter, could it perhaps be changed to “just work”, like xUnit?

[haf]

I know what that’s like 😉. At least with this thread it’s clearly documented what needs fixing and it’s not even a big fire that stacktraces don’t show up, so we can let it be right now until one of us has time to pick it back up.

[haf]

Good point! However, it requires a bit of remaking of the Expect module, responsible for printing the errors.