KeyWord Test Operations Favorites Category
The Frequently Used category is overall great, but I have some gripes with it. Unable to manually choose the order of the Operations that appear. The Operations supposedly order themselves automatically based on how often they are used, but it sometimes seems a bit arbitrary, with some Operations appearing on the list i think i use less than some Operations that do not show up on the list. Only 10 Operations can be displayed at a time. This is too few Operations to show and i often find myself needing to type search for addition Operation i often use. In the default Workspace layout / 'Desktop' / screen arrangement there is room for maybe at least another 10 Operations to be displayed on a 1080p monitor. showing 20 might be a bit excessive tho. Unable to choose which Operations appear. While this problem generally sorts itself out after a long time in usage, it would be nice to be able to just choose what shows up, or if the usage data where to ever be wiped for some reason (getting a new workstation, etc) I think adding a Favorites Category would solve all of the above small issues.
Automatic creation of "Variables"
While recording a test, we input values into one or more fields of a form under test. Currently TestComplete "hard codes" these as constant values in the test steps. even when we create a script out of these steps, the constant values go in there. In order to make the script work for generic test data, testers have to manually create variables and assign the values, which takes as much time as there are input fields. In order to reduce the cycle time from recording to replay with any test data, it is suggested that: For all input fields that the user enters some value during recording of a test, TestComplete has to create as many variables automatically Assign the default values to these variables with the values supplied / keyed-in by testers during test recording. This feature can be made available as one of the project / tool options.
project explorer tree expansion
With right click on a branch in the project explorers tree the option for collapsing/expanding appears. But everytime it collapses/expanses the whole tree and not certain branches. When you working with complex projects it would be great to have the option to just collapse/expand a single branch.
Keyword tests in different directories should be allowed to have the same name
We have different directories for keyword tests associated with each page of our application. As we work on them, we would like to have that keyword test called something like Sandbox. Being in different directories, that should be allowable, but TestComplete complains. For example, given KeywordTests->LoginTests->Sandbox, we should be able to create a keyword test KeywordTests->UserAdminTests->SandboxWhen change a name in NameMapping, Then the object name in script tests would also update
Let's say you don't like the name you gave an object in the NameMapper. When you change the name of that object, the name will also be updated in any and all Keyword tests which this object was used in. However, the name will Not be updated when used in script tests. It would be nice if the name would be updated in Scripts. Sometimes we think of better naming conventions and want to rename some objects.
Add a feature in TestExecute tool to run/enable single testcase from Execution Plan.
I had prepare a test plan with mutiple keyword tests on Execution Plan and want to execute only some of them using TestExecute tool but there is only option to run full project using TestExecute tool. So please implement feature to run single test also from TestExecute tool.Execution plan. Enable Disable redesign
Execution plan. Enabled/disabled The most often scenario for us: Run tests with only several items enabled. Items can be in different groups 1. The Context menu is complicated Every time I have to search for the proper option, when I expect it to be in the first, or second position Also often after disabling the part of the playlist I accidentally press 'Enable All' instead of 'Enable selected' and then I have to start from scratch because Ctrl+Z also does not work on this tab Just 'Enable' and 'Disable' menu items will be enough (maybe 'toggle' may stay, someone can use it) BUT enable or disable action should apply for all selected items So 'Enable all' action could be performed by pressing Ctrl+A and then ClickR, 'Enable\Disable|Enable' Same for 'Disable all' 2. Enabling the item does not enable the parent items So you have to click each parent manually. 3. Ctrl+Z should work in case of undo Enbled Disabled
function to get the name of a module started via Run Keyword Test
Please add a function to get the name of a keyword module, started from another keyword module. I need this to quickly identify a failing module in event handler and to quickly navigate in test report. I'm aware of below methods, but all of them return only the name of main module, from which the child module was run (via Run Keyword Module): Project.TestItems.Current.Name - returns name of the main keyword module aqTestCase.CurrentTestCase.Name - returns name of the main keyword module Project.TestItems.Current.ElementToBeRun.Caption - returns "KeywordTests -" + name of the main keyword module For now, I solved the problem by adding Set Variable Value action at start of every keyword module, which sets the project variable with hardcoded module name. But I don't like this solution, because it requires more steps and can cause potential failure in case the module name changes and someone forgets to change the hardcoded string in given module.
