In an upcoming project I could be using TestComplete Desktop for test automation. Having never used TestComplete before, now is a good time to familiarize myself with its functionalities. Within the posts of getting to know: TestComplete Desktop I will be sharing my experiences with TestComplete Desktop and the process of gaining them.
Like an automation diary.
Note of integrity: I am in no way affiliated with or sponsored by SmartBear or its subsidiaries. These are my personal experiences with the software.
system under test
The system under test is a WPF client that communicates with a server. As I currently don’t have access to the software, I will create a small sample application. This application will contain:
- 2 forms to automate workflows across different forms,
- some input controls to automate input,
- a combo box and a data grid as those tend to be more difficult to automate,
- a database to inspect the possibilities of test data management,
- and a service for external dependencies.
Another advantage of a self-written sample application will be the possibility to change names and ids of controls which will give me an idea of the automation’s stability.
SmartBear TestComplete Desktop
SmartBear’s description of TestComplete Desktop states that
- you can “create reliable functional UI tests for any desktop app”,
- you can “Data-drive […] these GUI tests to test thousands of combinations.”, and
- an “Intelligent object recognition mechanism ensures your tests are robust and easy-to-maintain.”
Although those are just marketing buzz phrases, TestComplete Desktop seems to provide all the prevalent features one would expect to find in an efficient test automation tool. After having read the creating your first test tutorial, I think that TestComplete Desktop can be used to record tests and edit them inside a structured IDE or with a popular programming language. Just like Ranorex or Coded UI.
Luckily, SmartBear provides a 30 day trial version of TestComplete Desktop. So that’s what I’ll be using for my evaluation.
a not so USP
It seems to me that every company thinks of its automation tool’s object recognition as a unique selling point: “Unlike other automated testing tools that work at image or coordinate level, automated desktop tests recorded using TestComplete Desktop work at object-level.” All the tools I’ve used for windows test automation so far have had this feature. In fact, I think that with UIAutomation, there is no need for image or coordinate based automation on windows!
For the next post, my goal is to show the sample application as well as the first test(s) automated with TestComplete Desktop.
TestComplete, TestComplete Desktop, picture of SmartBear HQ © SmartBear Software