This project is read-only.
1

Closed

xUnit runner doesn't recognize Theory tests

description

Running a test project through statlight with the following results in zero tests run, whereas running it in the browser shows two tests:
 
[Theory]
[InlineData( true )]
[InlineData( false )]
public void this_theory_might_pass( bool shouldPass ) {
Assert.True( shouldPass );
}
 
I noticed in the changeset associated with http://statlight.codeplex.com/workitem/13078 that both XUnitLight and XUnitContrib result in the same UnitTestProviderType.XUnit value being returned, rather than the XUnitContrib runner.
Closed Mar 2, 2011 at 12:40 AM by staxmanade
https://github.com/staxmanade/StatLight/commit/b2312eb7dc660c67aec0f21f3daa9411c136a631

comments

staxmanade wrote Mar 1, 2011 at 3:05 AM

The changeset was to add "autodetection" of xunit contrib in a xap. So you don't have to specify the -o parameter.

As an immediate work around, you can give it the -o=MSTestWithCustomProvider.

EmperorXLII wrote Mar 1, 2011 at 2:47 PM

Thanks for the workaround (didn't know MSTestWithCustomProvider was an option). Any idea on when that workaround will show up in an official release?

EmperorXLII wrote Mar 1, 2011 at 7:44 PM

Using the workaround, I was able to get steady progress in the console window, but eventually received a "No communication from the web browser has been detected. We've waited longer than the configured time of 00:05:00" error. Since I was building StatLight locally to get MSTestWithCustomProvider, I just changed the timeout from 5 to 25 in the source (it didn't look like there was a command-line parameter to configure it). However, since I got continuous output to the console, I'm unsure why it said there was no communication?

staxmanade wrote Mar 2, 2011 at 12:22 AM

Unsure on an official build as of yet. Possibly in a month...

Regarding the 5:00 min timeline, yes it's not configurable. StatLight is making an assumption that if it hasn't received a test message (5 minutes or less) it thinks something really bad has happened and will kill itself off.

Can you reproduce the timelimit you experienced and do you think it's a real issue w/ StatLight? or did you actually have a test that took over 5 minutes to run?

staxmanade wrote Mar 2, 2011 at 12:39 AM

FYI: the trunk has the autodetection now using the MSTestWithCustomProvider as the default - https://github.com/staxmanade/StatLight/commit/b2312eb7dc660c67aec0f21f3daa9411c136a631

wrote Mar 2, 2011 at 12:40 AM

wrote Feb 14, 2013 at 9:18 PM

wrote May 16, 2013 at 10:50 AM