Ability to get the get/extract the XPath or Css from the name mapping objects
I would like to have one location where I specify the xpath my html elements. Most of the time, this data is stored in the NameMapping. A lot of the time you can use aliases in scripts. However, there are some times ... like for the 'waitelement' which you have to use the xpath or css. I would really like to be able to get the xpath or css from the nameMapping. This would make things a lot safer and less error prone. I use keyword tests as much as I can, but there are times when scripting is beneficial. var myAlias = Aliases.MyWebApp.AdminButton; var selectorArray = myAlias.GetSelectors(); the selectorArray would be an array of objects that looks like this: selectorArray = [{'css', '#myAdminButton'}, {'xpath', '//div/button[contains(@class, 'adminbutton')]'}, {'xpath', //div//button}]TestComplete - Enhance support for dropdowns in Web
I used TestComplete to automate a webshop. Now I run into the issue that it has problems identifying items from dropdowns. I've tested the same webshop(so with no code changes) with PlayWright and performed the same steps, PlayWright seems to have no issue with the same dropdown to select an item from the dropdown.
a button to comment out BDD scenarios in feature files
TestComplete Suggestion: Let's add a comment feature for BDD scenarios, similar to how we comment out scripts. This helps manage scenarios better, select which ones to execute, and streamline testing. Plus, it encourages collaboration and improves documentation by explaining scenario reasoning and test variations.
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
Request for Enhanced Command Line Option to Generate Single HTML Log File in TestExecute/TestCmplete
Hi, when we use the following command line: "C:\ProgramFiles (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe" "C:\Users\USridhar\Documents\TestComplete15 Projects\ProjectSuite3\ProjectSuite3.pjs" /run /p:TestProject1 /exportLog:"E:\Testing\Test6.html" /e We are receiving multiple .html files, but we need only a single HTML file named Test6.html. We prefer not to use .mht files as they are not compatible with Chrome and Firefox.Testcomplete latest version not supporting Firefox 15.5.0esr (32-bit) version
We are using Firefox15.5.0esr (32-bit) version in our company and Test Complete does not support this version in their latest upgrade. Need so much approvals to use old versions of application if need manual installation. So request you to please provide new version supporting Firefox15.5.0esr (32-bit) version
Integrate TestExecute into TestComplete so user can run test cases on remote PC with TestExecute.
I would like to see TestExecute integrated into TestComplete so that a user can control the TestExecute instance to run nominated test cases directly from the TestComplete Project. It would be nice to be able to nominate where test cases will be run i.e. whether to run on the current machine under TestComplete or run on a nominated PC (on the network) using the TestExecute application and license attached to the remote PC. Ideally the user would be able to nominate at an individual test case level where to execute the test with the TestComplete PC being the default option. However, even the ability to nominate entire projects to be tested under TestExecute on a remote PC from the Project Suite Test Items list would be beneficial. The expectation being that the results are captured under a consolidated Project Suite log file for analysis. This is fairly high level but happy to discuss further.Update TestComplete engine to support PEP-622 - Structural Pattern Matching
Structural Pattern Matching (PEP-622) was introduced in Python 3.10 but TestComplete engine does not support it regardless of TC 15.56 contains Python 3.11. When we can expect match/case keywords available in Python scripting?
