Menu

qTest Parameters 2.1+ OnDemand Release Notes

2.1.7 Release Notes - September 26, 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

  • Ticket 20584: Issue with creating test runs using a dataset

2.1.6 Release Notes - August 10, 2018

Bug Fixes

  • Fixed '500' errors when consuming the following Parameters API:
    • /api/v1/parameters/link
    • /api/v1/parameters/unlink
    • /api/v1/parameters/detail
    • /api/v1/parameters/search
  • Ticket 19299: Fixed issue when importing Excel data to Dataset. Previously, a percentage in Excel would display as a decimal value in the Dataset after importing and some numbers would display as different values. This has been resolved. 

2.1.5 Release Notes - July 25, 2018

Bug Fixes

  • Cannot login to qTest Manager through login API: /oauth/v1/login. This has been fixed. Notes: this only impacts API users, the application users are still able to access Parameters from qTest Manager.

2.1.4 Release Notes - July 20, 2018

Enhancements

  • Ticket 17129: Feature Suggestion - Parameter selection UI in manual dataset creation will now display hover-text if the dataset value contains more than 20 characters. This enhancement will allow you to view the entire value in the list in the event the dataset values contain similar characters.
  • Parameters API enhancements:
    • /api/v1/data-sets/create: response code change from 200 to 201 for successful action
    • /api/v1/parameters/{pid}/values: Response code had changed from 200 to 201 for successful action
    • /api/v1/parameters/query: Response data had changed from array objects to single object
    • /api/v1/parameters/{id}: Added response code 403 for invalid Identifier
    • /api/v1/parameters/create: 
      • Response code had changed from 200 to 201 for successful action
      • Added response code 403 for invalid Identifier
      • Added response code 409 for existed Identifier
    • /api/v1/parameters/bulk-delete: Request body had changed from array objects to single object
    • /api/v1/parameters/bulk-archive: Request body had changed from array objects to single object
    • /api/v1/parameters/import: Available duplicate options had changed to: skip/add/overwrite

Bug Fixes

  • Ticket 17356: Bug: In test run creation, the suggested dataset does not contain the required parameters. This is now resolved.
  • Ticket 17047: PYTHON Parameters API: call parameters_api.api_v1_parameters_create_post(body) is returning parameter ID's but they are not showing in the UI. This has been fixed.
  • Ticket 18716: Unable to archive and delete a parameter in qTest. This has been resolved.

 

2.1.3 Release Notes - June 22 , 2018

Bug Fixes

  • Ticket 17868 and 18276: Parameters Swagger API now returns results consistently. You will need to re-download python swagger_client. 

2.1.2 Release Notes - April 13 , 2018

Bug Fixes

  • Ticket 16126: You can now create a Parameter with a Korean identifier. 

Enhancements

  • Ability to filter datasets by projects
  • Added login API for SSO users

2.1.1 Release Notes - March 19, 2018

Bug Fixes

  • When a project name is changed in qTest Manager, the new name will be synced to qTest Parameters and displayed properly.
Powered by Zendesk