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: 

Failing task since test cases were expected but none were found.

Praful
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!
October 14, 2018

I have a Bamboo job for mulesoft code, with steps as code checkout, build, test which generates coverage report, deploy.
Test step is failing with message 'Failing task since test cases were expected but none were found.' and coverage report is generated in specific path.
When I remove the specific path, job is success but coverage is not generated.
I tried enabling 'maven return code', which makes the job success, but can't see coverage report.

1. Give the path **/target/*, enable maven return code - job success, coverage not generated
2. Give the path **/target/*, disable maven return code - job failed, coverage generated

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Gonchik Tsymzhitov
Community Champion
February 9, 2019

Hi! 

 

We add the artifact in Junit4 xml format and as final task works built-in Junit4 parser 

 

Hope it helps

 

Cheers,

Gonchik Tsymzhitov

TAGS
AUG Leaders

Atlassian Community Events