TestDriven.NET by Jamie Cansdale

Sweet! Thanks!

TestDriven.Net (formally NUnitAddIn) version 1.1 is now available.
From Jamie’s blog, “I've...

Hi there. I've just downloaded and tried this new version on VS2003, and test solution no longer works. I can right click on a project and test that, but when I right click on a solution and select "Run tests", the solution is built, but nothing happens about the tests.

I can right click and select run in nunit gui, and I get a process invocation exception.

Hope this helps!

Matt

Why isn't this setup listed in the download area of the TestDriven.net site?

I can build MbUnit OK but the resulting MSI is no good. Can someone do a binary release of MbUnit?

G.

Graeme,

What do you mean by no good? I know there isn't a GUI or anything, it is supposed to silently install.

Jens,

This build is just experimental. I wanted a few people to test it before announcing it on the main site.

Hi Jamie,

Installing the MSI gives the following error:

=== Logging started: 05/05/2005 13:15:14 ===
Action 13:15:14: INSTALL.
Action start 13:15:14: INSTALL.
Action 13:15:14: ValidateProductID.
Action start 13:15:14: ValidateProductID.
Action ended 13:15:14: ValidateProductID. Return value 1.
Action 13:15:14: CostInitialize. Computing space requirements
Action start 13:15:14: CostInitialize.
Action ended 13:15:14: CostInitialize. Return value 1.
Action 13:15:14: FileCost. Computing space requirements
Action start 13:15:14: FileCost.
Action ended 13:15:14: FileCost. Return value 1.
Action 13:15:14: CostFinalize. Computing space requirements
Action start 13:15:14: CostFinalize.
Action ended 13:15:14: CostFinalize. Return value 1.
Action 13:15:14: ExecuteAction.
Action start 13:15:14: ExecuteAction.
Error 1305. Error reading from file X:\mbunit\src\src\build\MbUnit.msi. System error 1008. Verify that the file exists and that you can access it.
MSI (c) (A0:4C) [13:15:24:140]: Product: MbUnit -- Error 1305. Error reading from file X:\mbunit\src\src\build\MbUnit.msi. System error 1008. Verify that the file exists and that you can access it.

Action ended 13:15:24: ExecuteAction. Return value 3.
Action ended 13:15:24: INSTALL. Return value 3.

Needless to say, the file exists and I can access it. :)

IIRC the files are stored in a cabinet within the MSI and my guess is that it's corrupted in some way, or that there's a space there for it but it hasn't been put in the file. I can load the MSI in Orca and see the tables, but if I save the MSI back out from Orca it shrinks down to a few KB, which I suppose would be without the cabinet.

Hi,

We're using TestDriven w/VS 2005 Beta 2 (April rel.). VS 2003 is not installed. We use the installer you link to on this page.

It sorta works but there are problems:

- If you try to Run Test(s) on the solution level of one of our solutions, VS reports an internal error.

- Running tests on the project level or individual files works fine.

- Running the same tests w/Debugger doesn't provide the expected output, instead we get error messages:

Managed Debugging Assistant 'LoadFromContext' has detected a problem in 'C:\Program Files\TestDriven.NET 1.1\ProcessInvocation.exe'.

(See below for the entire output, with some long path names stripped out).

You can run with debugger, set breakpoints and the test seems to work (you can singlestep through it and it does what you would expect). But the output still does not report success/failure, you see the attached trace. The trace also reports exceptions from the app we're testing. Exceptions that are not reported when running w/out debugger.

Thanks,
Tommy

Output from Test With Debugger:

'Managed': Loaded 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Managed': Loaded 'C:\Program Files\TestDriven.NET 1.1\ProcessInvocation.exe', No symbols loaded.
'Managed': Loaded 'C:\Program Files\TestDriven.NET 1.1\TestDriven.TestRunner.Server.DLL', Symbols loaded.
'Managed': Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Managed': Loaded 'C:\Program Files\TestDriven.NET 1.1\TestDriven.TestRunner.DLL', Symbols loaded.
'Managed': Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Managed': Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Runtime.Remoting\2.0.0.0__b77a5c561934e089\System.Runtime.Remoting.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Managed': Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Managed': Loaded 'C:\Program Files\TestDriven.NET 1.1\EnvDTE.DLL', No symbols loaded.
'Managed': Loaded 'C:\Program Files\TestDriven.NET 1.1\TestDriven.Framework.DLL', Symbols loaded.
Managed Debugging Assistant 'LoadFromContext' has detected a problem in 'C:\Program Files\TestDriven.NET 1.1\ProcessInvocation.exe'.

Additional Information: The assembly named 'NUnitAddin.NUnit' was just loaded from 'file:///C:/Program Files/TestDriven.NET 1.1/NUnit/NUnitAddin.NUnit.dll' using the LoadFrom context. In almost all cases, it is recommended that assemblies be installed in the Global Assembly Cache or in the ApplicationBase directory so that the Load context is used.

See C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\sdk\bin\mdaBoilerplate.exe.mda.config for documentation.'Managed': Loaded 'C:\Program Files\TestDriven.NET 1.1\NUnit\NUnitAddin.NUnit.dll', Symbols loaded.
Managed Debugging Assistant 'LoadFromContext' has detected a problem in 'C:\Program Files\TestDriven.NET 1.1\ProcessInvocation.exe'.

Additional Information: The assembly named 'nunit.core' was just loaded from 'file:///C:/Program Files/TestDriven.NET 1.1/NUnit/nunit.core.DLL' using the LoadFrom context. In almost all cases, it is recommended that assemblies be installed in the Global Assembly Cache or in the ApplicationBase directory so that the Load context is used.

See C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\sdk\bin\mdaBoilerplate.exe.mda.config for documentation.'Managed': Loaded 'C:\Program Files\TestDriven.NET 1.1\NUnit\nunit.core.DLL', Symbols loaded.
'Managed': Loaded 'C:\src\...Publisher\bin\Debug\Publisher.DLL', Symbols loaded.
'Managed': Loaded 'C:\src\...Publisher\bin\Debug\nunit.framework.DLL', No symbols loaded.
'Managed': Loaded 'C:\src\...Publisher\bin\Debug\Core.DLL', Symbols loaded.
'Managed': Loaded 'C:\src\...Publisher\bin\Debug\Expose.DLL', Symbols loaded.
Managed Debugging Assistant 'LoadFromContext' has detected a problem in 'C:\Program Files\TestDriven.NET 1.1\ProcessInvocation.exe'.

Additional Information: The assembly named 'nunit.framework' was just loaded from 'file:///C:/Program Files/TestDriven.NET 1.1/NUnit/nunit.framework.DLL' using the LoadFrom context. In almost all cases, it is recommended that assemblies be installed in the Global Assembly Cache or in the ApplicationBase directory so that the Load context is used.

See C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\sdk\bin\mdaBoilerplate.exe.mda.config for documentation.'Managed': Loaded 'C:\Program Files\TestDriven.NET 1.1\NUnit\nunit.framework.DLL', Symbols loaded.
'Managed': Loaded 'C:\src\...Utilities.DLL', Symbols loaded.
'Managed': Loaded 'C:\src\...\bin\Debug\log4net.DLL', No symbols loaded.
A first chance exception of type '....AEDataException' occurred in Publisher.DLL
A first chance exception of type '....AEDataException' occurred in Publisher.DLL
A first chance exception of type '....AEDataException' occurred in Publisher.DLL
A first chance exception of type '....AEDataException' occurred in Publisher.DLL
The thread 0xf44 has exited with code 0 (0x0).
The program '[1956] ProcessInvocation.exe: Managed' has exited with code 0 (0x0).

Hi Jamie,

the "restart" comnmand available in 1.0 is gone in this 1.1 release, I found it really useful, would really appreciate if you would put it back in!

Best regards!
/marcus