Coded UI Tests are a specific type of UI testing introduced with Visual Studio 2010. You can create your first Coded UI test following simple instruction from MSDN documentation. Most of the introductory examples shows you how you can use the Recorder tools to record interaction with a software (Web, WinForm, Wpf. etc) to generate […]

Continue reading about Programmatically use of Coded UI in Visual Studio

Code UI Test are an effective way to test your UI through automation, they absolutely are not a substitution for Unit Testing, but they can be used effectively to verify the whole application behave as expected. The most annoying part of Coded UI Test is that while they are running you cannot do anything else […]

Continue reading about Is it possible to run Coded Ui Test in a Virtual Machine instead that in my primary machine?

A common question about TFS 2012 build is: how can I ask for code coverage? The answer is really simple, you should go to the test section of build definition and change the run settings from Default to another setting that includes code coverage and this is really everything you need to do. Figure 1: […]

Continue reading about Code coverage during TFS 2012 build

I’ve dealt in a previous post with the new Shim library in Vs11 that permits you to test “difficult to test code” and I showed a really simple example on how to use Shim to isolate the call to DateTime.Now to simulate passing time in a Unit Test. Now I want to change a little […]

Continue reading about Shim and InstanceBehavior fallthrough to isolate part of the SUT

I always strive myself to write testable code, but it is not always easy, especially if you do not follow TDD red-green-refactor mantra. Code written without Unit Testing in mind is usually not so easy to test and when is time to modify code written by other, if you want to create a safety net […]

Continue reading about Using Shims in Visual Studio 11 to test untestable code.