Will TestAPI be supported after VS 2010 release?

Apr 27, 2010 at 6:30 AM
Edited Apr 27, 2010 at 6:30 AM


short introduction, for the start: we use TestAPI for about a year and we've built quite a lot around it and it suites our needs so far.

I've had a look at the VS 2010's CodedUITest feature and it looks suspiciously close  to TestAPI (and has more helpful methods like WaitForSomething() and so on).

So, the question is - are you going to support TestAPI further (and that would be great) or "CodedUITest will take the place"?


Apr 27, 2010 at 4:18 PM
Edited Apr 28, 2010 at 5:45 AM

Hello NLord,

It's great to hear that you guys are using TestApi and that it suits your needs so far. Obviously, we'd love to hear your feedback, suggested areas for improvements and feature additions, etc.

VS 2010's CodedUITest does have some features that are close to what TestApi is providing. VS 11 will probably have even more of the features provided by TestApi. With VS, we strive to provide a full-featured integrated environment so we will pick up and expose the best of TestApi and more in it.

We will, however, continue to support TestApi as a standalone library too.  While we love VS (it's our product), we are also big believers in lightweight, standalone solutions, such as TestApi, esp. because they let us get value out to you guys faster and because they let us solicit feedback from you on what works and what doesn't. As a matter of fact, the VS CodedUITest dev manager recently blogged about using TestApi from within VS (see http://blogs.msdn.com/gautamg/archive/2010/04/08/how-to-do-image-comparison-in-coded-ui-test.aspx).

So, we will have TestApi as the lean standalone library that can be used form within any environment and we will have VS as the richer, deeper, fully integrated solution and of course one would be able to use future versions of TestApi from within VS. We will ensure synergy between the standalone TestApi and VS -- both will continue to be supported.

Hope that answers your question: