NCrunch can't find Record.ExceptionAsync with latest version of xUnit

bgeihsgt

#6987 11 years ago 17 Feb 2015 00:07 UTC

Repro:

Create an xUnit test with Record.ExceptionAsync against the latest build of xUnit (build 2857).

Result:

This test will always fail in NCrunch because it can't find Record.ExceptionAsync in xunit.core. After some investigation, the Record class was moved in to core 5 days ago via this commit:

https://github.com/xunit/xunit/commit/6d008db61fb32adb66cadd2dee8a009fa471d016

I noticed that NCrunch is using build 2700 at the moment.

While you are investigating, is there a way I can override which version of xUnit NCrunch uses?

Remco NCrunch Developer

#6988 11 years ago 17 Feb 2015 00:22 UTC

Hi, thanks for sharing this.

NCrunch is integrated with the version of xUnit packaged with the NCrunch binaries. Because of the design of xUnit and NCrunch's integration with it, this integration cannot be redirected arbitrarily to a different version of xUnit.

This presents some problems when dealing with development builds and frequent releases of xUnit V2, because proper support for changes such as this one would require a full new build of NCrunch to work with the new version of xUnit. It also means that such a new build of NCrunch also wouldn't be backwards compatible with older versions of xUnit V2.

If using xUnit in pre-release state is important in your project, all I can recommend at this point in time is that you use the version of xUnit that is aligned/compatible with the version of NCrunch you are working with. NCrunch's integration with xUnit is updated regularly for the major milestone releases.

bgeihsgt

#6989 11 years ago 17 Feb 2015 00:30 UTC

Thanks Remco. Running against the bleeding edge of xUnit is important to our team because Brad Wilson is on our team :P I guess I'll just wait until the next build of NCrunch comes with a stable release of xUnit. Should I say anything to Brad relating to this (i.e. should I tell him not to move the code to a different assembly because it breaks your integration?)

Remco NCrunch Developer

#6990 11 years ago 17 Feb 2015 00:37 UTC

bgeihsgt wrote:Thanks Remco. Running against the bleeding edge of xUnit is important to our team because Brad Wilson is on our team :P I guess I'll just wait until the next build of NCrunch comes with a stable release of xUnit. Should I say anything to Brad relating to this (i.e. should I tell him not to move the code to a different assembly because it breaks your integration?)

That is the single best excuse for bleeding edge adoption I've heard .. well.. ever :)

I'm happy with discuss options with Brad if he feels a little cornered by this. I think he was talking earlier about RC2 of xUnit V2 being ready soon, so this would be a good milestone to realign NCrunch with. As soon as RC2 is locked off, I should be able to get your team an early build without needing a full NCrunch release behind it. My big fear right now is that if I integrate with a new dev build of xUnit, it will break the integration for users running older versions... If we can avoid this, then I think the change can be accommodated.

bgeihsgt

#6991 11 years ago 17 Feb 2015 20:48 UTC

Thanks Remco -- The RC2 is available here. An early build of NCrunch would be awesome, thanks!

http://xunit.github.io/release-notes/2015-02-17.html

Remco NCrunch Developer

#6995 11 years ago 18 Feb 2015 05:17 UTC

bgeihsgt

#7001 11 years ago 20 Feb 2015 00:07 UTC

Thanks for the private build, Remco. Really appreciate it. Since installing the private build, we've been noticing that NCrunch will spin indefinitely without doing any work. We're doing xUnit in Static analysis mode. I've tried to switch to dynamic but that ends up with its own problems. Anything I can send you to help investigate?

Remco NCrunch Developer

#7002 11 years ago 20 Feb 2015 02:12 UTC

bgeihsgt wrote:Thanks for the private build, Remco. Really appreciate it. Since installing the private build, we've been noticing that NCrunch will spin indefinitely without doing any work. We're doing xUnit in Static analysis mode. I've tried to switch to dynamic but that ends up with its own problems. Anything I can send you to help investigate?

I strongly recommend using DynamicAnalysis as with the range of detailed features you guys are using, this will give you the best support.

Can you share any sample code that can make these problems appear? You're welcome to submit code via the contact form.

Post a reply