PaceEditor is the next-generation highly advanced test development environment for PaceWord 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 over PaceEditor:
There are two ways of using PaceEditor: directly within Qentinel Pace or downloading it to your VSCode. For the former, you need to have a Qentinel Pace account. If you don’t have an account Qentinel Pace account, you can quickly create one at https://pace.qentinel.com/signup.
For the latter, you can install PaceEditor to your VSCode. All the predictive features and cloud execution capabilities are made available to you when you integrate your VSCode with your Qentinel Pace account. If you do not wish to sign up for Qentinel Pace 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 VSCode and Qentinel Pace.
PaceEditor leverages massive amount of test case data when its guiding the user through the scripting process. In order for the PaceEditor to get access to the data, it must be configured properly. The first and foremost you need to define a "Personal access key":
PaceEditor will ask you to enter the access key when you start PaceEditor.
In order to use advanced predictive features or Qentinel Pace features from PaceEditor such as test execution and live testing, each test suite that you locally work with must be associated with corresponding test suite in Qentinel Pace. This also means that you must have have the very same test suite defined in Qentinel Pace as you are locally working with.
The integration is defined through a configuration file called "pace.yml" which must be placed to the root directory of your test suite. An example configuration file is shown below
The easiest way to get the URL is simply to navigate to your test suite in Qentinel Pace and copy the URL from your browser.
If you have not defined the above configuration file and you attempt to start test execution, PaceEditor will ask and guide you to create this configuration file.
Predictions and Completion Suggestions
Using a massive set of test cases data, PaceEditor 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, PaceEditor makes predictive suggestions to what your next test steps is likely going to be. Along with predictive suggestions, PaceEditor 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:
In the images below, PaceEditor is making an auto-completion suggestion for a PaceWord and a highly likely argument.
Test Case Analytics
With help of the massive test case data, PaceEditor 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 PaceEditor 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 PaceWord for PaceWord Palette
You can choose the PaceWord library that the PaceEditor uses in the PaceWord 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 F1 (or Ctrl+Shift+P) in the Visual Studio Code editor and start typing "Pacewords". This will bring up commands that you can use to switch between Web, Mobile and Vision libraries.
The release notes are available here.
PaceEditor VSCode extension is supported on the following systems:
Questions, Feedback, Contributing
You can post your questions and feedback on our community pages. If you are a Qentinel Pace 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 "PaceEditor" and "PaceEditor Language Server" (