TestComplete isn't quite complete (for WPF)
July 21, 2017
TestComplete isn't quite complete (for WPF)
Score 4 out of 10
Vetted Review
Verified User
Overall Satisfaction with TestComplete
The quality assurance department of Omnitracs Roadnet uses TestComplete to automate user interface testing of several of our applications, including a web application and a Windows presentation foundation (WPF) application. We primarily script automated tests to cover general "day in the life" use of our software, which saves time for manual test engineers during the regression testing period and can catch defects before manual testers find them.
- TestComplete allows access to the entire view model of WPF programs, which allows for complex tests to be scripted.
- TestComplete has a feature called Object Spy, which makes scripting of new tests fairly quick, as users can quickly see the names an attributes of applications elements simply by clicking on parts of the application user interface.
- TestComplete's text editor is extremely slow for debugging (especially for loading local variables, which can take minutes to load for every step in the debugging process).
- During our use of TestComplete, we found that it would regularly hang during test runs, requiring a manual restart of the test run.
- The version of JavaScript used by TestComplete is rather bare bones and could be much improved with features common in modern libraries.
- TestComplete seemed to have difficulty working with complex WPF programs as we found it necessary to script frequent breaks and refreshes into our automated tests in order to be sure that TestComplete had an accurate version of the view model.
- TestComplete saved time during the manual regression period of every quarterly release of our product by allowing test engineers to focus on new features.
- Debugging TestComplete related issues with our WPF application takes a great deal of time for our automation team and has had a negative impact on development of automated UI testing