Summary

I spend endless time looking for the right log in azdo to see where my errors are and what is their content. I need to:

• click on the PR
• go to build report
• go click some of the builds
• click the link to azdo build
• click on the build number to land on the main page
• click on tests, and hope it was not a crash that killed the run
• look at errors that are reported
• if there is a crash, look for the log and find where the log is, hope it is uploaded
• then hope that the error message has enough information / assertion failure is not just Assert.True expected true but was false.

I would much prefer to see the errors directly in the source code, under the line that failed.

I am not sure if this is problem with out arcade based setup, with MTP of mix of both. I do think that VSTest did this, but I don't see any reference to the ## api in vstest code, so maybe I am imagining stuff or it was vstesttask post processing TRX.

https://grep.app/search?f.repo.pattern=vstest&q=logissue

We do have similar integration in Pester pester/Pester#1996 where it works well.

https://github.com/pester/Pester/blame/main/src/functions/Output.ps1