Eclipse is a free and open source integrated development environment (IDE).
N/A
TestComplete
Score 7.0 out of 10
N/A
TestComplete is a GUI test automation tool that enables users of all skill levels to test the UI of every desktop, web, and mobile application. TestComplete is best suited for testers, automation engineers, and QA teams in any industry.
$2,256
per license
Pricing
Eclipse
TestComplete
Editions & Modules
No answers on this topic
Node-Locked Base
2,256
per license
Node-Locked Pro
3,950
per license
Float - Base
5,077
per license
Float - Pro
7,901
per license
Offerings
Pricing Offerings
Eclipse
TestComplete
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Pay for only the modules needed. TestComplete Pro includes all three modules: desktop, web, and mobile, at a bundled price point, as well as access to the parallel testing engine, TestExecute.
TestComplete has additional add-ons, including TestExecute and the Intelligent Quality Add-On.
Below are the points why we selected TestComplete 1. Better UI. 2. Plenty of validation cases supports i.e. checkpoints. 3. Multiple scripting languages. 4. Better accuracy and robustness. 5. Good documentation and Video tutorials. 6. Great support team.
We also evaluated Rational Functional Tester and QuickTest Pro. These other tools were a little more difficult to implement and very costly. They were not as flexible as TestComplete. The sales staff around TestComplete was friendlier and more responsive. They made us feel …
I think that if someone asked me for an IDE for Java programming, I would definitely recommend Eclipse as is one of the most complete solutions for this language out there. If the main programming language of that person is not Java, I don't think Eclipse would suit his needs[.]
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
While the DB integration is broad (many connectors) it isn't particularly deep. So if you need to do serious DB work on (for example) SQL Server, it is sometimes necessary to go directly to the SQL Server Studio. But for general access and manipulation, it is ok.
The syntax formatting is sometimes painful to set up and doesn't always support things well. For example, it doesn't effectively support SCSS.
Using it for remote debugging in a VM works pretty well, but it is difficult to set up and there is no documentation I could find to really explain how to do it. When remote debugging, the editor does not necessarily integrate the remote context. So, for example, things like Pylint don't always find the libraries in the VM and display spurious errors.
The debugging console is not the default, and my choice is never remembered, so every time I restart my program, it's a dialog and several clicks to get it back. The debugging console has the same contextual problems with remote debugging that the editor does.
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.
I love this product, what makes it one of the best tool out in the market is its ability to function with a wide range of languages. The online community support is superb, so you are never stuck on an issue. The customization is endless, you can keep adding plugins or jars for more functionalities as per your requirements. It's Free !!!
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.
It has everything that the developer needs to do the job. Few things that I have used in my day-to-day development 1. Console output. 2. Software flash functionality supporting multiple JTAG vendors like J-LINK. 3. Debugging capabilities like having a breakpoint, looking at the assembly, looking at the memory etc. this also applies to Embedded boards. 4. Plug-in like CMake, Doxygen and PlantUML are available.
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.
I gave this rating because Eclipse is an open-source free IDE therefore no support system is available as far as I know. I have to go through other sources to solve my problem which is very tough and annoying. So if you are using Eclipse then you are on your own, as a student, it is not a big issue for me but for developers it is a need.
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
The installation, adaptability, and ease of usage for Eclipse are pretty high and simple compared to some of the other products. Also, the fact that it is almost a plug and play once the connections are established and once a new user gets the hang of the system comes pretty handy.
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.
This development environment offers the possibility of improving the productivity time of work teams by supporting the integration of large architectures.
It drives constant change and evolution in work teams thanks to its constant versioning.
It works well enough to develop continuous server client integrations, based on solid or any other programming principle.
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
