QEditor is the next-generation highly advanced test development environment for QWord and Robot Framework test scripts. By leveraging a massive amount of test case data, it guides you through the scripting process and helps you to create scripts by constantly monitoring and analyzing your actions. The guidance is then provided from various directions. It supports numerous features to aid in your test development and make it extremely efficient.
Here are a few benefits of doing test development with QEditor:
There are two ways of using QEditor: directly within Copado Robotic Testing or as a VS Code extension. For the former, you need to have a Copado Robotic Testing account. If you don’t have a Copado Robotic Testing account, you can quickly create one at https://robotic.copado.com/signup in US and http://eu-robotic.copado.com/signup in EU.
For the latter, you can install QEditor to your Visual Studio Code (VS Code). All the predictive features and cloud execution capabilities are made available to you when you integrate your VS Code with your Copado Robotic Testing account. If you do not wish to sign up for Copado Robotic Testing and wishes to use this extension as a standalone for writing Robot framework test scripts that is possible too.
Now, we will tell you how to configure your VS Code and Copado Robotic Testing.
QEditor leverages massive amount of test case data when its guiding the user through the scripting process. In order for the QEditor to get access to the data, it must be configured properly. The first and foremost you need to define a "Personal access key":
QEditor will ask you to enter the access key when you start QEditor. Note that the access keys are specific to the region which you are logged in (EU or U.S.). You should also make sure that the access key that you provide matches the environment and region defined in QEditor settings (Press
In order to use advanced predictive features or Copado Robotic Testing features from QEditor such as test execution and live testing, each test suite that you locally work with must be associated with corresponding test suite in Copado Robotic Testing. This also means that you must have have the very same test suite defined in Copado Robotic Testing as you are locally working with.
The integration is defined through a configuration file called
The easiest way to get the URL is simply to navigate to your test suite in Copado Robotic Testing and copy the URL from your browser.
If you have not defined the above configuration file and you attempt to start test execution, QEditor will ask and guide you to create this configuration file.
Predictions and Completion Suggestions
Using a massive set of test cases data, QEditor has trained machine learning algorithms to predict next most likely test steps in your test cases. Based on your test cases and test flow so far, QEditor makes predictive suggestions to what your next test steps is likely going to be. Along with predictive suggestions, QEditor also provides you with completion suggestions. The various places in a test cases where you can leverage such predictive and completion features are as follows:
Test Case Analytics
With help of the massive test case data, QEditor can provide advanced analytics on your test case. By looking at you test case and its flow the editor can make predictive estimations on a test case’s probability of success, execution time, correlation with other test cases and more information on test generation. You can turn on/off from a list of advanced analytics features.
Test case analytics is accessible from annotation at the top of every test case.
Annotations and Guidance
There are a lot of places where QEditor provides you with annotations and guidances. You have probably used a few of them already while launching a live testing session, viewing advanced analytics etc. Annotations and guidances are often in the editor with light grey fonts.
Selecting library QWord for QWord Palette
You can choose the QWord library that the QEditor uses in the QWord Palette. Status Bar of Visual Studio Code on the bottom right of the editor will show you the active library and you can switch the library simply by clicking the status bar element. Alternatively you can press
BrowserStack Viewer allows you to monitor BrowserStack mobile and web sessions executed on BrowserStack. It shows a summary of the completed session as well as screenshots of an ongoing session. The main purpose is to provide visual help when developing and debugging tests locally. However, it is not recommended to use this tool as a viewer for normal test executions, as it will pollute the log with “Take screenshot” entries.
How to acquire the Session ID
In order to get the Session ID, execute any test suite using the QConnect Dev terminal with the following command:
Once the suite is executed, you will find the Session ID in the console Log like in this snippet:
The release notes are available here.
QEditor for VS Code is supported on the following systems:
Here are some solutions to problems you might encounter working with QEditor. It also advised to review the content of QEditor "output channels" (
QEditor fails to start
QEditor activation problems are often due to conflicting Robot Framework extensions which may prevent QEditor from starting. In order to resolve, go to Extensions panel (
QEditor language server fails to initialize
QEditor leverages a language server component for most of its features which is launched automatically as part of the QEditor activation routine. QEditor language server will only run on the supported platforms and an attempt to run QEditor on other platforms may trigger this error.
QEditor does not make predictions during the scripting
QEditor leverages Machine Learning algorithms when guiding the user through the test creation process. The editor requires assets that it downloads from the Copado Robotic Testing cloud entity. In order to do so, you must provide a proper Access Key that matches the region in which you are working in. Once a proper Access Key has been provided, the QEditor will provide predictions, etc. See Configuring QEditor for details.
QEditor does not predict argument values
Argument values can be predicted by the QEditor when it has been configured with (1) access to Copado Robotic Testing environment through an Access Key and (2) we have associated the current work in VS Code with a project in Copado Robotic Testing. See Configuring QEditor for details.
Questions, Feedback, Contributing
You can post your questions and feedback on our community pages. If you are a Copado Robotic Testing user, you can raise a question using in-app messaging.
We really hope you like our product. Write your reviews here.
When submitting a feature request, bug report, etc. please include the output from both "QEditor" and "QEditor Language Server" (
By downloading and using the Visual Studio Copado QEditor extension and its related components, you agree to the Copado Robotic Testing product license terms and privacy statement.