How to Create/Import Description File for JavaScript - Inquiry
I am attempting to add a description that appears in the AutoComplete Menu for various functions as can be seen with many of the built in functions/methods for a Javascript file. How would I go about doing so? So far I have attempted creating a description.xml file for one of my JavaScript Files and put the file in the same directory with my JavaScript files (./Scripts/). Is there a process I need to perform to actually import this file into the project? Also, assuming this description.xml file can perform the my desired action, can it be used to add descriptions to functions/methods for multiple JavaScript files? I would assume this is by having multiple of the <Script> tags in the xml, though want to confirm before further proceeding down this route. Below are images of what I am trying to accomplish, in case I am going down the wrong route entirely: Current state: Desired State: I have also attached the description.xml file I am using in attempting this. Please let me know if any additional information is required!
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örenekliSmartBear Test Extension manual installation
I want to setup Test complete on our Azure cloud machine, since it do not have internet access i followed the steps in the below link to install SmartBear Test Extension manually https://support.smartbear.com/testcomplete/docs/app-testing/web/general/preparing-browsers/chrome-extension.html?sbsearch=edge%20browser%20extension Issue i am facing is Edge and chrome browser SmartBear Test Extension is getting installed only for my user id and if i login using Test account, the Smart bear extensions are not available. Anyone else faced similar issue? I am not sure if i am missing something when manually adding the SmartBear Test Extension.
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/copilotchanging dropdown menu field for every testing
Hi Guys, what I want the system to do: I will check a field, it is a dropdown menu, and if this field is for example A, I should select another option for example B for this field from the dropdown list. Or if this field is B I should change it to A so how can I do it with scripting? Do you have an idea? I could have not found the correct codes for this:( For example in one test the field contains A and you should change it to B, than for the next time the field is B and you should change it to A.
