No more UI regressions
During the course of a Application Development Lifecycle, software goes through many iterations. Frequently, a change in one part of the software impacts another part and the developer remains blissfully unaware. Regression testing seeks to verify that existing functionality is not impacted by new changes. Automated Regression testing is a key tool for both the developer and the tester to ensure Product Quality.
Visual Studio Team System 2010 introduces a new test type – Coded UI Test, which enables you to create automated UI tests which can then be added to a regression test suite. Coded UI Tests may be run as part of a Build Verification Test suite, thus giving the developer immediate feedback on any UI regressions. The developer can run these UI Tests before his checkin and ensure that there are No more UI regressions.
A Coded UI Test can be created very easily with the tooling support provided in VSTS 2010. See links below for step by step guidance.
Generally initial phases in UI Testing is manual. Visual Studio Team System 2010 allows you to reuse the test artifacts created by manual tester. You can create a Coded UI Test from an action recording created by the manual tester.
Coded UI Tests may be created in either Visual Basic or C#. Multiple platforms can be tested with Coded UI Test. The platform support matrix is shown below.
Once a Coded UI Test is checked into source Control, you can easily add it into a Build Definition. The Build Definition below compiles a Coded UI Test Project and then runs its whenever a build is executed.
It is possible to associate a Coded UI Test to a Test Case. You can then run this test case from Microsoft Test & Lab Manager.
Coded UI Tests may be run from the command line also.
Summary:
Visual Studio Team System 2010 allows you to eliminate UI regressions by providing
- rich tooling and a powerful API for creating a Coded UI Tests.
- multiple easy modes of running Coded UI Tests.