Assert.Inconclusive causes an error (RED icon) in Visual Studio 2012 - by PaoloPablito

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 772936 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 11/30/2012 3:29:49 AM
Access Restriction Public


When running automatic tests, Assert.Inconclusive causes an error (RED icon) in Visual Studio 2012. 
In previous versions it caused a warning (YELLOW icon), so that I could easily distinguish inconclusive tests from failed tests. I consider this as a a regression.

Note that for me "inconclusive" means: "the test has an important prerequisite that wasn't satisfied, so I could not run this tests", this must NOT be an error, but a warning to me to apply the prerequisite. 
Consider that I don't use the testing features of VS only for unit tests, but also to automate more complex integration tests that sometimes involve files and the database. On some test machines I cannot apply some prerequisites, and I know it, so I often don't care if some tests are "Inconclusive", but I want to spot the ACTUAL failures immediately.
Sign in to post a comment.
Posted by Joshua [MSFT] on 12/17/2012 at 10:50 AM

Thanks for this valuable feedback. The Assert.Inconclusive status is a difficult issue, as some developers consider it a cause for failure and some do not. We do track this feedback and evaluate the correct course of action. The suggestion of a check box configuration flag is an interesting one we will keep in mind moving forward.

Joshua Weber
Posted by PaoloPablito on 12/7/2012 at 2:56 AM
p.s. A suggestion: you may add an Option that allows us to say "treat inconclusive tests as warnings / as errors". After all, you already have the "treat compiler warnings as errors" option...
Posted by Microsoft on 12/3/2012 at 1:11 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Macy [MSFT] on 11/30/2012 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(