Uploading NUnit TestResults brings error 500
Hi there,
I am trying to change my build into a matrix-based multi-job-stage environment.
By doing this I get an error 500 when posting test results (example attached), unclear to me why as it worked before.
Can't think of that the format has changed just between two days in a way that the server cant read it anymore? All other threads here leaded into this direction...
Best,
M.
- testResultsUnit.xml 12.3 KB
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Matthias on 11 Jun, 2020 06:45 PM
What changed indeed in the meantime is that I corrected the "Should" format in my Pester tests to be all dashed as latest Pester version wants to have it, so I changed quite a lot of
Should Be
intoShould -Be
and so on...might that be an issue here?Support Staff 2 Posted by Feodor Fitsner on 11 Jun, 2020 08:25 PM
Looking into that...
Support Staff 3 Posted by Feodor Fitsner on 11 Jun, 2020 08:33 PM
It crashes because parser expects
result
attribute in<test-case>
elements, but this test (and others below it) doesn't have it:We can fix that and deploy update to rely on
success
ifresult
doesn't exist? Don't know if you can do something on your side...4 Posted by Matthias on 14 Jun, 2020 09:37 AM
Hi Feodor,
thanks for having a look. I think I can't really do something about it. I assume it has to do with the latest Pester update to v5 where they changed quite a lot of important stuff.
This was just coming out of it as this.
Best,
M.
Support Staff 5 Posted by Feodor Fitsner on 16 Jun, 2020 03:42 AM
Sure, we will update our NUnit parser and deploy an update later this week.
Support Staff 6 Posted by Feodor Fitsner on 19 Jun, 2020 03:19 AM
Hi Matthias,
We've deployed a fix for NUnit XML test results parser.
Could you please give it a try and let me know how it worked.
Thanks for your patience!
7 Posted by Matthias on 19 Jun, 2020 11:41 AM
Hi Feodor,
thanks a lot. Seems to work now again.
Best,
Matthias
8 Posted by Matthias on 19 Jun, 2020 11:46 AM
Hi Feodor,
sorry...was too early: unfortunately it is not.
You can see the result at https://ci.appveyor.com/project/blindzero/connect-ms365/builds/3362...
You can see that 5 test are as failed. Those were not executed as the Pester tag was not executed.
Explained in detail:
I have to "tags" in Pester: "Unit" and "Integration".
In the step above only tag "Unit" is executed, maybe resulting in the empty XML-Results? Those are not executed and are not failed then.
Best,
Matthias
Support Staff 9 Posted by Feodor Fitsner on 20 Jun, 2020 02:42 AM
So, what would be the status of those tests: skipped?
10 Posted by Matthias Flesch... on 20 Jun, 2020 07:04 AM
Hi Feodor
Depends on what this status would define. Skipped would be ok, if the job is ok then and total is not including them.
Best
Matthias
Am 20. Juni 2020 04:42:08 MESZ schrieb Feodor Fitsner <[email blocked]>: