On Mon, 2009-03-02 at 09:29 +0100, Pascal Craponne wrote: > So, regarding DbMetal.exe problem, I don't believe this doesn't work. > There is a lot of ways to load an assembly, and NUnit probably just > can not restrict them.
Wait, what? So, the most important question: how do you normally run the unit tests? What are the exact steps that you follow to build and run them? If this is a case of "NUnit does things wrong," then does anybody regularly run the tests under NUnit? Or is all regular unit test execution done via the Microsoft testing framework? As mentioned earlier, what I'm doing is building the project files, which generates a .dll or .exe file, navigating to the output folder within Explorer, right-clicking the test assembly, selecting Run Tests from the context menu (which loads NUnit 2.4.8), then clicking the Run button within the NUnit GUI. Does anybody else do this? For those that do use NUnit, do the unit tests pass when there isn't a DbMetal.dll assembly? Thanks, - Jon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" 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/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
