[Open beta] Introducing Tests in Bitbucket Pipelines

[Samuel Mezger]

Hi @Rajkumar Singh ,

Yes, I use the Tests feature in Bitbucket Pipelines that you linked. This feature is what my comment is about, and this is why I posted it under this article about this feature.

As mentioned, this is about stdout output, not about the stack trace of failed tests. It is captured in the <system-out> Elements of the JUnit test report XML files. This information is valuable for us, regardless of whether tests failed or ran successfully.

Our workflow includes running Bitbucket Pipelines for building, testing and deploying, and the automated tests produce JUnit XML output. Tests may in some cases log some additional information to stdout. If logging to console, this is visible in the Pipeline step. If logging into JUnit XML, we can only see this output if we download the *.xml artifact and then open it. Potential for improvement in terms of user experience, and in terms of persistence of test results within Bitbucket Pipelines.