sounds good

--  
Krzysztof Kozmic


On Wednesday, 31 July 2013 at 10:59 PM, Jake Ginnivan wrote:

> In TestStack.ConventionTests.Tests/TypeBasedConventions.cs:
> > > public TypeBasedConventions() > { > - itemsToVerify = typeof(SampleDomainClass).Assembly.GetTypes(); > + // TODO: This should go to some sort of autodiscovery mechanism so users don't have to see this shit > + Convention.Settings.AssertInclunclusive = Assert.Inconclusive;  
> nCrunch looked good, and I know xUnit is fine with it.
> They are setup for showing any sort of exception, because often tests fail because of a null reference exception, or some other sort of exception. Any sort of exception has to be readable.
> I don't beleive any runner does anything special with their assert exception types, they are just custom exceptions which the framework throws.
> Also frameworks like shouldly would throw their own custom exceptions
>  
> —
> Reply to this email directly or view it on GitHub (https://github.com/TestStack/ConventionTests/pull/16/files#r5502304).
>  
>  
>