Hi Brian, I'd be interested to hear what unexpected exceptions were being thrown when you debugged using TestDriven.Net. It should work fine with 64-bit versions of Windows - I've this on a few people's machines. However I don't use a 64-bit version of Windows myself, so there may still be a few kinks to work out. Were you using TestDriven.Net 2.0 or the latest Beta?
Regards, Jamie. -- http://www.testdriven.net http://weblogs.asp.net/nunitaddin On 7/20/07, brian macdonald <[EMAIL PROTECTED]> wrote: > > By the way, thank you guys very much for answering my questions thus > far. They have been very helpful, and I'm making my new journey into > using MbUnit quite public at this point. :) > > Anyway, here's the situation > > Visual Studio Test System has been dropped from our testing framework > altogether. We removed all references and calls from our code. The > Test View has decided to hang then crash VS 2005 altogether every time > we try to load it... even if we comment out all Test class and test > method attributes. We can't afford to waste time supporting VSTS > anymore. > > The problem is: now we don't have am immediate way to do line-by-line > debugging of our unit tests. I've been able to create an empty > console project that calls the MbUnit Console as an external program > and do it that way. However, this method doesn't allow any developer > or tester to download this from depot, run a program, and choose a > test that he or she wants to run at will. He or she has to hand-edit > the debug properties of the empty console project. > > I've downloaded and tried TestDriven.NET, and it just didn't work. It > was a chore to get TestDriven to allow line-by-line debugging. (Test > With-> Debugger always threw exceptions beyond what was documented.) > More importantly, we have developers on 64-bit versions of Windows XP, > which TestDriven.NET does not support according to its liner notes. > In brief: TestDriven.NET is not an option. > > So, my question is: what now? All i would need is to create a small > Window App with a simple interface that would allow a user to choose a > test (or tests) to run, the launch a process that would call the > MbUnit Console and pass those filters to the MbUnit Console's > parameters, then line-by-line debug our test assemblies that way. > > The problem HERE is: I can't get this external MbUnit Console process > to attach to VS 2005's debugger. I've been experimenting with calls > available via the Systems.Diagnostics library, but to no avail so far. > > Have any of you been able to successfully attach your debugger, via > vode, to an external process that launches the MbUnit Console without > using TestDriven.NET? > > Many thanks in advance once again. > > Brian MacDonald > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
