<< VSTS 2010 | Home | Quality WPF Testing Guide >>
Dan, check out Gallio
Posted on Friday, April 17, 2009 12:36 PM

I like Dan’s idea of local testing every time you build but I'm really lazy… I don’t want to make the effort install NUnit and getting tripped up with the #if statements. Some people have suggested a file watcher on the test dlls and then run mstest when they change.

As luck would have it, I came across Gallio. This is like NUnitGUI but work with other test frameworks (including MSTest). It didn’t however auto run the tests when the get recompiled :( So based on you don’t ask you don’t get (http://groups.google.com/group/gallio-dev/browse_thread/thread/bd0be2deef146c98) the team added this in.

Rich has download the latest version and is using while developing to make sure no tests fail. I’m sure there are more feature including VS integration. See http://www.gallio.org/

Gallio

(iMeta ppl; a version can be found in MIS)

Thanks again to Jeff Brown and Graham Hay.

7 Comments

Comments

# re: Dan, check out Gallio
Gravatar I found it to make VS very sluggish (latest beta I tried). Let me know if you have better luck
Left by HHariri on 4/17/2009 1:56 PM
# re: Dan, check out Gallio
Gravatar @HHariri
Some things to try if Gallio makes VS sluggish:

1. Disable the Gallio add-in for Visual Studio. The way Microsoft has defined the Visual Studio test integration provider pretty much guarantees sluggish behavior after every build when you have the Test View open (all work happens in the foreground).

2. Disable the Gallio plugin for ReSharer or upgrade to ReSharper v4.5 (most work happens in the background now). We have significantly improved the performance and most people seem pretty happy with it but it may slow things down a tad.

Good luck.

Also, Gallio has been out of Beta for quite some time. :-)
Left by Jeff Brown on 4/17/2009 5:35 PM
# re: Dan, check out Gallio
Gravatar @Jeff,

Thanks. I've actually got 4.5 for quite some time. I didn't try disabling the Gallio add-in for Visual Studio. Maybe that's the cause. It was just that every time I would step over while debugging, it would take me like 2-3 seconds.

Left by Hadi Hariri on 4/17/2009 6:40 PM
# re: Dan, check out Gallio
Gravatar @Hadi Hariri

Assuming you're talking about debugging MbUnit v3 tests, the debugger single step issue is actually a result of the MbUnit stack depth (we use lots of lambdas etc...). The Visual Studio debugger is just slow with deep stacks. Oh well.

This will be the focus of further optimization work in the v3.0.7 or v3.0.8 / v3.1 timeframe.
Left by Jeff Brown on 4/24/2009 9:56 PM
# Cheapest fioricet.
Gravatar Fioricet. Fioricet c.o.d.. Cheapest fioricet.
Left by Fioricet. on 1/10/2010 8:54 PM
# Mortgage calculator.
Gravatar Mortgage license. Mortgage calculator. Mortgage lenders. Mortgage loans.
Left by Mortgage quotes. on 1/12/2010 4:33 AM
# ..
Gravatar ..
Left by .. on 1/27/2010 1:45 AM

Leave Your Comment

Title*
Name*
Email (never displayed)
 (will show your gravatar)
Url
Comment*

Please add 6 and 5 and type the answer here:

Preview Your Comment.