In fact, I think this used to exist so maybe I just can’t find it anymore. The test analytics are significantly less useful for me now since I can’t see the context for the test failure.
We currently do not have a way to link from a test to an exact line number to a job from a build. However, we do have a link from a test run to the Build number from the UI as shown below from the screen shot.
But from a build’s job, there is the View in Test Analytics button and a Tests tab that provides test results and descriptions executed in that job.
Thanks for looking into this and suggesting a workaround. Linking to the build is not too bad if the whole container failed and there aren’t too many failed containers to check
The execution probably already has access to the line number, since it’s displaying the actual line in the code block so hopefully it wouldn’t be difficult to also provide a link.
Thanks for the added context and use case. I understand that a link back to the job with the failed test would be useful here. Let me raise this as a feedback to our product team.
Thanks for reporting this, and apologies for not updating you sooner.
We had a regression in some recent overhaul work where the links from an execution back to a build from Test Engine (formally known as Test Analytics) did not go to the correct job, e.g. container 21 in your example above.
We rolled out a fix for this regression on 2024-10-04, so those links should now take you to the correct job.
We currently do not have a way to link from a test to an exact line number to a job from a build.
As you mentioned, we show the error text from the test failure on the execution page, but this is collected independently from the job log text shown on the build page. Unfortunately we don’t currently have any way to connect those 2 together, so we can’t link directly to the exact line of the failure on the build page.
Thanks again for the post, and hopefully the navigation will be a little better for you now!
