Menu

qTest Launch 1.3+ OnDemand Release Notes

Launch Hotfix 1.3.2 OD 26 September 2018

Addition of Flood to the 9-Box

We are happy to announce that Flood has been added as a feature to your qTest suite 9-box. 
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. 
 
Note: 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.
      • Note: 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.
        disconnet_qTest.png
        • The "Integrations" page displays. Here, you can see your qTest projects associated with your Flood account. To disconnect, select the Disconnect icon.
          Disconnect_option.png

Bug Fixes and Improvements

  • Ticket 20014: Universal Agent fails to submit results RangeError: Invalid time value
  • Fixed an issue that caused Tosca parser failed to parse Tosca results when executing Tosca in distribute mode
  • Ticket 18881: Postman JUnit parser failed to parse the XML result having single <testsuite> tag. This has been fixed.

qTest Launch 1.3.1 OnDemand Release Notes - August 06, 2018

Enhancements

Postman Json Parser

This enhancement enables the parser to parse the JSON result generated by Newman to better support the nested structure test result.  Ticket reference: 18881.

New Built-In Parsers

  • Postman JUnit. This parser parses JUnit XML result generated by the Newman Command Line tool.
  • Allure Results. This parser parses reports generated by Allure reporting framework which is used by an automation framework, e.g., Protractor, and collects test cases to submit to qTest Manager
  • Unified Functional Testing (UFT): This parser parses execution results generated by Unified Functional Testing (UFT) tool and collects test cases to submit to qTest Manager

For more information on parsers, read this article. 

Bug Fixes

  • JUnit for Java parser:
    • Ticket 18881: Failed to parse JUnit XML result with multiple <testsuite> tag.
    • Order of test run logs should start with one instead of 0
  • Launch did not update the IP address of the automation host when the IP address changed. This has been resolved
Powered by Zendesk