Desperate! Run All Unit Tests After Build no VSMDI?

[SnapDive]

I have a Visual Studio 2008 solution. There are 5 unit test classes
each with multiple tests. Each test .dll is named like "Test....dll"
in the name. A TFS 2008 instance is automatically building everything
and dropping it where it should go. The tests are GDR database unit
tests and classic tests that touch a web application project (not a
web site).

I would now like to add something that will let me say "run every test
in every binary that matches the name pattern test*.dll."

I do not want to use a vsmdi file or .testconfig file, they are messy
in my multiple-developer (and multiple time zone) environment.

I cannot find anything simple that applies to Visual Studio / TFS
2008.

Help! Please!

[Gregory A. Beamer]

Post by SnapDive
I have a Visual Studio 2008 solution. There are 5 unit test classes
each with multiple tests. Each test .dll is named like "Test....dll"
in the name. A TFS 2008 instance is automatically building everything
and dropping it where it should go. The tests are GDR database unit
tests and classic tests that touch a web application project (not a
web site).
I would now like to add something that will let me say "run every test
in every binary that matches the name pattern test*.dll."
I do not want to use a vsmdi file or .testconfig file, they are messy
in my multiple-developer (and multiple time zone) environment.
I cannot find anything simple that applies to Visual Studio / TFS
2008.
Help! Please!

My fave, for automated builds, is Cruise Control .NET. There is a TFS plug-
in for automating builds with CC.NET and TFS:
http://www.codeplex.com/TFSCCNetPlugin

From here, you can script in the tests in a variety of ways. MSBuild if you
want to work through the VS project files. This can be set up with MSTest,
as well. nAnt is another popular option, and there is tooling support for
this open source project (also open source).

As far as just running any assembly with tests, there is no baked in
goodness I know of. You can create your own "test runner" of sorts and fire
off the tests. I find it easier to script them out and put into the build
process (nAnt or MSBuild method).

Hope this helps.

Peace and Grace,
Greg
--
Vote for Miranda's Christmas Story
http://tinyurl.com/mirandabelieve

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************

[SnapDive]

Thanks for the response. I'm still working through this.