Both the MbUnit3 and MbUnit2.4 tests were run using Gallio 3.0.5 via the Gallio NAnt task, which spun up Gallio.Host.exe, and the NCover2 runner. So the MbUnit2.4 tests were using the adapter. So it is definitely a difference in the frameworks, not the runner. Using the isolated process runner, I saw a similar difference in performance. The local runner showed a difference as well, but not as pronounced.
James On Nov 19, 5:20 pm, "Jeff Brown" <[EMAIL PROTECTED]> wrote: > Were you running those MbUnit 2.4 tests using Gallio as well (via Gallio's > MbUnit v2 adapter) or with the native tools. > > In any case, performance is a big ticket issue for Gallio in the v3.1 > timeframe. Basically, we've learned a lot from the v3.0.* experience, we've > got some great tools, but we have to tweak a few of our early assumptions. > > When that's done... it'll be awesome. ;-) > > Jeff. > > On Wed, Nov 19, 2008 at 11:55 AM, ARKBAN <[EMAIL PROTECTED]> wrote: > > > I have on a previous upgrade from MbUnit 2.4 to 3.0.2 or 3.0.3 (I forget > > which). I have about 1000 unit tests, which take 45 secs on MbUnit 2.4 > > and 2+ minutes on MbUnit 3. I'm using .Net 2.0 and none of the > > frameworks you are using, so I think its MbUnit. > > > I plan to test with MbUnit 3.0.5 but by the time I get a chance 3.0.6 > > will probably be released : ( > > > ARKBAN > > > James Kovacs wrote: > > > On a current project, I upgraded from MbUnit 2.4 to Gallio 3.0.5. Test > > > execution times skyrocketed. The test suite is a reasonable size at > > > 694 tests - mostly unit with some integration. I tried running the > > > test suite under Gallio compiled for MbUnit2.4 and MbUnit3. The tests > > > are run with NCover2 integration using the Gallio NAnt task. > > > > MbUnit3 under NCover2 > > > Run#1 272.553s > > > Run#2 278.308s > > > > MbUnit2.4 under NCover2 > > > Run#1 165.769s > > > Run#2 145.258s > > > > The only code difference is correcting some minor syntactic > > > differences between MbUnit2.4 and MbUnit3, notably the > > > ApartmentStateAttribute on two test classes. Unfortunately I can't > > > share the code since it is a client project. I'm wondering if anyone > > > else has encountered this when upgrading to MbUnit3? I'm using a > > > fairly standard tool stack - .NET 3.5, Rhino Mocks, Oracle, Castle > > > Windsor, ... I just can't quite understand why MbUnit3 performance is > > > so much worse than MbUnit2.4. On the build server, which has a lot > > > less horsepower than my dev machine, it's taking around 8 minutes for > > > the build with MbUnit3 whereas it was around 4 minutes with MbUnit2.4. > > > Because of this, I've had to revert to Gallio running MbUnit2.4. Any > > > thoughts or suggestions would be appreciated. > > > > Thanks, > > > James --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
