TestDriven.NET Users Google Group

Feature Idea: Play a sound and display an icon when test run is completed

fabian.schm...@gmail.com (Fabian Schmied) — Mon, 21 Nov 2011 14:33:40 UT

Hi,
Here's a feature idea for TestDriven.NET: when a test run completes,
play back a sound and display an icon in the status bar. The icon
should be green when the test run has completed successfully, red when
the test suite has yielded an error, and yellow when there was a
skipped test. The sound should indicate whether there was an error

Re: Bug: Running all tests in a folder fails when the folder contains an nunit SetUpFixture class

michael.kett...@rubicon.eu (Michael Ketting) — Wed, 02 Nov 2011 13:24:25 UT

Hi Jamie!
Thanks for the quick response!
Considering your explanation, my sample was probably illconceived. I also
run into this problem when I have test fixtures before the setup fixture,
alphabetically speaking. Each class is in an individual source file. And
all classes belong to the same namespace. So, if I understood you

Re: Bug: Running all tests in a folder fails when the folder contains an nunit SetUpFixture class

jcansd...@gmail.com (Jamie Cansdale) — Wed, 02 Nov 2011 12:30:35 UT

Hi Michael,
This is a side effect of how TestDriven.Net executes its tests. Rather
than crawl the target assembly looking for tests, both the discovery
and execution of tests is delegated to the plugin test runners.
TestDriven.Net passes a test path to the test runner, rather that a
complete list of tests to be executed.

Bug: Running all tests in a folder fails when the folder contains an nunit SetUpFixture class

michael.kett...@rubicon.eu (Michael Ketting) — Wed, 02 Nov 2011 10:04:43 UT

Hi!
I have the folowing setup:
+ Folder
++ SubFolder1
------- SetUpFixture1
------- TestFixture1
------- TestFixture2
++ SubFolder2
------- TestFixture3
------- TestFixture4
When I try to run the nunit tests in SubFolder1 using TestDriven.NET, I get
the following error message: "You can't execute a namespace as an ad-hoc

Feature request: Rerun failed tests

fabian.schm...@gmail.com (Fabian Schmied) — Fri, 07 Oct 2011 07:18:42 UT

Hi,
I've got a feature request for TestDriven.NET: a command for rerunning
failed tests.
After performing a refactoring in big projects, I sometimes forget to
update a few tests, resulting on them failing. E.g., 3 failed out of
5000 tests. I then go and fix those tests and would like to repeat
running just them in order to ensure I actually fixed them.

Re: Solution: ProcessInvocation86.exe: Object is in a zombie state

jcansd...@gmail.com (Jamie Cansdale) — Wed, 25 May 2011 09:30:09 UT

Thanks for the sharing on this tricky issue! I haven't been able to
repro the issue here, so I've had to go on reports like these.
No, it doesn't terminate the test runner process. It simply detaches
from the process and leaves it running. I've ended up being super
paranoid about how I interact with the debugger due to hard to fix

Re: Solution: ProcessInvocation86.exe: Object is in a zombie state

fabian.schm...@gmail.com (Fabian Schmied) — Wed, 25 May 2011 08:41:10 UT

By the way, I can't seem to reproduce the issue with VS 2010 SP1. Has
anyone had the problem with SP1?
Fabian
On Wed, May 25, 2011 at 9:11 AM, Fabian Schmied

Re: Solution: ProcessInvocation86.exe: Object is in a zombie state

fabian.schm...@gmail.com (Fabian Schmied) — Wed, 25 May 2011 07:11:25 UT

Hi Zodman,
I also struggled with the problem. I think it is a race condition
between three actions:
1 - The Visual Studio debugger detects an uncaught exception.
2 - The Visual Studio debugger loads symbols for mscorlib and other
system assemblies that are on the call stack.
3 - The test runner process terminates due to the exception.

Solution: ProcessInvocation86.exe: Object is in a zombie state

carl.orion.scarl...@gmail.com (Zodman) — Mon, 23 May 2011 01:06:46 UT

I've been battling with this issue for quite some time (getting in a
zombie state when running TestDriven in the debugger). After a
lengthy but complete uninstall of VS2010 (including manually wiping
the registry and file system) I got rid of the issue, but it very
quickly came back.

In the end I narrowed it down to the import of my old Visual Studio

Re: ProcessInvocation86.exe: Object is in a zombie state

jcansd...@gmail.com (Jamie Cansdale) — Thu, 20 Jan 2011 10:48:56 UT

Hi Bryan,
Could you try deleting the contents of the following directory and let
me know if the problem persists:
%LOCALAPPDATA%\Temp\SymbolCach e
Regards,
Jamie.

ProcessInvocation86.exe: Object is in a zombie state

bslat...@gmail.com (Bryan Slatner) — Thu, 20 Jan 2011 05:43:03 UT

I'm working a small project with a fairly small number of tests, using
NUnit 2.4.8 and TestDriven.net 3.0.2749.

Sometime in the past couple of days, every time I debug a test --
whether it passes or fails -- I get a message that "Test Driven .NET
3.0 has stopped working". If I try to detach the debugger at that

Re: TestDriven.NET crashes when debugging - object is in a zombie state

fabian.schm...@gmail.com (Fabian Schmied) — Fri, 03 Sep 2010 10:53:25 UT

Yes, at the moment, it definitely looks like that's the problem. I've
managed to reproduce the issue on a co-worker's PC and experimented a
little more.
First, to narrow down the point of time of the crash, I've checked
what exactly the output window says. The crash definitely happens
after the assertion message is written to the window, but before the

Re: TestDriven.NET crashes when debugging - object is in a zombie state

jcansd...@gmail.com (Jamie Cansdale) — Fri, 03 Sep 2010 09:43:35 UT

I wonder if the process is crashing as VS attempts to detach the
debugger? I'm using the same command that a human would use when
detaching the debugger. If there's a bug in the VS / managed debugger
then TD.Net will be bitten by it. My only hope is to understand when
it occurs and attempt to work around the issue.

Re: TestDriven.NET crashes when debugging - object is in a zombie state

fabian.schm...@gmail.com (Fabian Schmied) — Fri, 03 Sep 2010 07:09:53 UT

There is only Microsoft Forefront Client Security.
Yes. All the systems I tested it on are.
It's really strange; when I wrote the original e-mail, I used to be
able to cause that problem every time I followed the steps outlined in
there. Now, however, I can't provoke the crash any longer. There must

Re: TestDriven.NET crashes when debugging - object is in a zombie state

jcansd...@gmail.com (Jamie Cansdale) — Thu, 02 Sep 2010 16:38:13 UT

Hi Fabian,
Thanks for the update.
I wonder if it might be something in the network stack that is causing
the process to crash. TestDriven.Net uses a TCP/IP channel to
communicate with its test process. In the past I've known network
security applications to cause .NET to crash. Is there any personal