New Idea



As many code editors propose, it would be interesting to be able to use keyboard shortcuts to move a line or lines of code up (CTRL+SHIFT+UP) or down (CTRL+SHIFT+DOWN).


Thank you

Currently the "quick" way for me to map multiple actions is to create a record script or keyword test. However, it also will record the actions and 99% of the time i just delete the test.  

If i want to map an object from my website to testComplete, i have to click on the "Map Object from Screen" button.  This will then bring up a new window that allows me to decide how i want to select the object. I drag the target to the point to the object and have name mapping feature try to find the object.  I then can say "map the obj as _____"  or choose a name and properties manually.  Perform that step and rinse and repeat. over and over and over and over again until i mapp all the objects I want.  

I would find it useful to allow the user to map multiple objects and have them go through a list of objects that need mapping. If it runs into an object that is already mapped just skip or inform the user. 

The MDS file for a TestComplete project appears to store what tabs are currently open in the editor for the project.  So, if I have the NameMapping for the project open, a script file, and a keyword test, the specifics of what is open appears to get stored in the MDS for that project.  


The problem this presents is that if we are making changes on multiple workstations using a SCC, we are constantly needing to checkin and check out the MDS file as these changes alter the file.  These are not "code" changes that we want to preserve and yet we do still want to source control the MDS for project properties, project level variables, test items, etc.


I would be nice if those parts of the project that are not execution related (such as the open tabs) are kept in a separate file, perhaps user specific for shared workstations.

TestExecute Settings Customization

Status: New Idea
by DavidE on ‎03-19-2018 11:06 AM

There needs to be some way to easily customize the settings within TestExecute without having to login to every machine that has TestExecute installed on it and manually configuring it.


Either installation parameters, more execution parameters, or a human readable tcsettings.xml file that can be rewritten to configure the installation.  Something like this.  My company has 10 licenses for TestExecute, and our lab machines are very dynamic, meaning they get rebuilt often.  We are automating the setup/configuration of that environment, but this has become a limiting factor.


There are 3 key settings that I absolutely had to modify on each installation, and therefore we have opted currently to copy this XML file across all of our clients, but because the file is not human readable, I have no idea what other things are in there, and what might cause problems because I copied the file from another machine.


Also, I think it would be a good idea to have an option to make this configuration file be at the machine level rather than the user level.  While there may be a case for user specific settings, if that is not needed, managing these settings at a machine level rather than a user level would be far more efficient and less of a headache.

Context:  Project | Organize Tests  | Test Items


Today, the double-click action takes you to the "Select Test" form.


The idea of this post is for the double-click action to mean "Jump to Test" instead of "Select Test".


Why?: Once a test has been assigned to the test item, it rarely changes. When it does need to change, all you do is click on the elipses of the test name and it brings up the "Select Test" form. So, make the double-click do something more common, "Jump to Test".


A Variation of this idea is for us to be able to configure what action is taken upon double-click.



Overview: Would like to have both the TextExecute Runtime and Test Suite compiled into a single executable.


Use Case: We would like to have the ability to run the Test Suite without having to perform an installation of the software.  This would allow for greater mobility, requires less setup and less software to be deployed.  In our case it would extend the range of machines we can test against as we have some areas that would not like to have additional software installed.


Thank You

We need the ability to customize the template for posting a defect to QA Complete so we can do this from Test Complete and include logs.


If I do this from an automated test in QA Complete the logs and other information don't automatically populate in the defects.

Test Report summary export to Excel format

Status: New Idea
by abinash11 on ‎06-19-2017 08:22 AM

Currently, once the tests are executed in TestComplete, we can export the results and the summary into MHT format but not in Excel. Getting the results in Excel is a basic need in most projects where you have to report the results based on the number of tests run including the Passed and the Failed tests.


If not Excel, at least a CSV format should be good to start with.



I suggest that TestComplete supports Google Polymer framework.


Thanks in advance.

Status: Selected for Development



Since this framework is based on Shadow DOM, TestComplete will be able to work with it once this technology is supported. We have support for Shadow DOM on our roadmap for 2018. I will keep you updated on this.

Currently, the mouse "Drag" method drags from a starting co-ordinate a set X distance and Y distance from that starting co-ordinate.  For most "normal" drag functionalities, this is sufficient.  I even wrote some code with help from folks up here that, given a starting object and a destitination object, will drag from one to the other.


function dragCalculatedDistance(startObject, destinationObject) {
    var startPoint, targetPoint, dragX, dragY;
    // Drag from the center of object A to the center of object B

    startPoint = startObject.WindowToScreen(startObject.Width/2, startObject.Height/2);
    targetPoint = destinationObject.WindowToScreen(destinationObject.Width/2, destinationObject.Height/2);

    dragX = targetPoint.X - startPoint.X;
    dragY = targetPoint.Y - startPoint.Y;

    startObject.Drag(-1, -1, dragX, dragY); 

The problem is this...  We have a situation where we need to drag an object that is present below a table in our application to a particular cell in the table.  In that process, when we cross the lower border of the table, the table may auto-scroll down to reveal other rows.  Because the above function just drags to a calculated set of co-ordinates, the end result is that we end up dropping the object on the wrong row in the table.


Proposed Solution: A drag functionality for TestComplete where, instead of dragging based upon a co-ordinate distance, actually drag from one object to another... something like



where the two objects are identified onscreen objects.  This would resolve the auto-scroll because it would actually drag to the particular cell we want and not to just a set of on-screen co-ordinates.


Low priority change to make... and I'm open to other code that would make this work better for us.  But I think this would be "cool" as it would mean that my custom code above wouldn't be necessary any more and we could have "smart" drag-and-drop functionality.



It would be helpful if the master pc can recover from lost connection.


Currently I have a test which needs to lose the network connection as part of the test and then it establishes the network connection.


Once we lose the network connection the master pc is unable to receive the results from the slave pc.


Currently, we would have to run this test locally on the slave pc as a workaround.


Attached is the screen shot of what happens on the master pc

Modify Keyword Test Tooltip

Status: New Idea
by Moderator Moderator on ‎01-26-2018 11:28 AM

Current Behavior: Tooltip for keyword test parameters is implemented as a "Full Name Tooltip", this makes it so that the tooltip appears over the area highlighted.


Identified Issue: For some users, it is too difficult to click the parameter for editing because of the tooltip's placement. The tooltip is directly over the area to be typed into.




Desired Behavior: Change tooltip implementation from "Full Name Tooltip" to one of the other kinds of tooltips that offset the tooltip instead of displaying it directly on top.


Kinds of tool tips here:

We would like to be able to capture any logs from the console or network messages so that we can provide specific network errors to our developers for any intermittent bugs that may occur which are of this nature.

Currently, while we can open developer tools and access this via the object browser to get the elements which contain the log messages, we can't do this solely via an automated run in Test Complete. Is there a way we could get this information and if not could you add a feature for getting it?

Frequently, I run into problems where my find()/find_child()/find_child_ex()/etc.. calls are finding the wrong objects (sometimes its hard to find uniqueness within the objects you have at your disposal). It would be AMAZING to have a 'finder' tool directly in the object browser that would allow you to pick an object to perform a 'find()' call on, give a form to fill in props and values and it would give you the object (or objects) that it is matching against without having to run any of your own code.


It's good to know right off the bat if your props and values are mapping to the object you expect. I could see it saving me a whole lot of time when developing test scripts.

I have a ProjectSuite with multiple projects in which keyword-test-routines of one project are referenced in multiple other projects. If an original keyword-routine is renamed, there is no other way but to remove and then readd the references after which all usages of these references in actual tests have to be found and replaced with the renamed references as well - needless to say, that this is always a quite hideous task.


It would be very helpful if renaming a keyword/script would also rename all references and all places where they are used.

Personally, I hate the new feature in 12.30 "Smarter auto-formatting. When you type a bracket or a quotation mark, the Editor now automatically inserts the corresponding closing bracket or quotation mark."


Please see community post for more details:


I would love to have an option to shut this off.

I have over 700 test items grouped into groups and distributed across multiple test machines in a network suite, so the result log is long.

I know I can go directly to an error but it doesn't select the test item in the tree (another annoyance).

When I only have a few errors I have to step through the whole tree to find them.


It would be nice if there were a right click menu item in the tree to select the top level and collapse all nodes, or expand all nodes.  Then I could collapse the entire tree, do a couple of high level expansions, and easily see the failing group and test.

Our Windows application has this functionality courtesy of our DevEx tree controls.  Since TestComplete has a similar look and feel, I hope that it would be easy to add this to your existing right mouse button tree menu.



Consider a project with 100 tests which has a master project which run all the tests in this project on a remote VM.


    + Project01
    + Master
        + NetworkSuite
            + Job01
                + Task01 - Project01 (100 tests - 1-100) - VM01


I would like to add another task to Job01 to run half the tests on another VM.


+ Master
    + NetworkSuite
        + Job01
            + Task01 - Project01 (50 tests - 1-50) - VM01
            + Task02 - Project01 (50 tests - 51-100) - VM02


A test item can be specified in the command line as detailed in TestComplete Command Line (thanks @tristaanogre, @cunderw).

      /project:project_name /test:test_name


test_name can be a test item/group. But specifying a test item in the "Test" field in a network suite task is not working. I would like network suite tasks also to recognize test ietms/groups so that a project with a large number of tests can be run on multiple slaves.

Provide Ability to Clean Alias and Mapped Objects Not Used in Tests

Status: Selected for Development
by ‎06-17-2015 10:35 AM - edited ‎07-10-2015 11:59 AM

In our trial and error approach to learning TC we have found ourselves with excess baggage (unused mapped objects and Aliases) which we wish to clean up. At some point we disabled 'Map object names automatically' and have a mix of tests using Mapped and Aliased object.


The ability to removed mapped objects and aliases which are used in keyword and script tests would be highly benificial.


Here isa thread which discusses in further detail.


Thanks for your consideration.

For now I have to count the number of automated scripts within every folder manually. That's not convenience. If you add the number next to folder, that's good for user. The high-level design is like the enclosed picture.



Suggest Product Idea
We need your help! This is your space to provide suggestions for features or improvements for SmartBear products. Let us know what you think, or how we can help improve your experience with TestComplete.
Top Kudoed Authors