TestComplete Feature Requests

It would be nice to add a custom message to property checkpoints within a keyword test.  This would be especially helpful when checking the objects or fields of primary object b/c in this case no screenshot is captured.            ... View more

Hello!   Whenever an alias is changed in a project's NameMapping file, TestComplete will offer to automatically correct any items in Keyword Tests that use the alias. However, I have found that this feature only works with Test Actions (On-Screen Action, If Object, etc.) and Checkpoints (Property Checkpoint, Region Checkpoint, etc.)   Currently, Logging items (Log, Post Screenshot, etc.) and Statements (While Loop, If... Then, Set Variable Value, etc.) do not get updated automatically with this feature. Having this functionality would help greatly reduce errors that result from partial renaming jobs. ... View more

When validating forms fields labels, and help text (properties ContentText values), the "Properties Checkpoint" is ideal. However, it waits for the Auto-wait timeout when it fails validation. In a large project, for example only 10 errors exist and each have to wait for the global default of 10 seconds, it would be 100 second additional run time where in automation time is of an essence.   Ideally the "Properties Checkpoint" should be performed in tow steps: 1. access the object including wait for the time out 2. compare the property value do not wait for the time out   Current options: 1. Change the global default time out of 10 seconds to a very low number, and that is not a good idea and still does not go as fast as should be 2. Override individual "Properties Checkpoint" to set a very low value, is difficult to maintain with constant edits, and still does not go as fast as should be 3. Use the "If Object" or "If Then" with "Log Message" it becomes 4 statements rather than the single "Properties Checkpoint", and still the time out applies ... View more

It would be very useful to have a feature where the test logs can be automatically generated to PDF files.   Essentially, rather than manually generate a PDF report as an export as instructed in Test Complete documentation: https://support.smartbear.com/testcomplete/docs/testing-with/log/working-with/exporting/index.html#pdf have the PDF report generate with a simple "writeLogToPDF" command.   Thanks for your consideration!   ... View more

In the checkpoint wizard, after you've selected an object, you advance to the "Select data to check" screen, which then includes a table of one or more "suggested" properties to check.   There should be a way for a user to set default properties, such as height, width, etc, based on their testing preferences. ... View more

Can you pelase add one more argument for the method 'Region.Compare()' which is to pass a 'ColorTolerance' value? Region.Check() is having that but that logs the error which I don't want to happen in certain scenarios. https://support. smartbear .com/testcomplete/docs/reference/project-objects/items/stores/regions/compare.html   Without having this ability, I have problem making use of the new feature 'rerun' tests when failed. ... View more

Excel Checkpoints: It should be possible to pass the file path as a paramer similar to File Checkpoints. ... View more

Can you please support CSV files in a similar manner to Excel files for a Checkpoint? ... View more

Allow CTRL select to select multiple values in OCR Checkpoint Recognized Text. As it functions now, can only either select specific values or groups of consecutive values. Would like to be able to select multiple values that aren't consecutive. ... View more

In a new versions of Testcomplete is disappeared the ability to select JScript language in project. But for several year has a problem that prevents our team from switching to JavaScript ES6. When test run has repeated Property checkpoints, each other assertion consumes more and more time to finish. It reproduces only in KeyWord tests, runned in JavaScript ES6 project with OnStartTest event is activated. In the attachment you can find an archive that will help you reproduce the problem. Execution of KeyWord test for a JScript ES3 project takes 53 seconds. For a JavaScript ES6 project, the same test takes more than two minutes to execute. There is a huge problem for a big projects. We created support Case #00415520 couple years ago, but this problem does not fixed yet in the newest versions. Perhaps the vote as feature request will push SmartBear to solve such a serious problem. ... View more