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

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

Accepted Answer
0 votes

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

428 views 0 8
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you