I have made a change which should hopefully resolve the exception, though I'm honestly not sure why there was any to begin with, as I don't think we should need concurrent containers here. xunit/visualstudio.xunit@e2c61c2
\nThat's not going to resolve the problem where ADO appears to be asking to run multiple test cases with the same unique ID, but it should at least convert it from an exception back to the warning message that it should've been.
\nAvailable in 3.0.3-pre.3
https://xunit.net/docs/using-ci-builds
-
I am receiving the following error when I try to run unit tests in azure devops using VSTest. How to identify which test cases are causing the issue?
|
Beta Was this translation helpful? Give feedback.
-
Can you provide a repro project? Thanks! |
Beta Was this translation helpful? Give feedback.
-
I'm actually getting the same error when i use the following properties for VSTest task in ADO:
Without it - no such error from xunit. From what i've heard without these options vstest.console is being called, while with them some service api is used |
Beta Was this translation helpful? Give feedback.
-
I have a feeling we'll be redirected back to xunit, since xunit is the one that fails :) I'll probably open a discussion there, not keeping my hopes up tho Logs are similar to what OP was mentioning. Somewhere in the middle of the run, in between passed tests, i see several failures:
I don't know what these keys are, but they do look same. If you know how these keys are assigned and what the expectation is from them - i can provide this information to the discussion in vstest From what i've heard setting custom batch size results in invoking vstest via translation layer, instead of cmd. Somehow this results in catastrophic failure somewhere in the middle here |
Beta Was this translation helpful? Give feedback.
-
I have made a change which should hopefully resolve the exception, though I'm honestly not sure why there was any to begin with, as I don't think we should need concurrent containers here. xunit/visualstudio.xunit@e2c61c2 That's not going to resolve the problem where ADO appears to be asking to run multiple test cases with the same unique ID, but it should at least convert it from an exception back to the warning message that it should've been. Available in |
Beta Was this translation helpful? Give feedback.
I have made a change which should hopefully resolve the exception, though I'm honestly not sure why there was any to begin with, as I don't think we should need concurrent containers here. xunit/visualstudio.xunit@e2c61c2
That's not going to resolve the problem where ADO appears to be asking to run multiple test cases with the same unique ID, but it should at least convert it from an exception back to the warning message that it should've been.
Available in
3.0.3-pre.3
https://xunit.net/docs/using-ci-builds