The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

What does the the automatic test reporting in pipelines look like when it's working

Federico Guardiola
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 7, 2018

In reference to https://confluence.atlassian.com/bitbucket/test-reporting-in-pipelines-939708543.html, I would like to know what that looks like when it's working. We are running cucumber-selenium tests in pipelines and generating junit xml results in:

./**/test-results/*.xml

But do not see anything in the UI that looks like it's locating the reports or tracking it. We clear the test directory after they finish running (using rm -rf of the parent directory), which may be responsible if the reporting step only runs after the entire pipelines run is completed (but before the instance gets torn down).

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Frank Harrison
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 22, 2018

We weren't seeing test results using boost::test because we didn't have both the log_sink and report_sink files being generated.

The log_sink needs to be in JUNIT format.

We run with the following switches, I hope it helps someone else:

<exe> --log_level=all --log_format=JUNIT --log_sink="$PWD/test-results/log_sink.xml" --report_level=detailed --report_format=XML --report_sink="$PWD/test-results/report_sink.xml" --use_alt_stack=1 --show_progress=1

 

TAGS
AUG Leaders

Atlassian Community Events