TestComplete Feature Requests

TL;DR: I want to be able to set some setting somewhere that tells TestComplete to only use the "data-testid" (or any other) attribute to map objects.    What is a data-testid? We have the data-testid tag on every (important) element on our webpage. This testid is used to uniquely identify an object, meaning no other object on the webpage has this testid.   For example like this: <fro-input-wrapper data-testid="CONFIG.COMMON.systemName"> <mat-form-field> <wrapper> <input> </wrapper> </mat-form-field> </fro-input-wrapper>   This is obviously a very simplified version, but this is how every object looks like. So every button, every text-input, etc has this attribute.     What we currently do We map our objects using XPath, since it is so much faster at runtime to find the objects. So we have only one selector for every object, since we don't need more than that. So our XPath for finding the object shown before would look like that:  //fro-input-wrapper[contains(@data-testid, 'CONFIG.COMMON.systemName')]//input   The issue is, that when we use the TestComplete Object Spy and hover over the Object shown before, TestComplete searches out what it thinks is best suited for mapping the object. Which is totally random and does not conform to the way we want it (like shown above) The TestComplete Mapping looks something like that....     ... Which is just some random way to identify the object.    So currently what I created is a Template for every object type (inputfield, slide-toggle, button, ...) that we just copy paste and paste in the correct data-testid. This is the most elegant solution that we found and it works sort of well. But I cant think that we are the only ones using some form of testid on our object.  We are thinking about switching to Cypress, since it supports data-testid with a testing-libary, but the issue is that not everyone in our team is a coder and doesn't know how to code in JS.   What we want   A setting to define any attribute (in our case the data-testid) that TestComplete automatically uses to map the objects. I imagine it working something like that:   Using the Object Spy to hover over an object that I want to map TestComplete searches for the data-testid attribute If it doesn't find one in exactly the Object that has been selected, it searches upwards in the DOM tree until it finds an object containing that data-testid attribute. It uses to object to map the original Object that was hovered over.   I don't think that this would be too hard to implement and it would greatly improve our workflow.,   For any questions regarding the issue, please feel free to ask. ... View more

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

In large TestComplete project, it would be extremely handy to be able to Collapse/Expand (All and Group) in KeywordTests script. Same as implemented in Project Explorer, NameMapping, Script Editor, and Logs. ... View more

Hi,    The Find/Replace feature for keyword tests work only  in the Value column, is there a way to search through  NameMapping in Item Coulmn of the  Keyword ?   Regards ... View more

Hey, it would be great if the log would not display the whole screen from 3 monitors which are in use. Better would be that TestComplete checks where the tested application runs and just make screenshots for the log from this monitor - or implement an option to choose which monitor should be logged.   Attached is a screenshot from a log with 3 monitors. ... View more

Hi,   The request is to have the 'Execution Plan Editor' to work with Automation tests that has 'tags' on them.   Currently if the "Run @tag" option is selected, the tests will run in no apparent order, ie. the 'Execution Plan Editor' feature does not work along with it.   Hope that the feature request can have some priority, since it would definitely help a lot of Projects that utilize the Automation tests to run on CI/CD Pipeline.   Thank you in advance. ... View more

Make it possible to call keyword tests in the OnStopTestCase Event. In case of an error, we would like to bring our application into a state that is necessary for the next test case. For this we would like to use a keyword test, which unfortunately does not work in contrast to a script test.   function GeneralEvents_OnStopTestCase(Sender, StopTestCaseParams) {     if (StopTestCaseParams.Status == 2) //Error     {         KeywordTests.TryAbortSimulation.Run(); //Keyword test will be ignored!!!     } } ... View more

In some cases it is useful / necessary to run a batch script from Testcomplete. Unfortunately Testcomplete can't get back the status code from the batch file to get the information if the script was executed successful or not. In many cases it would be useful to get back the status code at the keyword level of Testcomplete, for example: - execute a program to do some taks as pre condition for the following teststeps - execute some testcases with a batch file that can't be executed by Testcomplete directly, like python testcases with the pytest framework   ... View more

The Click Action waits until the TestObj is visible before clicking on it. In most cases I only want to click on it when the TestObj is enabled. It would be nice if this behavior could be optionally enforced. Click Action ClickButton Action ... View more

- select some Keyword Tests - right click - choose "Run selected Tests"   ... View more

Hello all,   I would like to suggest adding a lint tool to the code editor with configurable rules.  In teams with multiple members code styles can sometimes be a source of contention.  It would be nice if a Team Lead could set a few rules in place within a project to allow for a more standardized code view.  Examples: single quotes verses double quotes, use of semicolons, curly brace placement, use of white space as well as others.    Thanks    ... View more

The screenshots in the Log files on the file directory would be much more useful outside of Test Complete if you could specify the filename when the screenshot is taken. Ideally, you would be able to specify the filenames always, but at least it should be an option to specify the filename of a screenshot when one uses the Post Screenshot Operation. ... View more

The following capabilities are missing in scripting for TestComplete: 1. Changing of namemapping should also update any references inside scripts not just KeywordTests         - What I do now is use an external text editor to look for references to Aliases.browser.pageX and change it to                     Aliaes.browser.pageY 2. Changing the name of a method/sub/function in a script or the script name should update all references used in KeywordTests         - Right now if you change a function's name the references done by Keyword tests still use the old name thus                       causing exceptions during runtime   ... View more

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

When you change a variable in KW tests I would like to see all occurrences of this changed   it would be nice if you could rename the var from within the KW test or where the variable has been created /stored   e.g.   record password script password called 'Password1' update var name to reflect ''webLoginPassword'    all occurrences of this var instance should be updated to reflect as other KW script names are already ... View more

its not possible to select multiple keyword-tests (from the project tree) and drag them into an opened keyword-test (workspace). might be a helpful feature ... ... View more

In all of text boxes in TestComplete using the keyboard combination Ctrl+Backspace adds a non-displayable unicode character. In windows the functionality of this key combination backspaces an entire word instead of just a single character. This functionality would increase productivity by both lowering the keystrokes needed, but also by being consistent with the rest operating system it runs in. ... 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

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