TestComplete Feature Requests

Edit:  Added a specific Use Case for clarity   Like most users I use parameters for my KWTs.  Some parameters have a limited option pool e.g. paramater "WantACookie" can have 3 and only 3 values "Yes", "No" and "Not Sure"  This parameter is used to set the text of a combobox.  I could create it as a string that correlates with this and each other KWT or script that calls this KWT just needs to send the string.  Say, however the the marketing department decided that "Not Sure" is no longer broadcasting the right message and want to change it to "I'm Thinking About It"  All those other scripts and KWTs that used to set it to "Not Sure" will break.  Is it possible to create the parameter as a list of key->value pairs.  That way my other KWTs and scripts can say the vaule should be WantACookie.NotSure and all I have to do is go to my KWTs WantACookie paramter and change the value of the "NotSure" key to "I'm thinking About It"  You would probably have to define this KVP list in the parameter type itself I guess and when setting properties in the visual editor, this "Enum" should be available the same way Variables and Parameters are from a dropdown.   A specific Use Case:   The Enum is a way to define a limited amount of set options that you know won't change Say I'm an e-commerce site.  I wan't to make sure users don't have a bad experience by accidentally buying something when they intended to just add it to the wish list.  Three tests:   1. Textbox1.Keys()->Textbox2.Keys(),texbox3.Keys,etc,-> buttonPlaceOrder.Click() -> Open Wishlist page -> Are ther items ? No -> Pass -> Open Basket -> Are there items? Yes ->Pass   2. Textbox1.Keys()->Textbox2.Keys(),texbox3.Keys,etc,-> buttonAddWishList.Click() -> Open Wishlist page -> Are ther items ? Yes -> Pass -> Open Basket -> Are there items? No ->Pass   3. Textbox1.Keys()->Textbox2.Keys(),texbox3.Keys,etc,-> buttonCance.Click()l -> Open Wishlist page -> Are ther items ? No -> Pass -> Open Basket -> Are there items? No ->Pass   All three tests have the data populate in common.  I don't really care what data is in there and I won't use it in a Data Loop so it can all be the same and be written into a single test so I don't have to duplicate all those .Keys() and .Clicks() into all my KWTs So, create one KWT PopulateOrder that does the keypresses. One step further I can see the only thing that distinguishes the process is what button gets clicked.  If I specify this as a parameter like PopulateOrder(OrderAction) I can change my tests to this by simply dragging the new KWT into my visualiser :   1. PopulateOrder(Order) -> Open Wishlist page -> Are ther items ? No -> Pass -> Open Basket -> Are there items? Yes ->Pass   2. PopulateOrder(WishList) -> Open Wishlist page -> Are ther items ? Yes -> Pass -> Open Basket -> Are there items? No ->Pass   3. PopulateOrder(Cancel)->Open Wishlist page -> Are ther items ? No -> Pass -> Open Basket -> Are there items? No ->Pass   The last steps in  my Populate order is an if statement:    If(OrderAction equals "Order"){buttonPlaceOrder.Click()}   If(OrderAction equals "WishList"){buttonAddWishList.Click()}   If(OrderAction equals "Cancel"){buttonCancel.Click()}   If I drag the KWT into another KWT I can supply this parameter.  Problem is, if a user doesn't know the exact string required and they type in, say "PlaceOrder", the KWT will fail because none of the if statements match.  If on the other hand I can define the parameter as an enum that the user can choose from a dropdown I know the logic will always work e.g.   if(OrderAction equuals OrderActionEnum.Order) {buttonPlaceOrder.Click()}   It's something I would really have appreciated when I started using TC.   It would have helped standardise my tests by always having the option based parameters defined, thereby avoiding loads of rework due to early inexperience. It still helps because I wouldn't have to open the PopulateOrder just to double check what string I need to send. ... View more

Hi,   I regularly manage to have enough KWTs, scripts and project tabs open to make the tabs run into a second row.  I find though that at any given time there's only 2 or 3 I use intensively at a time.  For example, I have a test keywordtest for experimenting with new scripts.  Each time I open a script to debug or step through that tab gets pushed out until it ends up on the second row of tabs and I have to search for it again - repeatedly.  What would be awesome is if we could say, decide three tabs are used very intensively at the moment and are important to have them within easy reach, please always keep them leftmost in the tabs.  I know there is right click=>default docking in Workspace, which appens to move it to the top if it's already tabbed, but as soon as I decide some other tab is more important, default docking in Workspace kicks all the tabs all over the show again and I have to redo the docking.  Just a plain "Pin" and it always stays there and "Unpin" and it can go where it wants again would suffice.   Regards,   ... View more

everytime you open a keywordtest the project tree jumps to its location. if you have many many items in your tree it can be really annoying because you have to scroll and scroll. would be nice to have an option to disable the automatic behavior and use manual expansion (if needed). ... 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

If you're running a keyword test via script, especially in a data driven environment where the data dictates which test to execute, it would be useful to be able to get a count of the parameters on a keyword test.  Currently, for any keyword test, you have access to the Parameters object for the test and then just each parameter individually.  There is not a way to iterate through those parameters and assign values prior to execution nor is there a way to simply get a count of the parameters so you can build your parameter list to pass to the Run method.   It would be nice if, on a per test basis, you have access to something like KeywordTests.MyTest.Parameters.Count and even some way of iterating through the collection to set the values prior to test execution... something like going through all the parameters, setting the values, and then just executing "Run"...    The idea behind this, again, is to make implementing keyword tests in a data driven framework easier. With the above changes, you can add parameter values to a keyword test in a more generic way.  A framework developer could then (if the KeywordTest by name feature gets implemented), find a keyword test simply by name, assign parameter values to the keyword test straight from data without foreknowledge of the test ahead of time, and execute the keyword test.  A much more generic and dynamic automation framework could be created then to integrate keyword tests more fully into a data driven structure. ... View more

Runner.CallMethod works pretty well with regards to running Keyword tests.  You can do a syntax like:   Runner.CallMethod('KeywordTests.TestName.Run', 'parametervalue'); However, this is a bit clunky to me. First of all, if you don't have the name up front but want to parameterize this call, you would need to do a concatenated string for the object name. Secondly, this just seems to be a bit out of the way.  Code Completion already knows all the tests associated with the KeywordTests object so the information is already there.   It would be nice to do something like   KeywordTests.TestByName('MyTest').Run('parametervalue'); This just seems more intuitive and lends itself to a much cleaner implementation for creating a framework around the tests.   Note that I'd prefer the keyword test to be returned by name so that we have access to things like Test.Variables and Test.Parameters (see my other ideas on KeywordTests). ... View more

One of the beauties of Script Extension Runtime Objects is that you can create code that is shared across ALL projects without having to include the code units in the projects themselves.  I am involved in the process of creating a detailed test automation framework where a good bit of the framework code is encapsulated in script extension runtime objects.   However, one of the drawbacks I've run into is that, if the framework needs to execute a Keyword test instead of simply a Script routine, the code cannot reside in the extension. Currently, Script Extensions do not support the KeywordTests object and all the methods and objects underneath.   It would be nice to be able to execute KeywordTests within script extensions so I'm formally requesting the ability to do so. ... View more

it is not possible to work with multiple keywordtest-logs at the workspace. if you have one opened and opens another one, the first opened one will disappear. ... 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