Geeks With Blogs


Subscribe in NewsGator Online

Thawte WOT Notary
Serving Southern Indiana

Eric Hammersley <insert impressive list of technology to blog about here>

One of the first places I went was unit testing.  I really like what Microsoft has done by pushing the unit testing framework into the IDE and providing the tightly coupled code coverage tools along with it.  This is probably my top “most-used” feature of the new Visual Studio 2005 product.

First off the namespace of the UnitTesting framework has been changed in RC1 so any testing you’ve written in Beta 2 or earlier will not compile.  They have also changed the stub and methods for setup and teardown of your test methods.  I did not test if the previous Initialize() or TearDown() worked as before, I just adopted their new way of doing it.  This isn’t a big deal but like I’ve said many times beforeit’s beta code, deal with it.  Although I didn’t notice any changes with their PrivateAccessor generator I went ahead and regenerated my Accessors and Test stubs under their new format.  No big deal.

The next thing I noticed is that it didn’t recognize my old test metadata file.  This is the file that provides you with all the handy test grouping in Test Manager.  The new bits created a new test metadata file for me.  I initially shrieked but quickly realized I could just import my old file, delete it from source control and upload my new file.  Problem solved and no metadata lost.  There’s a toolbar button in Test Manager for importing your old file.

Next is speed.  WOW, what an improvement.  Just as an example I have a project with around 500 or so tests.  Not a lot but enough that in Beta 2 it took almost 3 and a half minutes to complete a full test run with instrumentation.  Now my 500 tests run in a lightning 30 seconds with full instrumentation.  Not bad at all!

Finally, code coverage color highlighting in your code and your sanity.  Your code used be to highlighted with a decisive green for covered, blue for partial and red for not covered.  A color scheme that made sense to me.  Now… the default is baby blue for covered (?!?), an almost peach for partial and a sickly red for not covered.  I have no idea where this scheme came from.  I will say one thing though.  The previous defaults of green, blue and red were harsh to look at for extended periods of time where as the new colors are very soft and pleasing.  You can however change the colors very easily in Tool…Options under settings for the Text Editor.  I’m not complaining about the new colors except I got used to the old ones and when I saw all my code go blue I thought I was in trouble.

On a final note remember if you are developing with a Beta 2 Go-Live license this version is not for you as it is not covered under the Go-Live license terms.  I don’t know why I feel the need to say that every time but somehow it seems important to me.

Posted on Tuesday, September 13, 2005 3:00 PM Visual Studio 2005 | Back to top

Comments on this post: Initial Observations - Visual Studio 2005 Team Suite RC1

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Eric Hammersley | Powered by: