Clik here to view.
Coded UI Tests (CUIT) With Multiple UIMaps Using A Container
When using Coded UI Tests (CUIT) to test large applications, it’s recommended to create individual UIMaps for each screen. I used the following container to configure multiple UIMaps to point to the...
View ArticleClik here to view.
Always Run Visual Studio As Administrator
When ever you have admin rights to your computer, be sure to run Visual Studio as Administrator. This will greatly reduce the number of headaches cause by tools who don’t react the way you expect them...
View ArticleClik here to view.
Building Maintainable Coded UI Tests (CUIT)
The following example, will be using Coded UI Tests (CUIT) and Visual Studio 2012 Premium to test the login window for a small WPF application. The Login Test Application is quite simple and composed...
View ArticleClik here to view.
Test For Positives
When you build your test plans, it’s quite important to keep in mind that testing for positives is always easier to maintain. Furthermore, by testing for positives, you are effectively testing and...
View ArticleClik here to view.
Adding A UI Control To A UIMap Without Adding A UI Action
Whether you are working with one or many UIMaps the best way to add a UI Control to a UI Control Map , without adding a UI Action, is to right click on the UIMap to which you want to add the control...
View ArticleClik here to view.
Building Data-Driven Coded UI Tests (CUIT) Using A CSV File
Data-Driven Coded UI Tests are great at testing screens with data permutations. In this example I am using data stored in a CSV file as a Data Source. The application under test is a simple WPF login...
View ArticleClik here to view.
Getting Detailed Test Results From Coded UI Tests (CUIT)
Coded UI Tests can fail for a number of reasons, producing detailed logs that can be used to rapidly identify what caused the failure. The interesting characteristic about the logs produced by the...
View Article
