Pulse 9.0.2+ Release Notes

Pulse 9.0.4 Release Notes

September 26, 2018

Addition of Flood to the 9-Box

We are happy to announce that Flood has been added as a new option to the 9-box within the qTest product suite.

Flood is a cloud-based load testing tool that gives users the flexibility to test with millions of concurrent users in just minutes, using a shared cloud or your own private cloud resources.

The results from these tests are aggregated into a real-time dashboard so you can investigate and pinpoint the root cause of performance problems as they occur. 

With an open REST API, it is easy to Launch performance tests from any scheduling service like qTest Launch. Jenkins. or Bamboo so that performance testing can happen within your CI/CD pipeline.

Flood is currently only available in the 9-box for OnDemand versions. This new feature will be available for OnPremise customers in a future release.

The following test frameworks can be executed within Flood:

  • JMeter

  • Gatling 

  • Flood Element

  • Selenium 

  • Tosca

As an exclusive for QASymphony customers, you have been granted 20 node hours which allows you to run a 1-hour test with up to 20,000 users.

Read here for more information on how to get started with Flood, or reach out to your customer success manager/sales representative for a quick start session. 

Accessing Flood

Accessing Flood from your qTest suite is easy. To do so, follow these steps:

  1. Select the 9-box, and choose the Flood icon from the 9-box menu.

  2. You are redirected to the Flood suite. Take note:

    • New Flood users will have a fresh account

    • Existing Flood users' accounts will be linked, and they will be taken to their already existing Flood accounts.

    • Projects will automatically be created within Flood to mirror what users already have in qTest.

      • There is an option to disconnect your qTest projects from your Flood account. To do so, select the Integration option in your user drop-down menu.

         

        • The "Integrations" page displays. Here, you can see your qTest projects associated with your Flood account. to disconnect, select the Disconnect icon.

Pulse 9.0.3 Release Notes

June 13, 2018

Bug Fix

  • Previously, when not using an SSL, the service would still provide an HTTPS URL instead of an HTTP URL. This issue has been resolved.

Pulse 9.0.2 Release Notes

May 31, 2018

Enhancements

Option to Hide Constant Values

You now have the option to hide your Constant values, by selecting the 'Make value hidden' check box when editing a Constant in the Pulse Rules editor. This is beneficial for hiding Constant values, such as passwords, tokens, or other IDs. If you choose to hide your Constant values you will not be able to unhide them. Additionally, you can not export a hidden Constant value.

To hide a Constant value, do the following:

  1. From the Pulse homepage, select the Constants tab.

  2. Locate the Constant for which you would like to hide the value and select the edit button. The Modify Constant widget opens.

  3. Select the 'Make value hidden' check box and Submit.

  4. The Constant value will no longer be shown on the Constants page.

Pulse Actions Now Support a Callback Method for Including Response Messages

Pulse actions now support the optional callback parameter. You can use it to explicitly return information back in the event log. (Eyeball)

The general syntax is: callback(Error error, Object result);

Where: error – is an optional parameter that you can use to provide results of the failed Action execution. When an Action function succeeds, you can pass null as the first parameter. result – is an optional parameter that you can use to provide the result of a successful Action execution. The result provided must be JSON.stringify compatible. If an error is provided, this parameter is ignored.

The following are example callbacks:

callback();  // Indicates success but no information returned to the caller.
callback(null);  // Indicates success but no information returned to the caller.
callback(null, "success");  // Indicates success with information returned to the caller.
callback(error);  // Indicates error with error information returned to the caller.

Example Action Code:

Copy 
var message = body.message || "Hello World!";  const PASSED = true;  console.log('Message =' + message);  if (PASSED) {  // Indicates success with information returned to the caller.  callback(null, "success");   } else {  // Indicates error with error information returned to the caller.      callback("Something went horribly wrong!");     } 

Example Result= Success:

Example Result= Null: