TrustRadius Insights for TestComplete are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
TestComplete is a versatile tool that is primarily used to automate GUI interfaces for web applications and standalone applications. Users have found it particularly helpful in organizing and running tests smoothly, increasing the efficiency of their testing processes. By automating repetitive tasks and allowing more time for exploratory testing, TestComplete has helped users identify previously unknown bugs in software. It is commonly used to automate regression tests of web-based products and in-house developed software that integrates with other applications. Additionally, TestComplete has proved valuable in the banking industry for testing web and mobile applications, custom modules, and CRM systems. It has also been utilized to automate tests for simulation software and to migrate manual test cases to an automated framework. Overall, TestComplete enables users to automate testing processes, save time and effort, and perform a higher number of tests in a shorter period of time.
We attempted to use test complete to perform functional and UI tests on our windows native as well as our swift and kotlin apps. In my experience, test complete failed miserably on functional tests incorporating the mobile apps cameras. On the native windows app written in c# test complete has been nothing short of a nightmare. We find ourselves troubleshooting it more than we do our app. You can run the same test twice in a row on a dedicated vm and get the test to pass one time and fail the other with no changes made to the app your testing.
Pros
cause frustration among the entire team
Cons
better support
fixing its issues related to headless testing
running in a uniform manner where the same test fails or passes arbitrarily
better mobile support
Likelihood to Recommend
In my opinion, dont waste your money smartbear has a lot of work to do with this product.
VU
Verified User
Engineer in Engineering (Computer Software company, 11-50 employees)
I used TestComplete for 2 of our products. 1. Ours is a read-only CAD tool, where we used the object mapping technique to create the test cases and it worked well for us except for a few of the exceptions where object mapping failed. 2. It is an add-on for the Creo Parametric, where we recognize the features of the object/CAD model.
Pros
Object Mapping is really good.
Validation of test cases (checkpoints) is user friendly and intuitive.
Support of different script languages such as python, VBSript, JavaScript, etc.
Help documentation is very detailed and clear.
Grouping of the Test Cases and in detail test reports.
Cons
Recording in the case where object mapping is not possible, coordinate recording needs a better approach. Sometimes coordinates are not getting clicked for the desired tab and other tab gets clicked when the test is rerun.
Likelihood to Recommend
TestComplete is best suited for applications where object mapping is captured perfectly. It can cover complex test cases in this case. Applications where object mapping fails. screen/window coordinates suit well, but with some limitations where proper tabs are not getting recognized when clicked and other tabs are clicked based on coordinates recorded.
TestComplete is used across our department. It is primarily used to automate GUI interfaces to our application product suite.
Pros
The organization of test suites and test projects is very intuitive. This made it easy to learn and fairly easy to manage. We had a conceptual framework for tests that TestComplete seems to support very well.
The blog web site for technical support is very responsive and the people supporting it know the product quite well. This has been essential in helping us to apply the product across a wide variety of testing needs.
TestComplete allows one to create very robust automated test procedures. When it comes to testing on a very large scale, the test procedures must themselves be bullet proof. There are quite a few tricks to learn to make this happen, but TestComplete allows us to do this.
Cons
The reporting features are poor to non-existent. We need to develop our own presentation formats for results and do not want to buy an add-on product (such as QA Complete) to do so. We have had to get creative and embed report meta data generating subroutines into our test procedures so that we can capture the data that we need. This is time consuming and inefficient.
There are a couple of files that are particularly vulnerable to corruption if you are not very careful with how you manage your source control. The name mapping file and individual project files can be corrupted easily when more than one person is making changes to those files. Merging capabilities with something like the Git version control tool can be tricky. Remember to back things up frequently and carefully!
TestComplete does not provide searching for internal relationships without writing special scripts to do so. For example, it would be nice to find out what TestComplete objects are affected by making a change to javascript function. Getting a list of keyword tests and lines affected would be great. Another example is changing the name of an object. In some cases TestComplete propagates the name changes to the affected related objects and in other cases it does not. How does one understand the impact of changing a shared object if these relationships are not readily at one's finger tips??
Likelihood to Recommend
We use TestComplete almost exclusively for GUI testing. It is capable of testing non-GUI applications as well, but we do not do that with TestComplete. TestComplete is not well-suited for testing the applications running on operating systems other than Windows.
[It's] Used in one department to automate testing of power management appliances we manufacture. [It's also used for] Automated testing of browser based control panels for products.
Pros
Basic scripted testing of login pages and basic web operation. Keyword / macro capability easy to program.
More involved functional tests with time period testing between events. Good for performance evaluation.
Cons
The key issues are that TestComplete often has problems running previously created scripts as a browser version update - identifying page objects is problematic.
TestComplete is used throughout our development cycle to run a series of regulated tests in place with FDA standards. I manage 400 automated tests that follow specific steps to validate proper functioning of routines within our software. I keep the tests organized by using grouping and keeping name mapping as detailed as possible so the tests are easily readable, can be searched through with ease for certain sections, and can be easily edited when a new feature needs to be tested. I use TestComplete daily and have multiple project suites for different software packages to help stay organized.
Pros
TestComplete would be easy to learn for a user with no programming experience. The keyword tests make recording and editing very easy.
The user can have direct control over how objects are mapped and how they are named. This is very helpful for organization.
The tree structures used for the tests in the projects, for name mapping, and even within the tests keep everything very organized and easily accessible.
Cons
TestComplete seems to have a hard time mapping smaller objects in my company's software. In the main window, there are some controls and buttons but TestComplete only sees the pane they are located in and not the actual buttons. To get around this I have to tell it to click at a certain location within the pane instead of telling it to click on a button. Mapping works perfectly for every other software I test in except the software developed in my company. It is easy to work around but I had to switch monitors recently and redo all of those locations because the resolution had changed. Also for certain popup windows it will default to a location within the window rather than click the OK button and I have to go back and tell it to insert an action for the button because it does not map the button at first. It would be nice if the name mapping were a little more particular.
Often when I record a new portion of a test or make other changes, the preview pane will revert to "default" height and I have to resize it so it big again and I can see what I am looking at. This is annoying, it would be nice if the preview pane always remembered its size.
Likelihood to Recommend
TestComplete would be an exceptionally useful tool, but it seems to have a hard time mapping our software. I do not think this is a problem with TestComplete but rather how our software is developed. TestComplete is still the best tool for us at this time.
VU
Verified User
Engineer in Engineering (Computer Software company, 11-50 employees)