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: 

FAIL: Artifact sharing results in "test cases were expected but none were found"

Peter Kahn
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 30, 2015

Hi all,

 

I hoped Atlassian fixed this between 4.4.2 and 5.8.1 but apparently not.  I have a two stage plan:

  1. Test:   jobs: test win, test lin  - share surefire reports
  2. Report:  depend on shared artifacts from previous jobs and scan to report test failures
    Pick up test results that were created outside of this build  is checked....

Result:

  • Report publishes the test files as artifacts (good)
  • JUnit scanner failes to detect the files (bad)  

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

 

I've worked around this before by moving and touching files. It is somewhat lame but easily done. 

 

Let me know if you have a better solution

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Peter Kahn
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 30, 2015

Ooops, that wasn't the case.  I had the wrong path, which means Atlassian did fix the bug between 4.4.2 and 5.8.1.  sorry guys and thanks

 

Peter

TAGS
AUG Leaders

Atlassian Community Events