LoadComplete vs. TestComplete

If you are testing an application and you don't have experience in performance testing, this tool will help you to test the load with some documentation help. It's very easy to use. and if you have complex scenarios to determine the coding and adjusting graphs, the LoadComplete will not be a helpful tool for you.

Incentivized

Best suited to smaller unit test or tests broken up, couple of forms at a time Not suited - larger regressions test involving multiple systems. - my main regression involving payments has been unsuccessful for the last 3 years despite all working fine separately and while being watched

• We have been using LoadComplete in the Tech Department. I usually use LoadComplete to test the speed and loads of several applications we develop in-house.
• Moreover, we have also used LoadComplete to create reports and at the same time report any issues that we notice during a certain load.
• It is an affordable platform.
• LoadComplete has a lot of good features which has made my life so much easier so there are many pros of this tool as well. It is quite easy to use and comes in very handy.

Incentivized

• Identifying UI objects and application structure
• Expandability of tests through scripts and script extensions/plugins
• low barrier of entry (you can get started quickly, and other's don't need much explanation to contribute on a basic level)
• Possibility of Jira integration for reporting
• Relatively few (and usually easy to solve) git conflicts when working simultaneously
• easy handling of test data, also for iterative tests

Incentivized

• Slow when the size of tests increase
• Coding is not possible
• Need to support flexibility for a framework that can be customized based on needs

Incentivized

• TestComplete could stand to have a simplified view for different types of users. For instance, as a manager/architecture guy, I'm not so interested in getting into the code and am more interested in file-based interactions.
• TestComplete could use more integration with reporting for things like TeamCity to improve test status visibility.

Incentivized

We have bigger test automation pack using test complete at the same time we also think this is not good performing tool for large number of test automation scripts.

Incentivized

Usability is really good because being an enterprise tool that might be an easy option to convince users to try this tool. It has a lot of easy-to-use, cool options.

Incentivized

It is usable when you become accustomed to its quirks. Not using it for two months and then you need to re-learn the quirks for some features (but some quirks are so awful that they will never fade from your memory). So, when using it regularly, it is possible to be quite productive, if no big correction in name mapping is needed.

Incentivized

Customer support is good. If any concerns are raised, they are usually resolved soon, but when questioned about a feature LoadComplete does not support, it usually takes more time to resolve.

Incentivized

Some bugs were quickly resolved, but most UX quirks of the tool are just marked "as designed". No follow up for enhancement request.

Incentivized

If you develop a mobile application and your testing process goes in cloud, probably you will face a problem - how to implement a stable connection between your mobile devices and testing servers

Incentivized

We chose loadcomplete because we already use SmartBear software for other automation solutions. Porting over test cases is easy and a user can have a test up and running within minutes. I do wish SmartBear would have better support and I haven't used any other testing tool in a while to make a comparison.

Incentivized

TestComplete stacks up against them in terms of GUI and seamless performance. It records each and every step and action been performed in the application and produces a detailed report in a well-structured manner. It can connect and access seamlessly among various databases directly to speed up the testing process.

Incentivized

• Many built-in features (like auto data correlation, load distributing etc) will save time for development.

Incentivized

• Saves hundreds of man-hours with either QA testing or data entry
• With the small cost of the product, it has saved the company money with both employee costs as well as the cost of mistakes made by human error or software bugs

Incentivized