TestComplete Feature Requests

Please add QT 6 support.    Our company has been using TestComplete for a decade for testing our QT application.  We have been updating QT along the way and now need to to update QT 6 so we need to TestComplete to also update their support.  We have thousands of man hours of work into our scripts at this point and having to switch to a different software would be a painful experience and would take likely years to get us back to where we are now. QT is a major player in Desktop Testing so I don't think they are going away anytime soon. ... View more

It would be nice to be able to enable line numbers when editing a keyword tests. ... View more

Currently, test logs can be saved/exported as unpacked storage or as .mht file.   I prefer to have it as one file (so mht is preffered), however only IE is capable of showing .mht files. MHT format it's a bit of an obsolete file format.   The request is to implement an alternative format that is similar to MHT however more supported by different browsers. ... View more

Currently we have to do a mapping from scratch if a name in the application changes.  Search and replace would save a lot of time. ... View more

The warning "An object recognition hint. See Additional Information for details." is always displayed, when an object is used and not found.   When testing if an object exists, the warning is not needed. Not finding the object in that case is not necessary a problem. Not generating warning when testing the Exists property, would also make "legitimate" object recognition hints easier to find and fix.   At least, it would be convenient, to have an option to turn it off at the project level.   ... View more

We are dealing with many different executables, which are interacting with each other in our tests. What we would like is to do is to have distinct responsible persons to maintain the NameMapping and the tests for each of the individual applications. In the "main" test project, we like to reference the "subprojects" and plug them together to obtain the integration test suite. This is working fine for script files (where you can add a reference to an "external" file, which is part of another project). But this does not work for the NameMapping file. It is only possible to have one monolithic NameMapping file in the main project. The only way at the moment is to "merge" all the NameMappings of the subprojects to the main project's NameMapping, which is error prone and cumbersome. It would be great if the NameMapping of the main project could somehow "include" or "reference" other NameMapping files from other projects, which are part of the project suite. ... View more

Viewing a Python script inside TC vs the IDLE code editor is like night and day. It makes it easier to follow. ... View more

Hi, Jenkins and Test Complete Integration produces just 'Junit Style Reports' but not the actual 'Junit report'.  Since this is not an actual 'Junit Report', this format is not being accepted while posting the report in our system.   Here are the examples of Junit Style Report and actual Junit Report   Junit Style Report- Result from Jenkins-TestComplete integration: <?xml version='1.0' encoding='UTF-8'?> <result plugin="junit@1.20"> <suites> <suite> <file>C:\Jenkins\jobs\Test\builds\51\tcreports\8023278.xml</file> <name>ETR</name> <duration>47.851</duration> <timestamp>2017-08-01T06:33:49.972-04:00</timestamp> <time>47.85100173950195</time> <cases> <case> <duration>47.851</duration> <className>ETR.ETR</className> <testName>ProjectTestItem1</testName> <skipped>false</skipped> <failedSince>0</failedSince> </case> </cases> </suite> </suites> <duration>47.851</duration> <keepLongStdio>true</keepLongStdio> </result>   Actual Junit report: <?xml version="1.0" encoding="UTF-8" ?> <testsuites id="20140612_170519" name="New_configuration (14/06/12 17:05:19)" tests="225" failures="1262" time="0.001"> <testsuite id="codereview.cobol.analysisProvider" name="COBOL Code Review" tests="45" failures="17" time="0.001"> <testcase id="codereview.cobol.rules.ProgramIdRule" name="Use a program name that matches the source file name" time="0.001"> <failure message="PROGRAM.cbl:2 Use a program name that matches the source file name" type="WARNING"> WARNING: Use a program name that matches the source file name Category: COBOL Code Review – Naming Conventions File: /project/PROGRAM.cbl Line: 2 </failure> </testcase> </testsuite> </testsuites> ... View more

Hi Team,   I would like to propose new idea on creating an ability to generate test report summary in xUnit format along with the current supporting formats mht, xml and html. It would be helpful to publish the report in xUnit format to any dashboards if the team have their one.   Thanks, Karthik K R ... View more