In last post, there was a little bit of grousing about Test Automation, need for approaching it strategically and side effects if Test Automation == GUI automation.
Also, there was another post talking about Quality practices for Agile teams..
My intend here to connect them and share how I would approach the Test Automation strategy for a .NET project using Visual Studio stack of tools
If I approach the entire Quality engineering with different perspectives that Janet Gregory & Lisa Crispin explained in their book, below diagram will be my goal
In that, Test Automation plays significant role in Quad 2 and hypothesis being a .NET team, VS ALM will help them to be up and running in no time. Beyond coverage on Test Automation, tight integration with other ALM capabilities are a great plus.
Additionally, on the Quad 4 tests such as Performance and Load testing, Visual Studio offers native support for local execution. Any of the tests written already can be reused. Also, Visual Studio Online offers support to execute load tests from the cloud.