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: 

[Feature Request] Support for Non-Unit-Test Results

Bryan Conner
Contributor
March 28, 2025

Bitbucket supports importing the results of failed tests which is useful for build pipelines. However, testing Linting or other non-critical failures still shows x/x tests failed.

Ideally, we should be able to tag the tests somehow to be unit-tests or other such that it handles the results differently. I would like to see for example:

6/483 Tests Failed
186 Warnings

Where the warnings would be things like Linting, and then tests failed is the traditional x number of unit tests were run, and y failed. With linting it always reports x/x (same value for each, 100% fail rate).

These changes would increase clarity of test results and improve the value of Bitbucket pipelines.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 31, 2025

Hi @Bryan Conner 

Thank you for your feedback. I've raised a feature request on your behalf with our developers, please Watch this for future updates and Vote for it to improve its visibility with regard to customer demand:

Cheers!

- Ben (Bitbucket Cloud Support)

DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events