nunit: Running from console on visual studio solution fails due to non test assemblies
I am running my tests via mono on ubuntu and the tests are being found and passed just like they are from windows when I run them in NCrunch or the test runner in visual studio, the problem is my tests are being marked as failed because of the non-test assemblies containing the code being tested. Is there a way to ignore these NotRunnable assemblies to keep it from failing the tests?
The xml from the “Invalid” test is :
<test-suite type="Assembly" id="68-1" name="OutsideSources.DomainServices.dll" fullname="/home/toburn/Desktop/OutsideSources/OutsideSources.DomainServices/bin/Debug/OutsideSources.DomainServices.dll" testcasecount="0" runstate="NotRunnable" result="Failed" label="Invalid">
<properties>
<property name="_SKIPREASON" value="Unable to locate a driver for /home/toburn/Desktop/OutsideSources/OutsideSources.DomainServices/bin/Debug/OutsideSources.DomainServices.dll" />
</properties>
<reason>
<message>Unable to locate a driver for /home/toburn/Desktop/OutsideSources/OutsideSources.DomainServices/bin/Debug/OutsideSources.DomainServices.dll</message>
</reason>
</test-suite>
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 27 (16 by maintainers)
Commits related to this issue
- Support filtering project when nunit3-console is used with a solution. See issue #668 — committed to pcalin/nunit by deleted user 8 years ago
In 2.6.4 I could just tell nunit to run the solution file and it just worked. Because of that I never had to have nunit project files or maintain them or write XSLT or NAnt code to generate them or otherwise control the process outside of a single command line parameter. I honestly don’t understand why it isn’t obvious why someone would want to take the simplest approach. Anyway that involves creating an nunit project file is more complicated because you also need a tool to debug and write your test code.