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.
Github Copilot Integration
GitHub Copilot suggests code completions as developers type and turns natural language prompts into coding suggestions based on the project's context and style conventions. One new idea would be having a copilot plugin for testcomplete would increase productivity and coding efficiency URL for reference - https://github.com/features/copilot
Possible bug with using regexp for manual object name mapping
I have some desktop application under test where MDI windows have highly variable WndCaption property. This produces an awful lot of name mappings when I record keyword tests. Auto-generated mappings use two parameter-value pairs: "WndClass: Afx:00400000:b*" and "WndCaption: <whatever_caption>". However the captions have some distinctive patterns and naturally I wanted to utilize those patterns to reduce number of mappings. So I created the manual object mappings like this: wndType1: WndClass == "Afx:00400000:b*" WndCaption == "regexp:^Object: .*" wndType2: WndClass == "Afx:00400000:b*" WndCaption == "regexp:^!(Object:).* - \(.*\)$" ... and so on, paying special attention to possible ambiguities when constructing the regular expressions. Mapping worked as expected, showing correct MappedName in the Object Browser. Upon converting the existing keyword tests to use the new mapping, everything functioned seamlessly. However, when I attempted to record new keyword tests, TestComplete consistently generated its own mappings instead of utilizing the existing ones, despite my efforts. After some trial and error, I resorted to replacing the regular expressions with the combination of conditions and wildcards: wndType1: WndClass == "Afx:00400000:b*" WndCaption == "Object: *" wndType2: WndClass == "Afx:00400000:b*" WndCaption == "* - (*)" AND WndCaption != "Object: *" And all of a sudden everything works like a charm! I believe this behavior is not intended, especially since I couldn't find any mention of limitations related to the use of regular expressions in the documentation available.
