Pulse 9.1.0 Release Notes

October 1, 2018

qTest Pulse 9.1.0 OnDemand includes an enhanced UI experience along with the addition of these new features:

Pulse Rule performance metrics
Enhanced code editor
Visual Rule Generator
You can now execute and test the Rules from within the UI and see the response in real time.
Uses AWS Lambda to execute rules! This will be reliable AND very scalable, of course.
New APIs to use with Scenario 2.0.4-1 so that you can access your Scenario Features and steps directly from the API. You can also write back to color-code the steps for passed/failed/skipped with the APIs. (hardcoded to red green yellow)

We also have a qTest Pulse Quick Start Guide that provides you with more detail on these changes along with the action items you need to complete.

There are a few action items that you will need to do before you can use Pulse 9.1.

Update the following Constants:

qTest API Token for authorization
Scenario Project ID-although this was a constant used in Pulse 9.0 you will need to update the value for Pulse 9.1
Export the new 9.1 Pulse Rules from GitHub

New Features

Rule Performance Graph

A new Rule Performance Graph is available at the top of the Pulse homepage that shows you the number of actions that have been executed over a specific amount of time. You can filter the 'Viewing' dates over the past week or the past month, using a rolling calendar. The bar graph displays each Action that was executed and provides hover text with the Action name and execution count.

Enhancements

Pulse Rules

The Rules section includes several new enhancements, listed below:

'Trigger' is the new term for a Pulse Event (from 9.0) which is your webhook.
A 'play' button is now available in the Options column which hits the 'Trigger' (webhook) with the payload and returns results in real time.
A Status filter allows you to view 'active' or 'inactive' Pulse Rules.
A Tag/Name filter allows you to view Rules based on tags/names associated with your Pulse Rules. The Tag/Name will be handy as your Pulse Rules library expands. An example Use Case for Tags is associating version numbers with a set of Rules.
The Execution Log provides you with more detail on the Rule Execution including the Payload, Standard Output, Standard Error, and the Response.

You will not be able to import your Pulse v9.0 Rules into Pulse v9.1. You will need to export the 9.1 Pulse Rules from GitHub and import them into your own environment.

Constants Relocated

The Constants tab has been moved from the header of the Pulse homepage and relocated to the bottom of the screen next to the Actions.

Pulse Filters

Filters have been added to each Pulse section ex: Triggers, Actions, Constants. These filters are separate from one another and specific to the category you are filtering.