PaceEditor features

PaceEditor supports numerous features to aid in your test development and make it extremely efficient. A complete list of features is available to you in editor configurations. Go to file menu and select editor configuration. This will open a dialog box listing the complete set of features with options for enabling/disabling them. Every feature has a tooltip attached to it describing the feature briefly.

features1

The picture above shows the default configuration of PaceEditor. The feature sets are broadly classified into five categories. Towards the end of this document there are other features, which are not configurable.

Warnings

Real-time error detection is enabled in PaceEditor by default. Live check and error detection generate warnings for possible flaws in a test script at various levels. Currently, warnings are generated at following levels

  1. Test case setting level: A test case can only have one [Tags] line and validating correct test generation usage.

  2. Keywords level: Number of arguments, keyword name, return arguments etc.

A script with warnings is executable but it might have potential flaws. You may turn warnings on/off by enabling/disabling this feature. A warning is marked by a curvy red underline and always accompanies a concise explanation. You may choose to peek into the problem or apply a possible quick fix. In the images below, I am peeking into the problem.

features2
features3

Prediction and completion suggestion

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:

  1. Enable predictive editor features based on Machine Learning models

  2. Enable predictions of Pacewords and other keywords

  3. Enable predictions of test case settings

  4. Enable predictions of test generation configuration options

In the images below, PaceEditor is making an auto-completion suggestion for a PaceWord and a highly likely argument.

features4
features5

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.

  1. Enable test case analytics and estimates

  2. Enable general test case analytics

  3. Enable test case execution result predictions and analytics

  4. Enable test case execution time predictions and estimates

  5. Enable test generation analytics and estimates

Test case analytics is accessible from annotation at the top of every test case.

features6
features7

Test flow analytics

From the normative models of test cases, this features identifies the likely/unlikely test steps in your test cases. The central idea is to guide your test cases towards Qentinel Pace test automation best practices. Due to its computational expensive nature, it is set off by default.

In the image below every test step is highlighted with a color code. From green to red, where green is very likely to be there, however dark red is a deviation from the data set.

features8

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.

  1. Script annotations and guidance

features9
  1. Scripting guidance and hints through annotations placed on top of the current line

features10
  1. Test case summary annotations

features11
  1. "Create new test from template" annotation and action: Present at the end of your test file.

features12

Auto save

This functionality protects any unsaved changes in your test file when your session gets interrupted for any of the various possible reasons: browser crashes, accidentally closes editor or website, navigate to other websites etc. When you get back to the same file PaceEditor prompt a window asking whether to restore your unsaved data or discard it. The restoration point gets updated continuously when you are editing a file.

Auto save is tied to your browsers memory and hence it will only work when you launch Qentinel Pace from the same browser and same machine. Besides, that there is no expiry date to the restoration point.

features13

PaceWords documentation

PaceWords documentation is made available to you in the editor itself on many avenues.

  1. Palette: You could enable PaceWords palette on the right hand side of your editor from keyword library toggle.

  2. Hover over: Hovering over a particular PaceWord in the editor.

  3. Editor suggestions: Hovering over editor provided PaceWords suggestion.

You can change the library specific context of PaceWords from PaceWords library menu.

The documentation rendering is low on readability and we would recommend you to refer PaceWords documentation