TestComplete Feature Requests

It would useful to be able to define clean-up steps/post-conditions for keyword tests. This could be implemented as a new test step section at the bottom that always gets called regardless of whether the main test failed or not. The test would still be reported as having failed in the test results, but before moving onto the next test it calls the clean up steps.   I know that you could implement this as a separate test that gets called after the main test in the test project, but that's a pain if multiple tests have the same clean-up steps. Having explicit clean-up steps makes it easier to understand what the test does just by looking at it, and how it might affect the rest system and subsequent tests if it fails early.   I tried using the Try ... Finally keyword test steps but the Finally step isn't called when an error-level message is logged. Maybe we need to be able to raise exceptions from keyword tests instead of using Log Error Message, so the Finally step is still called. ... View more

Currently, test case value is visible from UI part, but the same identification from the script would be great. For example, it is available to get Enabled, Description, Timeout, etc https://support.smartbear.com/testcomplete/docs/reference/project-objects/project-suite/testitem/properties.html   So, I want to request feature to get value using script if test item is marked as "test case" or not   About test case column from UI part https://support.smartbear.com/testcomplete/docs/working-with/managing-projects/test-items.html   Thanks, Kristina ... View more

If this feature is available, I do not know how to do it.  It would very helpful to be able to enter multi-line text content into the Description column of the keyword test editor.  Our convention for documentation is to write something meaningful to a human operator of the software application being tested for each step such that a manual test can be performed to mimmick the keyword test.  The problem is, there is no wrap-around on this column, nor is there an ability to enter a carriage return directly into the editor.  We have a workaround, which is to write the text into Notepad (with carriage returns) and cut and paste from Notepad into the Description cell.  This is very cumbersome at best.   As far as I can tell, the Description column appears to be the place to do line-by-line comments (we prefer to use the Comment line in keyword tests for higher-level documentation).  We like the line-by-line commenting because we have a in-house program that will pull out the Description content from keyword tests and write them to a text file, thus giving us a manual test procedure for a diagnostician to run when we encounter bugs. ... View more

Hi, I read that there was a feature request about 2 years ago suggesting that when we add a new parameter to a keyword test updates all references to that keyword test to at least pass the default value of the parameter.   Is there a reason this feature is not being developed? We have a suite thats almost three years old and the more functionalities our application has the more we add optional parameters or make a separate keyword test to handle those new functionalities.   Making a separate keyword test still requires us to look for all references to the original keyword test and add the new complement keyword test.   Testcomplete does allow us to update all references to objects such as namemapping aliases so I'm just curious why this hasnt been done yet ... View more

if you create a folder in keywordtestlist it will be automatically named "New Folder 1, New Folder 2, ..." and you have to rightclick, choose rename to name it as you want - pls enhance the creation to normal behavior (like windows):  - create folder - default name is highlighted but not set - you can type new name (without reselecting!) ... View more

if you have a large list of networksuite jobs its very annoying to scroll trough the whole list of tests manually - it would be nice to have a selection window like it exists for the project suite test items. ... View more

We develop WPF applications for Desktop with touch screen. TC provides only mouse events of controls. Touch events and mouse events are entirely different beasts. They are not interchangeable. Testing of drag, flick, pinch, press+drag, rotate... (multi touch) are not possible to test with TestComplete. But this is neccessary. ... View more

when you change the name of a keywordtest it asks you if it should change the name in other keywordtests too. this works so far BUT the changes aren´t apply for used keywordtests in your networksuite jobs list.  ... View more