TFS 2010 - Test Impact Analysis Series - Part 1

I love TFS / VS 2010 and the ALM features that it provides. One of the best investments of the 2010 product is in testing. The testing edition in Team System 2008 never really resonated with me, but the new testing features in 2010 rock!

One of the most exciting new test features is Test Impact Analysis. The idea of being able to take a new build from the dev team and have a good idea what tests have been impacted by their code changes is a great step forward in the Microsoft ALM story.

However (especially when testing web sites) it may not be as straight forward as it could be...

This short series of posts will highlight some issues and gotchas that I found using Test Impact Analysis (TIA) - incidentally most of these will also apply to IntelliTrace as it uses the same underlying profiling mechanism.

With luck you will read this before you hit the same hurdles...

And now onto Part 2

1 comment :

  1. Very nice post. I simply stumbled upon your blog and wished to mention that I have really loved surfing around your blog
    posts. In any case I'll be subscribing to your feed and I hope you write again soon!
    Practice test series