It allows us to test both desktop and web applications. This is a very important feature for system integration tests, as we develop desktop applications, web applications, and a Web API using the same database.
It is very hard to read the test log generated by TestComplete Executor if the log file is very big. TestComplete Executor is a small tool for just running the TestComplete test framework (not for developing).
In fact, this is an issue regarding how to read the test log in MHT format generated by TestComplete.
We know a test log is always generated automatically by test tool after executing a test. TestComplete provides a standard IDE (Integrated Development Environment) interface for user to review the test log. We don’t have issue reviewing the test log within TestComplete regardless how big the test log is (Our test log record the test running for more than two days without stopping. The test log extension name is .tcLogs and the size of total test log is very big over 2.5 GB).
TestComplete also provides a function for the user to export the log into MHT format file via manually selecting each test log after complete a test or dynamically exporting the test log during test executing via command in test script. The MHT log file can be opened by IE. However, if the MHT file is a little big, such as >200M, the user could experience obvious performance issues. It takes a very long time for IE to open this file because IE loads all the contents into one page which could finally eat up all your system memory. I tried to find another tool to open the big MHT log file, but no luck. Even executing a small test (running for one to two hours), the MHT log file size can easily reach to 200M, if a screenshot is included, for example. Normally, each one round of our regression test runs for 30-48 hours. It is impossible for us to open the big MHT log file as the system runs out of memory and an error appears definitely after hours of waiting to just open this file by IE.
TestExecute is a small tool to just execute the test developed by TestComplete. But TestExecute only generates MHT log file rather than TCLOGS file. Obviously, we cannot open the MHT log file if it is very big. So we gave up using TestExectue and export MHT log file function in TestCompelete at all.
We have to buy six individual full license of TestComplete to run and review the test.
We have used this for nine years.
Overall, TestComplete is quite stable. But the only issue affecting me is if TestComplete is terminated unexpectedly while test is still running (such as, terminating TestComplete without stopping the test first, window restarting, or shutting down unexpectedly), user could lose all the logs.
There were no issues with scalability, but it may have a performance issue with expansion.
Technical support is excellent.
The initial setup was straightforward.
The product is becoming more and more expensive. There are two types of licenses: locked and float. Locked license save more, but can only be used in a physical machine. Float licenses can be run in virtual machines.
QTP, was very expensive when compared to TestComplete, many years ago.
This tool is very easy to use and very powerful. It has a short test development circle and good technical support. There is an expensive license, but it could save more, as testers may spend more time achieving a certain test goal if using an Open Source tool. You need to consider the testers' script experience and the company’s budget to choose the right tool.
Test Complete provides detailed reports since every profit software should do, since people pay for its reporting functionality also. On the other hand, some big and expensive products stil has the reporting gaps, for example there are third party reporting tools for HP QC.