Feature Request: Support for modern Python 3.13+ third-party libraries (Pandas/NumPy)
Hi everyone, I’m currently facing a major challenge regarding the integration of modern Python 3rd-party libraries, specifically Pandas and NumPy, in TestComplete. The Issue: Since TestComplete updated its Python engine to 3.13, attempting to use these libraries results in the error: "ImportError: cannot load module more than once per process." While I understand that TestComplete has limitations regarding C-extension modules, this is critical for many of us who rely on data-driven testing. Using native TestComplete DDT is significantly slower and less efficient for handling large datasets compared to the speed and flexibility provided by Pandas. The Impact: This issue is preventing us from running key parts of our automation framework. Our automated testing was working flawlessly before the update, and now we are forced to either use inefficient methods or seek external workarounds. My Request: I would like to formally request that the TestComplete team looks into improving the compatibility with modern Python libraries or provides an official, stable mechanism to allow for these modules to be reloaded/re-initialized within the TestComplete process without triggering the "load module more than once" error.Is anyone else experiencing this after the move to Python 3.13? If this is affecting your workflow, please upvote this post so we can get more visibility on this request.Thanks, OscarGitHub Copilot integration with TestComplete
Hi team, in the current world, the programmers are using Stack overflow to find code snippets for simple problems, and git hub has a feature called Copilot, which we can use to suggest the code sample which works like a suggestion dropdown when we use some testcomplete methods, it would be great if we create any kind of plugin or some functionality which can do the above mechanism to make our work easier. Thanks and Regards, Sathish Kumar K
Support for Automated Script Extension Installation and Updates in Azure Pipelines
Feature Request: Support for Automated Script Extension Installation and Updates in Azure Pipelines Problem Statement: Currently, there is no way to automatically install or update script extensions in TestComplete or TestExecute during Azure pipeline runs. This results in a manual and repetitive process of updating script extensions on multiple machines, which can be time-consuming and error-prone. Our team manages script extensions in a source control repository, and we pull them onto the machines as part of our pipeline workflow. However, after the files are updated, we must manually open the "Install Script Extensions" UI on each machine to reload the extensions. Occasionally, we also need to re-add the script extensions folder, particularly after updating TestExecute. This manual process creates inefficiencies, especially when managing multiple machines or frequently updating script extensions. Current Workaround: Pull script extension files from source control to the appropriate folder on the machine. Open the "Install Script Extensions" UI manually to reload them. Re-add the script extensions folder if it gets removed (e.g., after a TestExecute update). Proposed Solution: Introduce a mechanism to install or update script extensions automatically during pipeline runs, without manual intervention. Command-Line Interface Support: Add a command-line option for installing or updating script extensions. Example: TestExecute.exe /InstallScriptExtensions "path\to\script\extensions" Example: TestExecute.exe /ReloadScriptExtensions (mimics what clicking the Reload button in the Install Script Extensions folder does) Benefits: Streamlines the automation workflow for teams using TestComplete and TestExecute in CI/CD pipelines. Reduces manual effort and human error associated with installing/updating script extensions. Improves consistency and reliability when running tests across multiple self-hosted agents. Impact: This feature would significantly enhance the usability of TestComplete and TestExecute for teams integrating with CI/CD tools like Azure Pipelines. It would be particularly beneficial for teams working in large-scale environments or frequently updating script extensions.
Managing Execution Plan with Scripts
Hi everyone, For projects with a large number of scripts (e.g., ~100 or more), manually adding and configuring them in the Execution Plan can be a time-consuming and tedious process. The ability to manage the Execution Plan directly from the script would greatly simplify this task and improve overall efficiency. Description: Add the ability to access the Execution Plan directly from the script, and provide controls to shift the execution plan up, down, left, or right. Also, allow updating of the "On exception" and "On error" settings from within the script. Rationale: This would give users more control and flexibility in managing the test execution flow, making it easier to optimize and maintain complex test suites. Best regards görenekli
Add .MD (markdown file) support
I would like to be able to define a simple README.MD file (or whatever.MD) in a project or folder location in a project to provide documentation for other developers and/or future me. Currently I have to use a script file to do this and I don't like creating empty script files just to provide myself with module-level documentation.
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:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe" "C:\Users\USridhar\Documents\TestComplete 15 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.
