Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,472
Community Members
 
Community Events
176
Community Groups

Failed NUnit tests show as skipped

I created a NUnit test and it works fine when everything passes, however once a test fails, then that test is shown as Skipped/Quarantined rather than failed. I found this issue which got solved by adding ";format=nunit2" to the result option. In our Bamboo version (7.0.3 build 70016) this gets done automatically already.

How to make Bamboo understand NUnit results?

Test result from log:

build	17-Nov-2020 14:49:39	Test Run Summary
build	17-Nov-2020 14:49:39	  Overall result: Failed
build	17-Nov-2020 14:49:39	  Test Count: 1, Passed: 0, Failed: 1, Warnings: 0, Inconclusive: 0, Skipped: 0
build	17-Nov-2020 14:49:39	    Failed Tests - Failures: 1, Errors: 0, Invalid: 0
build	17-Nov-2020 14:49:39	  Start time: 2020-11-17 13:49:30Z
build	17-Nov-2020 14:49:39	    End time: 2020-11-17 13:49:39Z
build	17-Nov-2020 14:49:39	    Duration: 8.910 seconds
build	17-Nov-2020 14:49:39	
build	17-Nov-2020 14:49:39	Results (nunit2) saved as TestResults.xml
simple	17-Nov-2020 14:49:39	Parsing test results under D:\Bamboo\xml-data\build-dir\TEST-TEST-TESTS...

 

1 answer

1 accepted

0 votes
Answer accepted

I think I fixed it. Needed to add

--result TestResults.xml;format=nunit3

 into the console parameters. It seems the NUnit parser expects nunit3 style, but the runner by default still produced nunit2 style

While this fixed the test showing incorrectly as skipped and it shows correctly as failed, it does not show the error log why it failed.

 

Edit: Turns out it does not show lines written to TextContext.Error. When using the error messages in Assert.Fail() or similar it works

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events