Comments on: Resharper 5.1’s Test Runner Is Broken

By: SleeperSmith

SleeperSmith — Tue, 27 Sep 2011 02:03:00 +0000

“Rest assured that we do, far beyond you could imagine.”

And it’s exactly people like YOU that made bugs like this appear. As explained later:
“Unfortunately, we didn’t had the other case in our regression testing” after you guys reverted back to NUnit 2.5.2.

In plain English. YOU HAD THE TESTS BEFORE NOW YOU DON’T. Don’t come out here bashing people acting all knowledgeable when your process failed right in front of you. Whether it was a human error or a process problem, it doesn’t matter. No one cares. You shipped a product with a bug that it didn’t have before and is a behaviour you guys ALREADY IDENTIFIED.

Yeah, you know why that Lotus you bought earlier broke down? Oh because the Toyota engine in it has problem. Tell me you would swallow that.

Oh no wait, NUnit is a closed source software and you can’t do anything about it, am I right?

Another developer with no business perspective as usual. I love JetBrains. But your attitude just plain stinks.

By: Chris Mccall

Chris Mccall — Mon, 25 Jul 2011 16:12:00 +0000

Don’t you think Jetbrains has been punished enough for this bug? Have some courtesy, they are a very productive and reliable vendor, and it’s unlikely you would be as successful in your work without them. We get it: you found a bug and it’s stopping you from running a few of your tests. Relax and let the vendor fix it. Maybe a copy of the developer’s pink slip and a photo of a Christmas tree with no gifts under it will satisfy your thirst for revenge?

By: Chris

Chris — Mon, 13 Dec 2010 22:01:54 +0000

I’m getting the same issue on the latest Resharper version (5.1.1753.4) and it is running NUnit 2.5.7 according to the Resharper –> Options –> Unit Test –> NUnit. This completely screws all of our tests.

By: Davy Brion

Davy Brion — Wed, 28 Jul 2010 07:21:36 +0000

@Martin

if their last 2 releases had major issues for me, both of which i believe should never have made it into a released version then i have every right to react the way i do

it’s not because they’re JetBrains that they can get a free pass

By: Martin Aatmaa

Martin Aatmaa — Wed, 28 Jul 2010 06:46:05 +0000

For the record, I think you were being a tad harsh on Jetbrains on this.

I’m actually even more impressed with them as a result of this. Keep up the great work and support guys!

By: Davy Brion

Davy Brion — Tue, 20 Jul 2010 07:55:46 +0000

for future reference, the path1 thing was indeed a resharper bug and has been fixed:
http://twitter.com/resharper/status/18943045975

By: Davy Brion

Davy Brion — Mon, 19 Jul 2010 07:31:05 +0000

@Bill

you’re right… enabling shadow-copying makes it work

i usually turn it off though since we sometimes get bad results because of it

By: Alexey Petriashev

Alexey Petriashev — Mon, 19 Jul 2010 07:27:30 +0000

@Bill

Yes I checked “Shadow-copy” and Nunit 2.5.5 started

By: Bill Blinn

Bill Blinn — Mon, 19 Jul 2010 02:53:58 +0000

@Davy

Things worked fine for me when I was using NUnit 2.5.5 with the tests written into the super class. But as soon as I unchecked Tools -> Unit Testing -> Shadow-copy assemblies being tested, the error with path1 started happening.

Let me know if you guys are seeing the same thing/have a fix.

By: G-Mac

G-Mac — Sat, 17 Jul 2010 23:10:04 +0000

For what it’s worth, the NUnit 2.5.5 workaround worked for me. Thanks Davy and Ilya!

By: Alexey Petriashev

Alexey Petriashev — Thu, 15 Jul 2010 11:39:29 +0000

Specified Nunit installation does not work for me.
Failed to load test assembly…
VS2010, Nunit 2.5.5 (with alone 2.5.2 same error)

By: Davy Brion

Davy Brion — Thu, 15 Jul 2010 07:15:46 +0000

@Ilya

yeah, that works as expected

By: Ilya Ryzhenkov

Ilya Ryzhenkov — Thu, 15 Jul 2010 06:16:35 +0000

@Davy, could you please try using NUnit GUI of the respective version to run your tests? Does it work without any problem?

By: Davy Brion

Davy Brion — Wed, 14 Jul 2010 14:43:56 +0000

@Valeriu

tried both, same result :s

By: Valeriu Caraulean

Valeriu Caraulean — Wed, 14 Jul 2010 14:40:34 +0000

@Davy
I’m not sure it’ll make a difference, but I’ve got NUnit by unzipping in my “Tools” folder. Same as it was suggested by Ilya. And you were using the installer and putting it to “Program Files”…

By: Davy Brion

Davy Brion — Wed, 14 Jul 2010 14:15:13 +0000

@Ilya

i get the same exception when trying this with NUnit 2.5.3 :s

By: Ilya Ryzhenkov

Ilya Ryzhenkov — Wed, 14 Jul 2010 14:12:47 +0000

@Valeriu great to see it helped you, thanks for posting info in YouTrack!

By: Ilya Ryzhenkov

Ilya Ryzhenkov — Wed, 14 Jul 2010 14:11:48 +0000

@Davy, TaskException is just a wrapper for real exception occurred in remote AppDomain (in separate process), so that it can be serialized and delivered to Visual Studio. I agree that diagnostics could be a little bit better. I’m here to try to help you have a working environment while we are investigating things on our side. If you can find NUnit 2.5.3 (shipped with ReSharper 5), you could try that and see if it works. If it does, it could give us more info in our work with NUnit guys on solving this issue. Thanks for being with us

By: Valeriu Caraulean

Valeriu Caraulean — Wed, 14 Jul 2010 13:56:45 +0000

@Ilya
Suggested workaround worked for me…

I’ve posted this solution also in your bug tracker, so that people that is coming and voting for the issue can continue use Test Runner.

By: Davy Brion

Davy Brion — Wed, 14 Jul 2010 13:18:06 +0000

@Ilya

btw, the fact that you guys don’t have any “path1″ parameter doesn’t mean you can’t look for the reason of the exception… it is throwing a JetBrains.ReSharper.TaskRunnerFramework.TaskException so it is coming from your software _somewhere_

regardless of whether this is an NUnit bug or not, this entire experience (the test runner’s problems in general) is really hurting the confidence that i used to have in you guys and i’m betting i’m not the only one