Hi community,
I'm struggling to make test reporting work on Bitbucket Pipelines.
- My maven project defines a couple of JUnit tests.
- Test reports are generated by maven surefire plugin on the right place at first glance.
This is an excerpt of my pipelines log:
+ pwd
/opt/atlassian/pipelines/agent/build
+ ls -lia target/surefire-reports/*.xml
5522980 -rw-rw-rw-. 1 root root 62399 Jul 15 15:54 target/surefire-reports/TEST-ut.com.nolddor.capgras.rest.model.SwitchAuthorizationTest.xm
Which looks like good, as xml reports are located in one of the default scanned paths following the documentation:
Configuring test reporting
To enable test reporting, make sure that build test reports are generated in one of the supported default locations (with a directory depth of 3 levels):
./**/surefire-reports/**/*.xml
./**/failsafe-reports/**/*.xml
./**/test-results/**/*.xml
./**/test-reports/**/*.xml
The test report file scanner will begin searching from the base directory of your build:
/opt/atlassian/pipelines/agent/build
Configuring test runners
Maven Surefire / Failsafe plugins
For Maven build jobs, no special configuration is required if you are using Maven Surefire Plugin or Maven Failsafe Plugin. The reports are automatically generated when the unit or integration maven test goals are executed.
Hello @Jack Nolddor _Sweet Bananas_
Thank you for the detailed description. It was very helpful!
Once I read It I went right away to test it myself and observe the same behavior. Which is:
If the test passes
You will only see them reported in the left panel beside the pipeline step name.
If the test fails
You will see a new tab with the reports for the tests that failed.
My first glance was to check our docs to see if this information was available there and it was:
Note: the Tests tab will only show if you have failed tests to review.
I guess I learned something today =]
Please confirm if this is the same scenario you see there otherwise we will need to investigate this a bit further.
Quite interesting and confusing behaviour hehehe
I expected to see Test tab whenever my build finished either fail or success.
Thanks for resolve this mistery.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess it was intended by design assuming that passed tests will not be reviewed.
I'm glad to be helpful!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It still can be useful to review the test results to analyze which tests take most of the suite time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey guys,
here is the ticket Bitbucket team created for this issue: https://jira.atlassian.com/browse/BCLOUD-15716
The current issue status is "Gathering Interest", so please go and vote for it if you are still interested.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for sharing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was scratching my head for a while as well - but same experience here. Successful tests do not show a tab, while failures do. Kinda stupid...but at least we know now :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the post. I got caught by this... for the 2nd time over the years perhaps. Upvoted the open issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.