Today Microsoft announced the world’s first and only automation testing tool for Windows, and in this post I share some of the reasons why I think the tools are necessary.
Automation testing tools are about automating some mundane or repetitive task to allow developers to verify that their code works as expected. There are two types of automation tools: full-blown testing tools, which automate the process of testing code, and half-baked tools, which only do an automated test once and then leave it open to review by a human.
The half-baked tools are pretty much what I’ve been doing for the past five years. I’ve been using them to check our code for obvious bugs (like the ones that occur only when you don’t test). I’ve also been using them to write automated tests for our game engine and a few other things. And then I’ve been using them for testing our web service.
Microsoft’s new test tools aim to simplify the process of writing automated tests, but not just for code. The tools can be used in a variety of situations including web content, system administration and even testing web APIs. The new tool suite includes tools for unit testing, integration testing, performance testing, and stress testing.
The test suite should be able to run on real hardware, and run well on modern browsers. And as this test suite has a lot of it built into it, it’s hard to find a better one.
The new test suite is built on Cucumber, which is a framework that allows you to write functional tests using a common language. It’s a great framework for writing automated tests, but it’s more geared towards code-level testing than the more developer-focussed testing that the new tools are.
Cucumber is a great framework, but it’s used in a way that’s too developer-focused. Its a framework that’s used to write “functional” tests, whereas the new tools we’re testing are designed to be more developer-focused, and should provide the kind of real-time feedback you would expect from a Cucumber test.
Cucumber and the new test-driven development tools are both great, but the developer-focused nature of the new tools means that they will be a little more difficult to use in situations where it isnt easy to write tests at all or have them be as good as the way you would expect. This is probably the main reason why the new tools are so much more difficult to use for developers than the other tools.
With the new test-driven development tools, you can have a lot more control over the test results, because you can have more control over the test results if you test them against the results from the previous test. What happens when you test against the results from the previous test? When you test against the results from the second test? It’s a much more difficult question, but that’s what happens when you test against the results of the first test.
We can’t wait to see the new build of the tool we use to control the tests. It is the only one of the tools we’ve found so far that actually controls the test results.