Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
NCrunch Grid: How to debug error on grid server?
Options
Previous Topic Next Topic
GreenMoose
#1 Posted : Friday, February 7, 2014 4:40:08 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/17/2012(UTC)
Posts: 507

Thanks: 145 times
Was thanked: 66 time(s) in 64 post(s)
(Using Nunit).
Testing out the grid functionality for the first time.

I get a test error with the unfriendly message "TestFixtureSetUp failed in SomeFixture", so according to http://www.ncrunch.net/d..._distributed-processing I disabled processing on my local machine by setting "Max no of processing threds" to 0. But when I choose to debug the failing test, it starts debugging it on my (local) server. Maybe debugging on grid nodes isn't supported?

If so, what's the best way to find out the reason of failure? The test never executes, the opening bracket of test method is red indicating test failure, but rest of code is gray, including setups methods.

Thanks.
Back to top
Remco
#2 Posted : Saturday, February 8, 2014 12:27:09 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,123

Thanks: 957 times
Was thanked: 1286 time(s) in 1193 post(s)
Hi, thanks for posting.

Unfortunately, remote debugging on grid nodes is not yet supported by NCrunch. Because of this, if you try to debug a test when in 'grid only mode', the projects will build locally and the test will run locally.

Remote debugging is a complex area that requires either a very tricky infrastructure setup, or a large amount of high maintenance integration. It's something I'd been hoping to evaluate in future if the grid features proved to be very popular.

At the moment, the best way I know of to debug code that can only execute on a remote machine is by introducing Debug.Write/Console.Write statements into the code to learn more about how it is behaving. The continuous execution of the code by NCrunch combined with code coverage still makes this a more pleasant experience than it would be to debug tests in this way using a traditional test runner, but I agree it isn't ideal.


Cheers,

Remco
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.025 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download