QASymphony Claimed Company

Our mission is to transform the way global enterprises create quality software. read more

EMPLOYEE PARTICIPANTS: 4

TOTAL RATINGS: 80

CEO: David Keil

QASymphony FAQs

QASymphony's Frequently Asked Questions page is a central hub where its customers can always go to with their most common questions. These are the 1001 most popular questions QASymphony receives.

Frequently Asked Questions About QASymphony

Automation Host 2.3.3 Release Notes - February 17, 2020

Enhancements
When executing Tosca test using ToscaCIClient tool in Universal Agent, the updated Tosca test steps, which are generated in the XML result, will also be updated to the test run in qTest Manager
Bug Fixes
Ticket #
Component
Description
35237
Automation Host
Automation Host did not automatically start when system starts up in Linux. This has been fixed.
NA
Automation Host
Failed to automatically upgrade Automation Host on Mac
NA
Automation Host
Cannot delete agent associated with an archived/deleted project
NA
Automation Host
Fixed vulnerabilities
View Article
qTest Jenkins Plugin Release Notes

qTest Jenkins Plugin 1.4.5 - Feb 10, 2020
Enhancements
Previously, when executing Tosca test with qTest Jenkins Plugin, only FAILED test logs are submitted to qTest Manager. Now, the test logs for PASSED test cases are also submitted to qTest Manager.
When executing Tosca test with qTest Jenkins Plugin, the updated Tosca test steps, which are generated in the XML result, will also be updated to the test run in qTest Manager
Bug fixes
Ticket #
Component
Description
None
Jenkins Plugin
Fixed vulnerabilities
qTest Jenkins Plugin 1.4.4 - August 09, 2019
Bug fixes
Ticket #
Component
Description
30380
Jenkins Plugin
Jenkins Plugin doesn't show builds higher than 39999
qTest Jenkins Plugin 1.4.2 - June 24, 2019
Bug fixes
Ticket #
Component
Description
24641
Jenkins Plugin
qTest Jenkins Plugin cannot bypass proxy even the proxy is configured in No Proxy Host in Jenkins'proxy setting
22269
Jenkins Plugin
qTest Jenkins Plugin creates test suite with an incomplete name
qTest Jenkins Plugin 1.4 - August 24, 2018
New Features
We added the ability to execute Tricentis Tosca tests and the results will submitto qTest Manager. This feature can be achieved via FreeStyle project configuration and/or Pipeline script generation. Follow these instructions to configure Tosca integration in qTest Jenkins Plugin.

Jenkins and Bamboo Integration
qTest Jenkins Plugin 1.3.1 - April 06, 2018
Bug Fixes:
Tickets15799,15994,15949,15773,15906: Update qTest Jenkins Plugins to work with Jenkins 2.113.
Ticket 15082: Fixed an issue with Proxy configuration in Jenkins.
Ticket 15243: Unable to retrieve data from Manager in Jenkins.
qTest Jenkins Plugin 1.3.0 - Mar 12, 2018
New Features/Enhancements
Jenkins Plugin 1.3.0 now supports Jenkins Pipeline with qTest Managerfor advanced continuous integration scenarios. You can now generate a pipeline script from the qTest Jenkins Plugin to submit test results to qTest Manager. The script, once generated, can be used as a step in your entire pipeline scripts.
Previously, if you were using Jenkins Pipeline youwould need to use the QASymphony API directly to upload your test results.
More Information
For more information, read the article.
View Article
Launch 1.5.3 Single Server Upgrade Guide for Docker

Overview
In this article, we provide step-by-step instructions to upgradeupgrading to qTest Launch 1.5.3 on a CentOS/ Ubuntu machineusing Docker and then connect it to qTest Manager 9.8.3 on adifferent machine.Please read the instructions thoroughlybeforestarting your installations.
The Q4 2019 OnPremise release, does not include a version change for Launch. Therefore, you will be upgrading from the previous 1.5.3 (with Docker deployment package 4.9) to the newest 1.5.3 (with Docker deployment package 4.10).
If you want to deploy qTest Launch 1.5.3 andqTest Manager 9.8.3 on the same machine using Docker, check out this article Manager 9.7.1 to 9.8.3 Single Server Upgrade Guide for Docker.
To request assistance withupgrading or obtain the self-upgrade links, complete the Upgrade Request Form.
Note:If you are performing a fresh install, use the OnPremise New Install Form and reference the OnPremise InstallGuide.
Before You Begin
qTest Launch 1.5.3 only works with qTest Manager 9.7.1 or later.
qTest Manager has been deployed using Docker on a separate machine.
Docker 17.03has been installed. Follow these instructions to install Docker on your machine if you have not done so already.
For CentOS, you need to follow additional instructions to adjust Docker Storage Driver from overlay to device mapper.
For CentOS 7.X+ or Ubuntu 18.04 machines: Docker requires a 64-bit installation and your kernel must be at least 3.10.
Read the following:
Getting Started with Q4 2019 OnPremise
Recommended Hardware Requirements
Upgrade qTest Launch to 1.5.3
Shutdown the Previous Deployment
Openthe Terminal.
Accessthe directory where you extracted the previous docker deployment package 4.9, shut it down and create a backup.
$ ./shutdown
Download the Deployment Package
Downloaddocker-deployment-4.10 package.
$ wget <ENTER DOWNLOAD LINK HERE>
Extractthe package.
$ tar -zxf <DOWNLOADED PACKAGE FILE NAME>
Accessthe docker-deployment-4.10 directory.
$ cd docker-deployment-4.10
Configure Applications
$./configure--apps"launchlaunchlb"
Configure URL and port
Deploy qTest Launch with HTTP
$./configure --launch-url "http://<public IP of current machine>:<launch port>" --launch-http "<launch port>" --cluster "<IP of postgres docker server>"--qtest-url"http://<qtest manager's domain or public IP address>:<qtest port>"
Deploy qTest Launch with HTTPS
$ ./configure --ssl-key "<SSL Key>" --ssl-cert "<SSL Cert>" --ssl-ca "<SSL Ca>" --launch-url "https://<public IP of current machine>:<launch https port>" --launch-https "<launch https port>" --cluster "<IP of postgres docker server>"--qtest-url"https://<qtest manager's domain or public IP address>:<qtest https port>"
Upgrade qTest Launch
Execute the command below to upgrade qTest Launch:
$ ./upgrade
Start the deployment process
$./startup
The script will download the application images to the Docker. It may take acouple of hours depending on your network connection.
Open your web browser, access qTest Launch using the URL specified above in the configure command to validate if it has started successfully
Once the installation is complete, access qTest Manager via your browser and setup for qTest Launch.
You have finished upgrade qTest Launch.
Troubleshooting
If the installation was not successful, perform the following steps to rollback to qTest Launch 1.5.3 (with Docker deployment package 4.9).
Start launch 1.5.3 server
# cd /path/to/docker-deployment-4.9
# ./startup
When the process is complete, contact Customer Support to troubleshoot the issue with upgrading qTest Launch.
View Article
qTest Sessions OnDemand Release Notes

Sessions 4.3.2 OnDemand February 10th, 2020
Bug Fixes
Ticket
Component
Description
NA
Submit New Defect to VersionOne
Cannot attach screenshot into the defect
NA
Update existing defect to VersionOne
Always show "Cannot find defect/issue with id: <valid id>
NA
Submit new Defect to Rally
Cannot attach screenshot into the defect
NA
Update existing defect to Rally
Always show "Cannot find defect/issue with id: <valid id>
NA
Create/Update defect to Rally
Rally defect description is blank
NA
Submit defect to JIRA
Cannot attach screenshots into the subtask
NA
Security
Fix Vulnerabilities
Sessions 4.3.1 OnDemand December 26th, 2019
Enhancements
For On Demand users only:
When submitting custom script generator plugin via Sessions' settings page, the plugin will be scanned for virus or malware before processing
When attaching file(s) to a session via Link Objects tab in session review page, the file will be scanned for virus or malware before processing
Sessions 4.2.9 OnDemand December 19th, 2019
Enhancements
Flood Element added to Script Generator
Flood Element is now available in the list of plugins within the Sessions Automated Script Generator. This enhancement allows Sessions users to generatea ready-to-run Flood Element scriptwhich can be downloaded as a TypeScript file and run directly on the Flood platform.
Submit Test Case from Sessions and Export to Excel
The Sessions PID is now a hyperlink and displays in the first column of the Excel workbook and displays before the Session Name. For additional information on submitting Test Cases to qTest Manager from Sessions, read this article.
Bug Fixes
Fixed "Cannot update defect to JIRA" issue
Fixed vulnerabilities
Sessions 4.2.8 OnDemand September, 2019
Enhancements
Session ID is now prepended to Session Title as a hyperlink in an exported document (PDF/Word) which allows to navigate user to the Session Review page.
Bug Fixes and Improvements
Ticket
Component
Description
29669
Sessions
It is no longer impossible to use the color panel to modify bubbles or fonts.
NA
Security
Fixed an issue with an unsecured cookie
NA
Submit Defect
Sessions cannot submit or update defect to Rally due to Rally UI changing in their new version. This has been fixed.
qTest Sessions 4.2.7 OnDemand July 2019
Security Enhancements
Defect Submission
Fixed security issue when submitting a defect from Sessions.
Performance Enhancements
Ticket 27715: Test Case Submission
qTest Sessions 4.2.7 offers an enhanced Test Case submission. Prior to this release, too many Test Modules in a specific qTest Project caused Sessions to not fully load. Therefore, the Test Cases would not all display in the Submit Test Case screen. In order to fix this issue, we applied lazy loading for Test Modules.
Bug Fixes and Improvements
Ticket
Component
Description
NA
Submit Defect
Sessions could not submit or updated defects to Rally, due to a Rally UI changed in the newer version. This has been fixed.
29669
Session Editor
You can now the use color panel to modify bubbles or font
28277
Installation
qtest 9.6.1 startup script failed to create sessions_961 database. This has been fixed.
Sessions 4.2.6 OnDemand June 14, 2019
Bug Fixes and Improvements
Ticket
Component
Description
NA
Sessions
Fixed and issue that caused 500 error when accessing Sessions from 9-box in Oregon region.
Sessions 4.2.5 OnDemand June 12, 2019
Bug Fixes and Improvements
Ticket
Component
Description
27715
Submit Test Case
Fixed performance issue when submitting Test Cases: Too many Test Modules in a specific qTest Project caused Sessions to not fully load and therefore, they would not all display in the Submit Test Case screen. In order to fix this issue, we applied lazy loading for Test Modules and we also had to compromise a functionality to search for Test Module by name.
NA
Security
Fixed security issue when submitting a defect from Sessions.
Known Issues
Sessions cannot submit or update defects to Rally, due to a Rally UI changed in the new version at the time if this release. We will provide the fix in the next release when we identify a resolution.
Sessions 4.2.4 OnDemand May 23, 2019
Bug Fixes and Improvements
Ticket
Component
Description
27313, 27483
Export
Fixed an issue with PDF exporting if the recorded sessions has some special characters.
NA
Security
There have been multiple security improvements.
Sessions 4.2.3 OnDemand January, 28 2019
Enhancements
Security improvements
Sessions 4.2.2 OnDemand January, 7 2019
Bug Fixes
Ticket 22067: You can now successfully submit images to Jira via qTest using the new Jira UI.
Ticket 20752: The spinning wheel seen when submitting test cases through Sessions is resolved.
Sessions 4.2.1 OnDemand September, 26 2018
Addition of Flood to the 9-Box
We are happy to announce that Floodhas been added as afeature to yourqTestsuite 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
AccessingFloodfrom your qTest suite is easy. To do so, follow these steps:
Select the9-box,and choose theFloodicon from the9-box menu.
You are redirected to theFloodsuite. Take note:
NewFloodusers will have a fresh account
ExistingFloodusers' accounts will be linked, and they will be taken to their already existingFlood accounts.
Projects will automatically be created withinFloodto mirror what users already have in qTest.
Note:There is an option to disconnect your qTest projects from yourFloodaccount. To do so, select theIntegrationoption in your user drop-down menu.
16094
The "Integrations" page displays. Here, you can see your qTest projects associated with yourFloodaccount. to disconnect, select the Disconnecticon.

Bug Fixes and Improvements
Ticket 20858:Certain characters are no longer lost in the export process. Previously, some characters were lost when exporting a document from qTest explorer.
Ticket 20041, 20042: Fixed depreciated scripts generated by C# Selenium Code Generator
Sessioons 4.2 Release Notes - May 28, 2018
Bug fixes
Ticket 17066: Notes made to recorded sessions are truncated and not exported.
Cause: the note length was limited to 100 characters only when exporting
Fix: increase the maximum length of a note to 255
Ticket reference 17315 : usinginternet Explorer, user is unable to choose Test Module without drop-down disappearing after every click made to collapse/uncollapse the structure.
Sessions 4.1.1 Release Notes - April 23, 2018
Bug fixes:
Explorer reverts back to first project after closing an execution. Ticket reference:
Sessions 4.1.0 Release Notes - January 08, 2018
Enhancements
New 9box icons
Provides users with instant access and knowledge to all QASymphony applications
You will know if you have access to a specific application or you need to upgrade your license
You will know if you have permission to access to a specific application or you need to ask your administrator for access
Bug fixes
Unable to export session to PDF: export session to PDF failed intermittently. This release fixed that issue.
View Article
Parameters 2.2.8 OnDemand Feb 03, 2020 Release Notes

Bug Fixes
Ticket #
Component
Description
NA
Parameters
User cannot search parameter created by another user in the same project from qTest. This has been fixed.
NA
Parameters
A user can see test case, which includes parameters, created by another user although they are in different project. This is caused by a bug in Parameters API. It has been fixed.
View Article
qTest Controller - Setting up qTest Insights with Postgres Read Replica 9.6.1 OnPremise

Overview
Thegoal for this process is to split complex reporting queries from the production database.
Prerequisite
Your qTest Manager and qTest Sessions database are on thesame Postgres database server.
This article assumes you have the knowledge to create a postgres read-replica server.
Note:These instructions are verified on qtestctl 6.3 (9.6.1).
Stop Insights
Linux (non-Docker)-Access the current directory "qtestctl" where you've installed your latest version of Insights.
systemctl stop qtest
Windows
C:\[path_to_qtestctl]>net stop qtest
Modify qtestctl/insights/build.gradle
Note:Remember to fill your replicated DB information into the placeholders.
Find keyword: qtestread.url=${qtestJdbcUrlWithoutCredential} (Line 239, in qTest version 9.6.1.)
Replace with qtestread.url=jdbc://postgresql://<YOUR READ REPLICA HOST>/${config['insights.postgres.db']}
qtestctl/insights/build.gradle
237 #--------INFO QTEST DATABASE READ -----------
238 qtestread.poolName=Qtest Read DB Pool
239qtestread.url=${qtestJdbcUrlWithoutCredential}
Find keyword: sessionread.url=${sessionJdbcUrlWithoutCredential} (Line 253, in qTest version 9.6.1.)
Replace with sessionread.url=jdbc://postgresql://<YOUR READ REPLICA HOST>/${config['sessions.postgres.db']}
qtestctl/insights/build.gradle
251#--------INFO SESSION DATABASE READ ---------
252sessionread.poolName=Session Read DB Pool
253sessionread.url=${sessionJdbcUrlWithoutCredential}
Find keyword: PostgreSQLServer="${config['insights.postgres.host']}" (Line 458, in qTest version 9.6.1.)
Replace with PostgreSQLServer="<YOUR READ REPLICA HOST>"
qtestctl/insights/build.gradle
455 CommandTimeOut="600"
456 PostgreSQLConnectionString="${logiConnectionStringqTest}"
457 ID="qTestMySQL"
458 PostgreSQLServer="${config['insights.postgres.host']}
Find keyword: PostgreSQLServer="${config['sessions.postgres.host']}" (Line 480, in qTest version 9.6.1.)
Replace with PostgreSQLServer="<YOUR READ REPLICA HOST>"
qtestctl/insights/build.gradle
477 CommandTimeOut="600"
478 ID="sessionDB"
479 PostgreSQLConnectionString="${logiConnectionStringSession}"
480 PostgreSQLServer="${config['sessions.postgres.host']}"
Restart qTest Service and Verify
Linux (non-Docker)
$ systemctl start qtest
Windows
C:\[path_to_qtestctl]>net start qtest
Access Insights from the 9-box in qTest Manager and verifyconnectivity.
View Article
Parameters2.2.4 Single Server Upgrade Guide for Docker

Overview
In this article, we provide step-by-step instructions to upgrade qTest Parameters from 2.2.4 on a singleCentOS/Ubuntu machineusing Docker. Please read the instructions thoroughlybeforestarting your installations.
The Q4 2019 OnPremise version did not have a version change for Parameters. Therefore, you will be upgrading from the previous 2.2.4 (with Docker deployment package 4.9) to the newest 2.2.4 (with Docker deployment package 4.10).
To request assistance withupgrading or obtain the self-upgrade links, complete the Upgrade Request Form.
Note:If you are performing a fresh install, use the OnPremise New Install Form and reference the OnPremise InstallGuide.
Before You Begin
qTest Parameters 2.2.4only workswith qTest Manager 9.7.1 or later.
Read the following:
Getting Started with Q4 2019 OnPremise
Recommended Hardware Requirement
Note:if you want to upgrade to qTest Parameters 2.2.4 on the same machine with other applications, e.g. qTest Manager, on Docker environment, follow this article Manager 9.7.1 to 9.8.3 Single Server Upgrade Guide for Docker
Shutdown your Previous Deployment
Open Terminal.
Access the directory where you extracted the previous docker deployment package 4.9, shut it down and create a backup.
$ ./shutdown
Configure qTest Applications
$ ./backup
Download DeploymentPackage
1. Downloaddocker-deployment-4.10 package.
$ wget <ENTER DOWNLOAD LINK HERE>
2.Extract the package
$ tar -zxf <DOWNLOADED PACKAGE FILE NAME>
3. Access to docker-deployment-4.10 directory
$ cd docker-deployment-4.10
Configure qTest Parameters
Choose one of the below options to configure qTest Parameters:
Copy configuration of all applications in your previous docker deployment to the /profiles directory of docker-deployment-4.9 package.
$ cp -r /path/to/docker-deployment-4.9/profiles/ .
Above command will copy the old configuration file at/docker-deployment-4.9/profiles/default.into/docker-deployment-4.10/profiles/default.in
Next, open the file at/path/to/docker-deployment-4.10/profiles/default.in, locate and change the version value to4.10, as below:
version = "4.10"
2. Another option is to use./configurecommand and specify parameters application that you want to configure.
For HTTP:
$ ./configure --parameters-url "http://<public IP address of current machine>:<qTest Parameters port>" --parameters-http "<qTest Parameters port>"--cluster "<IP of Postgres docker server>"
For HTTPS:
$ ./configure --ssl-key "<SSL Key>" --ssl-cert "<SSL Cert>" --ssl-ca "<SSL Ca>" --parameters-url "https://<public IP address of current machine>:<qTest Parameters https port>" --parameters-https "<qTest Parameters https port>"--cluster "<IP of Postgres docker server>"
Upgrade qTest Parameters
Execute thecommand below to upgrade qTest Parameters:
$ ./upgrade
Start Deployment Process
Next, start the deployment process by executingstartupscript which will download application images and qTest Parameters components to the Docker container.It may take a while to complete depending on your network connection.
$ ./startup
When it's done, you can access qTest Parameters and verify the new version.
Set up qTest Applications
Please follow this guide:to complete the remaining steps to activate your account.
Troubleshooting
If the steps above are not successful, perform the following steps to rollback to qTest Parameters 2.2.4 (previous version with Docker deployment package 4.9) (docker, images, parameters, parameterslb).
Restore backup data
# cd /path/to/docker-deployment-4.9
# ./restore
Start qTest Parameters 2.2.4
# ./startup
When therestore process is complete, contact Customer Support to troubleshoot the issue with upgrading qTest Parameters.
View Article
Parameters 2.2.4 OnPremise Single Server Install Guide for Docker

Overview
In this article, we provide step-by-step instructions to install qTest Parameters 2.2.4 on a CentOS/ Ubuntu machineusing Docker and connect to qTest Manager 9.8.3 on another machine.
Note:If you want to deploy qTest Parameters 2.2.4 andqTest Manager 9.8.3 on the same machine using Docker, read Manager 9.8.3 Single Server Installation Guide for Docker.
To request installation assistance or to obtain the links to self-install, please click here to fill out the New Install Form.
Note:If you are not performing a fresh install and are upgrading, use the Upgrade Request Form and reference the OnPremise Upgrades Guide.
Before You Begin
qTest Parameters 2.2.4 only works with qTest Manager 9.8.3 or later.
Docker 17.03has been installed. Follow these instructions to install Docker on your machine if you have not done so already.
For CentOS, you need to follow additional instructions to adjust Docker Storage Driver from overlay to device mapper.
For CentOS 7.X+ or Ubuntu 18.04 machines: Docker requires a 64-bit installation and your kernel must be at least 3.10
Read the following:
Getting Started with Q4 2019 OnPremise
Recommended Hardware Requirement
Download DeploymentPackage
1.Downloaddocker-deployment-4.10 package.
$ wget <ENTER DOWNLOAD LINK HERE>
2.Extractthe package.
$ tar -zxf <DOWNLOADED PACKAGE FILE NAME>
3.Accessthe docker-deployment directory.
$ cd docker-deployment
Configure the Applications
$ ./configure--apps"parameters parameterslb"
Configure qTest Applications
Configure to Deploy HTTP
If you are going to deploy qTest Parameters with HTTP.
$./configure --parameters-url"http://<public IP address of current machine>:<parameters port>"--parameters-http"<parameter port>” --cluster "<IP of Postgres docker server>"
Configure to Deploy HTTPS
If you are going to deploy qTest Parameters with HTTPS.
$ ./configure --ssl-key "<SSL Key>" --ssl-cert "<SSL Cert>" --ssl-ca "<SSL Ca>" --parameters-url"https://<public IP address of current machine>:<parameters https port>"--parameters-https"<parameters https port>"--cluster "<IP of Postgres docker server>"
Start the Deployment Process
$ ./startup
The script will download the application images to the Docker. It may take a couple of hours depending on your network connection.
Once the installation is complete, access to qTest Manager via your browser and start to configure qTest Manager and qTest Parameters.
Set up qTest Applications
Please follow this guide:to complete the remaining steps to activate your account.
View Article
Create Unified Functional Testing (UFT) Agent from Automation Host v 1.3.8 or Later

[Updated] This legacy UFT Agent type lacks a few features and flexibilities as compared to Universal Agent. So you are highly recommended to integrate your UFT project with Universal Agent instead.
Overview
In this article, we explain how to create and configure a Unified Functional Testing (UFT) Agent to a specific Automation Host machine.
IMPORTANT
To be able to launch your UFT tests, Automation Host must be running on a Windows Command Prompt with an active logged in Windows user. If automation host was installed as a Windows service, it cannot launch your UFT tests. Refer to this article for more detail about this limitation: IMPORTANT: Limitation of Automation Host service on Windows
The qTest Automation Host and your UFT tool must be installed on the same machine in order for the UFT Agent in Automation Host to kick off your UFT script execution
The UFT Agent in Automation Host works withUFT version less than or equal to 14.
The UFT Agent in Automation Host does not work with UFT version 14.04.
UFT Agent in Automation Host can only execute your UFT tests on Windows
If a failure occurs during testsubmission, the Failure Log will be included as a text file attachment in the Test Log details.
Prerequisites
Activate Automation Integration
Install and Register the Automation Host
In addition, make sure you map UFT execution status to qTest test automation execution status. The table below shows which UFT execution status is mapped to qTest automation execution status:
UFT Execution Status
qTest Execution Status
PASSED
Passed
FAILED
Failed
PASS
Passed
FAIL
Failed
SKIPPED
Incomplete
SKIP
Incomplete
WARNING
Incomplete
DONE
Passed
Passed
Passed
Failed
Failed
Pass
Passed
Fail
Failed
Skipped
Incomplete
Skip
Incomplete
Warning
Incomplete
Done
Passed
Screenshot below demonstrates how you do the mapping in Automation Settings of qTest Manager.
https://github.com/QASymphony/uft-sample
Step 1
Download the sample UFT automation project at https://github.com/QASymphony/uft-sample and save it to your local machine, e.g. D:\uft-sample
Step 2
Access to Automation Host UI then Click on+ Addbutton in the right corner of Agents list.
You will be presented with a New Agent dialog, as shown below.
Configure UFT Agent
Agent Name: name of the new agent, e.g. New Agent.This is the agent name that will be selected in qTest Manager Test Execution when scheduling Test Runs
qTest Manager Project: select a project that the new agent will be associated with, e.g. qConnect - Sample Project
Agent Type: Unified Functional Testing
Directory (required): specify the path to your UFT automation project in the source code that you have downloaded in step 1
IMPORTANT NOTES:your UFT project is located in the machine at <path to working directory>\<project name>\<file name>.usr. Conventionally,<project name>and<file name>must be the same. And you should put<path to working directory> to the Directory field,NOT<path to working directory>\<project name>
EXAMPLE: if you downloaded our sample atand saved it to your working directory at D:\uft-sample so your project structure will be as below:
D:\uft-sample: this is your working directory
D:\uft-sample\LoginFlights: this is your project folder
D:\uft-sample\LoginFlights\LoginFlights.usr: this is the path to your uft script file
Then your must putD:\uft-sampleto Directory field
Include (required): define patterns to scan for tests in the UFT automation project using ANT Style Pattern Matcher. Use a comma as a separator between patterns.
Exclude: define patterns to ignore tests when scanning for tests, again you can use ANT Style Pattern Matcher
HINT: ANT Style Pattern Matcher uses the following rules:
?matches one character.
*matches zero or more characters.
**matches zero or more 'directories' in a path.
Below is an example of UFT agent configuration
Click Save to finish creating UFT agent.
View Article
Create Unified Functional Testing (UFT) Agent from Launch

[Updated] This legacy UFT Agent type lacks a few features and flexibilities as compared to Universal Agent. So you are highly recommended to integrate your UFT project with Universal Agent instead.
In this article, we will walk you thru how to add a new Unified Functional Testing (UFT) Agent to a specific agent host from qTest Launch.
Note:follow this article to learn how to access to a specific host in qTest Launch in order to create a new Agent.
IMPORTANT
The qTest Automation Agent Host and UFT Integration tool must be installed on the same machine in order for the UFT agent type to kick off UFT scripts.
The integration tool works withUFT version less than or equal to 14.
Updated May 07, 2018:with the release of Automation Host 2.0.4, you can integrate automation host with UFT up to 14.03
UFT agent can only be executed on Windows.
Prerequisites
Activate Automation Integration
Install and Register the Automation Host
In addition, make sure you map UFT execution status to qTest test automation execution status. The table below shows which UFT execution status is mapped to qTest automation execution status:
UFT Execution Status
qTest Execution Status
PASSED
Passed
FAILED
Failed
PASS
Passed
FAIL
Failed
SKIPPED
Incomplete
SKIP
Incomplete
WARNING
Incomplete
DONE
Passed
Screenshot below shows how you do the mapping in Automation Settings of qTest Manager:
https://github.com/QASymphony/uft-sample
Step 1
Download the sample UFT automation project at https://github.com/QASymphony/uft-sample and save it to your local machine, e.g. D:\uft-sample
Step 2
Access to qTest Launch then locate a host that you want to create a new agent and open its detail dialog. On the host detail dialog, click on Agents tab then Click on + New Agent button. You will be presented with the New Agent dialog, as shown below:
General Information
Agent Name: name of the new agent, e.g. New Agent.This is the agent name that will be selected in qTest Manager Test Execution when scheduling Test Runs
qTest Manager Project: select a project that the new agent will be associated with, e.g. qConnect - Sample Project
Agent Type: Unified Functional Testing
Test Scripts
Directory (required): specify the path to your UFT automation project in the source code that you have downloaded in step 1
IMPORTANT NOTES:your UFT project is located in the machine at <path to working directory>\<project name>\<file name>.usr. Conventionally, <project name> and <file name> must be the same. And you should put<path to working directory> to the Directory field, NOT<path to working directory>\<project name>
EXAMPLE: if you downloaded our sample at and saved it to your working directory at D:\uft-sample so your project structure will be as below:
D:\uft-sample: this is your working directory
D:\uft-sample\LoginFlights: this is your project folder
D:\uft-sample\LoginFlights\LoginFlights.usr: this is the path to your uft script file
Then your must put D:\uft-sampleto Directory field
Include (required): define patterns to scan for tests in the UFT automation project using ANT Style Pattern Matcher. Use a comma as a separator between patterns.
Exclude: define patterns to ignore tests when scanning for tests, again you can use ANT Style Pattern Matcher
HINT: ANT Style Pattern Matcher uses the following rules:
?matches one character.
*matches zero or more characters.
**matches zero or more 'directories' in a path.
Test Scripts example on Windows
View Article
Using the API's to Link Test Cases and Requirements

Use Case
In the event you have a large number of test cases, linking them manually in the qTest Manager UI will take a considerable amount of time and energy. There comes a tipping point where using the API's becomes a more efficient way of linking your requirements with your test cases.
Tricentis recommends the following as Best Practice when linking Requirements to Test Cases, either from within the UI or via API. Note the maximum thresholds and associated impact. These numbers are generalized for providing context.
One Requirement linked to 2,500 Test Cases: expect difficult navigation within the UI at 2,500 and load time will increase.
One Requirement linked to 60,001 or more Test Cases: not recommended as the system will become unstable.
Overview
This article provides an example of linking your requirements with your test cases using the APIs. In this example, we will use the following:
3 API calls,
an online JSON to CSV converter, and
Postman's Runner
The online converter will format the APIs, from the standard JSON response format to a CSV format, which allows you to sort the data and use the relevant columns to create a spreadsheet. This spreadsheet can be imported via Postman’s Runner using environment variables to link your requirements to your test cases, going row by row through the final CSV file.
The majority of the work in this process is aligning your requirements with the associated test cases they need to linkto. If you have this information already available in an Excel document or some other form, the majority of the work is already done! If not, you can gather this information using the GET API's listed below.
Use GET API's
You will needto run both of the appropriate APIs to receive all of the Requirements and Requirement IDs, as well as all of the Test Cases and their corresponding Test Case IDs.
Use this API to get multiple Requirements:
https://api.qasymphony.com/#/requirement/getRequirements
Save your JSON results so you can access them later.
Example screenshot of the API call in Postman:
here
Use this API to get multiple Test Cases:
https://api.qasymphony.com/#/test-case/getTestCases
Save your JSON results so you can access them later.
Example screenshot of the API call in Postman:
Convert JSON API Responses to a CSV Format
You will need to complete these steps for both of the Requirements and Test Cases JSON responses.
Use the following online converter:
https://json-csv.com/

Edit CSV Files
You will now have two CSV files. They will look similar to the example below.
Use the "id" filter option found in the Data tab. This allows you to manually remove the filtered rows with a blank Requirement ID field.
Repeat this process for the Test Cases file as well.
Now the relevant columns are the "id" columns for both the Requirements and Test Cases CSV file.
Hint:Keep the name of the Requirement and Test Case in the files. This will make them more readable and user-friendly.
Create and name a new CSV file, which will be the file where you aggregate yourdata from your individual Requirements and Test Cases CSV files.
Copy the Requirement Name and Requirement ID column data and paste into the new CSV file.
Copy the Test Case Name and Test Case ID column data and paste into the new CSV file to the right of your Requirement columns.
Now, you need to align the Requirements with the associated Test Cases.
Hint:Add two blank columns in between your Requirement Name column and your Test Case ID column for 6 columns total. These two new columns allow you to easily cut/paste your Test Case ID and Test Case Name data to align the Requirements. Once you are all finished, you will have 4 columns with data like the image below.
Notice the column header names used in the example file above. These header names will be referenced in the final API call, "requirementid" and "testcaseid."
Create Links Between Objects
Use this API call to link your Requirements to your Test Cases.
https://api.qasymphony.com/#/object-link/linkArtifacts
Use environment variables to specify the Requirement ID and Test Case ID that will be substituted to the corresponding value in the CSV file
Note: You can read more about how this works here.
Set the API call up using Postman Runner module.
Note: You can read more about how this works .
Notice the environment variables in the image below, and the header tab is visible:
This image shows the body tab visible:
Save this API to a "collection."
Now you can select the "collection" you created within Postman's Collection Runner module.
In this example, we have called the collection "LinkRUnner." See example configuration image below.
Select your saved collection with the API for linking objects, environment variables, and also the combined CSV file. Once complete, select the Run button.
If successful, your screen should look similar to this screenshot:
View Requirements in qTest
Navigate to the Requirements module and check a Requirement in the Resources area. Your Test Cases should now be linked to your Requirements!
View Article
qTest Manager 9.9.2+ OnDemand Release Notes

Manager 9.9.3 January 16, 2020
Bug Fixes and Improvements
Ticket #
Component
Description
33565
Site Fields/
Test Case
Previously, users were unable to save a Test Case when System Site Fields, that were not marked as required fields, did not contain a value. This is now resolved.
34092
Test Execution Reports
Users adding attachments to Test Steps with a file name that contained a long dash were unable to open the Test Run Detail report with the Test Step Attachment column due to the long dash in the attachment name. This is now resolved.
33853
API
The Create Test Run and Update Test Run APIs would not allow users to set the Assignee field to empty "". This is now resolved.
34722
API
Some users experienced issues when using the GET Test Runs API when using a Release ID that contained more than 32k Test Runs.
34703
API
When using the Submit Automation Test Logs API some users experiencing intermittent failure issues. This is fixed.
34525
Test Design
An issue is now fixed that caused performance issues when performing the following actions that included Called Test Cases:
Loading a Test Case with called Test Case(s) in Test Step.
Loading a Test Run created from a Test Case with Called Test Case(s) in Test Step.
34865
Test Design
Some users were unable to search for a Requirement by PID but able to search for the Requirement by name when attempting to link a Requirement to a Test Case from within Test Design. This has been resolved.
Manager 9.9.2 January 02, 2020
Data Query Results Updated
When running Data Query results through Test Design and the query results return with:
Less than 10k test cases, you can sort by any system or custom field.
More than or equal to 10k test cases, you can sort the Query Result grid by mostsystem fields.
More than or equal to 10k test cases, you cannot sort by any custom field and will receive a new warning message:
"Sorting is disabled for more than 10k objects. Please revise the query to reduce the number of objects."
The Query Result will automatically be sorted by the currently sorted column.
Sorting occurs at the top of the column of the data query results.
Known Limitation
Due to the complexity of the data query when there are more than 10k test cases, the following system fields cannot be sorted:
Requirements
AssignTo
Attachments
TestStep
Subscriber
Bug Fixes and Improvements
Ticket #
Component
Description
31099
APIs
When users retrieve Test Cases using a query based on a date, the response is paginated but not consistently or predictably. This has been fixed.
32567
Test Design
When copying/pasting text into the precondition field of a Test Case, the history tab does not display the correct change. It displays a change was made to both the Pre-Condition field and the Description field. However, there was no change made to the Description field. This has been fixed.
33792
TestPad
When users entered data in the following ways, Actual Results were not saving correctly:
Copy/Paste from Actual Results in another step of the same test run, using right-click to select "Copy" and "Paste as plain text"
Copy/Paste from Notepad, using right-click to select "Copy" and "Paste"
This has been fixed.
34900
Email Notifications
The verbiage for theProject Admin email that customers receive when they are made the Project Admin for a project has been updated.
"All permissions on this project has been granted to you as a result."
to:
"All permissions on this project have been granted to you as a result."
View Article
qTest Scenario with OAuth Configuration Guide

Overview
As of qTest Scenario 3.3.0 OD, Scenario can now be configured to work with OAuth for either JIRA Server, or JIRA Data Center. This article outlines how to set up this configuration.
Prerequisites
You need to have generated a Client and Server key pair.
You can find the instructions below.
The account that setup Scenario must have the Global Administration permission.
Enable JIRA Connection in qTest to use OAuth
Before configuring Scenario to work with OAuth, your qTest and JIRA Integration should also be using OAuth. If you have already configured your JIRA Connection to use OAuth, you can proceed to the next section. If not, follow these instructions to establish your qTest and JIRA Integration with OAuth.
Important! If your qTest Project is already using a JIRA Connection, do not create a new connection, simply edit your existing connection.
New JIRA Integrated Project to use with OAuth
JIRA Server/Data Center
Edit an Existing JIRA Integrated Project to use with OAuth.
JIRA Server/Data Center
Please note that the consumer key must be entered exactly in this format: qTest
Obtain the JIRA Access Token from within qTest
In qTest, Project Admins have the ability to view/copy the JIRA access token that is associated with JIRA integrated Projects.
Navigate to theqTest project, and select the gear icon in the toolbar.
SelectIntegration Settings. The "Configure Integrations" page displays.
SelectJIRAin the External Systems panel.The "Configure Integration: JIRA" page displays.
In the Connection Name column, select theblue hyperlink of your JIRA Integration name.
TheAdd Jira Connectiondialog opens.
A "Show Password" checkbox is available and is not selected by default. Once selected, Project Admins can view and copy/paste the access token which will be used in following steps.
Note: When closing the Add Connection dialogue, the checkbox resets to the default and the password/token will be hidden again.
Configure Scenario to Work with OAuth
From your JIRA instance, selectJira Systemin theGearbutton () beside the account image.
TheAdministratorpage updates, select theAdd-onstab.
ChooseManage add-onsat the left navigation panel.
SelectqTest Scenario - BDD for Jiraadd-on then chooseConfigure.
ThePlugin Configurationpage ofqTest Scenariowill be loaded, then scroll down to "Basic Authentication" and "Jira OAuth" sections.
Configure access token (required): enter"oauth"in the username text box. In the password field, enter the access token that youretrieved from your qTest Project integrated with JIRA.
Configure OAuth private key (required): copy the content of the Private key file then paste to the corresponding text box. If the private key has a passphrase, then type it to thePassphrasetext box.Note: we only support key decryption for pkcs8 format.
Select Save Configuration.
View Article
Parameters 2.2.8 On Premise February 2020 Release Notes

Enhancements
Added new API to search for multiple parameters in one request.
Bug Fixes
Ticket #
Component
Description
34100
Test Case
When a user edits a parameter, including associating the parameter to the projects they are a member of, the projects that were previously assigned to the parameter will be gone when the Parameter is saved. This caused the other user who is the member of the gone projects to be unable to use the parameter anymore. This has been fixed.
NA
Security
Fixed vulnerability issues
NA
Parameters
User cannot search parameter created by another user in the same project from qTest. This has been fixed.
NA
Parameters
A user can see test case, which includes parameters, created by another user although they are in different project. It has been fixed.
View Article
Introduction to qTest Objects

Overview
qTestObjects arecomponents you create within your qTest environment. These objects can be edited, deleted, copied, or cut on the system tree so that qTest remains both highly customizable and user-friendly.
DefectsSection of the Help Guide.
Objects in Test Plan
Test Plan is the default homepage for each qTest Project because you can view the general project overview. Many of the fields you see here populate with data that you enter when creating the qTest Project. The Test Plan displays the following information:
Name
Start and End Dates
Description
Project Timeline
Key Facts
Associated Releases
Note: To view Releases, select the arrow on the "Release" drop-down menu.
In theTest Plan, you can create and edittwo qTest Objects:
Release:aninternal or external distribution of software once a development loop within a product's lifestyle has been completed.
Build:includes data on the relevant testing plan, tests conducted, test results, and defect records. A release can have multiple Builds that you can define as a Milestone. An example would be a build for UAT and another build for your Beta release.
If your team uses an external ALM such as JIRA, Rally, or VersionOne, the release plan was likelyalready established in that external ALM. If that is the case, feel free to use the Test Plan as a lightweight feature to create the releases as “containers” to build actual plans that you will see inTest Execution.
For step by step instructions on how to use the Test Plan, refer to the Test Plan for Releases and Builds article.
Objects in Requirements
Requirements in qTest are synonymous with a user story/issue, which describe in detail what needs to happen for the software you are developingto meet its objectives. You will link your Test Cases to your Requirements.
The structure you create in Requirements will be mirrored in Test Design.
In qTest, you can group yourRequirements together andnest them inside ofModules. This allows you to createhierarchical groupings based on the product’s structure and functionality that has one common objective, such as a sprint or epic. You can even have multiple levels of Modules to group like items together, such as requirements worked by different teams within a sprint.
To manage qTestRequirements,refer to the article Create, Edit, Copy, and Delete Requirements.
Example: This example shows a top-level module, named Imported from JIRA, and in that module are three nested modules named EBJ1 Sprint 3, Medium (P3) and EBJ1 Sprint 4. Within the Medium (P3) module there are 4 requirements. This project's Jira Requirement integration settings are organized to bring in requirements in a nested structured that contains Sprint and Priority.
Objects in Test Design
Test Design is also comprised of Modules but includes another qTest Object: theTest Case.
ATest Casedescribes in detail what needs to be tested to meet quality objectives and will detail steps, including actions, scenarios, and the expected results.
Find Test Cases in the Navigation Panel housed withinTest Design Modules. Your Test Design Modules will be a logical grouping of similar Test Cases.
Refer to the Linking Test Cases to Requirements topic for additional information.
Example:Test Cases for a login screen for different types of users.
Objects in Test Execution
Test Execution contains the most qTest Objects. Here, users can manage:
Releases
Test Cycles: the testing of a release can be broken into a number of shorter cycles and are assigned to an overall release, or you can assign them to a build within a release. ATest Cycleis a container that shows a high-level summary of its underlyingTest Suites and TestRuns, including the execution results of these tests and any defects found. Within a given release, you may need to execute many types of tests such as new features and bug fixes. For this reason, you may have more than oneTest Cyclewithin the release or even multi-levelTest Cycles, which will be beneficial for organizing and reporting. A possible example of multi-level Test Cycles would be for new features that need to be tested on a browser version and a mobile version of your software.
Test Suites: a set of the same type of test cases, such as functional tests, non-functional tests, sanity tests, or possibly even regression tests. Test suites are focused on addressing specific test objectives. For example, tests in a test suite may be grouped to validate specific components of your software or to test given levels of integration.ATest Suitecan be regarded as the lowest level container to organize test runs.
Test Runs:an uninterrupted period of time spent in executing a test case.
These Objects are in the left Navigation Panel.
For more information on usingTest Execution,refer to the Test Execution section of the Help Guide.
Defects
qTest Manager also tracks objects calledDefects. Defectsare any flaws that cause a component or system to fail to behave/function as expected.
For more information onDefectstracking, refer to the
View Article
Manager 9.9.1 OnDemand Release Notes

Overview
We are happy to announce qTest Manager 9.9.1 OnDemand. This release has many exciting updates, including several Feature Requests submitted by customers!
Here are a few release highlights:
Virus Scanning for attachments and imported files
New Rally Integration fields
additional VersionOne Integration field
prevent the approval of Test Cases with no linked Requirements
Enhancements
Ability to Prevent the Approval of Test Cases Without Linked Requirements
Project Admins can now prevent users from approving Test Cases that do not include linked Requirements. This features enablement is on a per-project basis, and applies to the approval of newly created Test Cases, or when modifyingproperties or Test Steps ofexisting Test Cases via the UI or API.
By default, this new feature is OFF, but Project Admins can enable it from the Project Settings>Test Case Settings page.
If enabled, ensure your Project Users have the following permissions:
Edit Test Cases
View Requirements
Approve Test Cases
Once enabled, users must link Requirements to the below scenarios of Test Cases before approval:
newly created Test Cases
modified Test Steps of an existing Test Cases
modified Properties of an existing Test Case
Retrieving Requirements from VersionOne
Enablement of this feature applies to the following:
Approval of single Test Cases via UI
Batch Approve
When users Batch Approve Test Cases that have no linked Requirements, qTest confirms the Test Case versions and they can only select MAJOR versions of Test Cases to execute.
APIs:
Approve Test Case
Submit multiple Test Results
Submitting multiple test logs in one API request, and create Test Cases and Test Runs in a hierarchical structure
Submit an Automation Test Log
Submit a Manual Test Log
Exceptional Users Permission
Project Admins can designate "exceptional users" who can approve Test Cases without linked Requirements even when this feature is enabled. This is managed within the Test Case Settings page.
Rally Integration Enhancement
The Rally Integration has been enhanced to display all system and custom fields from Rally that are configured within the Projects Integration Settings. Previously, the Rally fields were hard-coded. This enhancement applies to the following:
Defect Mapping
Requirement Mapping
Project Admins with the Manage Integration Settings can map the newly available fields.
Virus Scanning on OD S3 Attachments
UI
All attachments will be scanned for viruses and malware after being uploaded
All existing attachments will also be scanned
After being uploaded, a file can have one of followings statuses:
Scanning: the file is in queue for scanning
Clean: the file has been scanned and is not virus/malware infected
Infected: the file has been scanned and is virus/malware infected
Scanning Failed: for some reason, our scanning service is not available at the time and your file cannot be scanned for virus/malware
The status of a file is appended the file name so you know its scanning status (if nothing is appended to the file name, that means it is “Clean”)
You are not allowed to preview attachments which are “Scanning”, “Scanning Failed” or “Infected”
You can download attachments which are “Scanning” or “Scanning Failed” “at your own risk
You are not allowed to download attachments which are “Infected”
APIs
We updated the following API endpoint to download an attachment so it responds consistently with the UI:
GET /api/v3/projects/{projectId}/{objectType}/{objectId}/attachments/{attachmentId}
Given an attachment which is “Scanning” or “Scanning Failed”, you can download the file by specifying this URL parameter: forceDownload=true (eg: GET {qTestURL}/api/v3/projects/{projectId}/{objectType}/{objectId}/attachments/{attachmentId}?forceDownload=true)
If you make an API call to the endpoint and omit the parameter, its default value is false and the API will return code 400 with following message: "The attachment has not been scanned for malware/virus successfully."
You are not allowed to download “Infected” attachments. If you try to download an “Infected” file, the API will return code 400 with following message: "The attachment is virus infected."
Import multiple files Import Requirements, Test Cases and Defects
qTest will only proceed to import data from your uploaded files if all of the import files are “Clean”
You will need to wait until your import files are scanned successfully and all of them are found “Clean” in order to proceed
If some of your import files are “Infected” or “Scanning Failed”, you will need to manually remove them in order to proceed
For some reason, if our scanning service is not available when you are doing the import, please try again later
Import or upload single file
For following existing functions, you can upload and import one file at a time:
User Import
Import Automation Test Runs
Upload metadata file to set up SSO
Upload private key for Jira integration
Upload private key
If the file is “Clean”, you can proceed with the import or save your uploaded file
If the file is “Infected” or “Scanning Failed”, you cannot proceed with the import nor save your uploaded file
If the scanning service is not available at the time, please try again later
Project Field now available in VersionOne Requirement Integration
The VersionOne Project field is now included as an option in the V1 Requirement Integration Settings. Additionally, you can configure the V1 Project field to organize your "Imported from V1" folder using Field 1 or Field 2 of the Requirement Integration.
This organization option is then visible on the Requirements tab within qTest once you save your Integration Settings changes. This allows you to display VersionOne Project information in each Requirement that is synced to qTest Manager.
Project Admins with the ability to configure Version One's Integration Settings can now:
Select the Refresh Fields Settings button to get the latest field setting from VersionOne including the VersionOne Project field.
Organize imported VersionOne's requirements with theVersionOne Project field
Activate the VersionOne Project field to display in the "V1 Properties-Read Only" section of the Requirement in qTest.
Read the section for additional information on how to use the VersionOne Requirement Integration.
Tricentis Analytics User Permissions in qTest
In preparation for the future release of Tricentis Analytics OnDemand, we have included new User Group permissions associated with Tricentis Analytics. Additionally, the User API's of GET, Update, and Invite include these new permissions.
TA Viewer:Users who can view reports in Tricentis Analytics.
TA Designer:Users who can define reports in Tricentis Analytics.
TA Administrator:Users who can manage data from all qTest projects in Tricentis Analytics.
Bug Fixes and Improvements
JIRA Integration Update
To provide backward compatibility with JIRA server versions older than 7.6, a new configurable property is introduced:
integration.jira.testConnection.legacyEndpoint.clients=<CLIENT_ID1>,<CLIENT_ID2>
This property will either be null or contain Client IDs separated by a comma, for clients who are using JIRA server versions older than 7.6.
When testing the JIRA connection, if the current client id matches with the values contained in this property, it will send a request to the old endpoint:/mypermissions
Otherwise, it uses new endpoint:/permissionscheme
Ticket #
Component
Description
31488, 34815, 35258
Test Design
Users were experiencing issues adding rows to existing test cases and that data not saving in those rows. This has been fixed.
33555, 33895, 34459, 34460
Test Design
Users use Ctrl+B or the Bold button to bold sections of text in Test Design. Turning bold off caused text to be added to the left of the cursor instead of the right of the cursor. This has been fixed.
33562
Test Design
Users were unable to see the bottom of the page in Chrome on a second monitor when scrolling up and down. This has been fixed.
33720
Test Design
When using the Ctrl+S hotkey to save data in Test Design, some users but experienced an error that would wipe the data instead of saving. This has been fixed.
33880
Test Design
When users exported Test Cases from Excel, the format changed and added an extra line between rows. This has been fixed.
34803
Test Design
Users were experience issues where Text Copy/Paste is greyed out when in Editor mode in the Test Steps. This has been fixed.
34857
API integration
When using the API to add a new release type using Fix Versions for a Jira Integration, users were getting an error. This has been fixed.
34569
Test Design
Users were experiencing issues using the Chrome spellcheck extension within Test Design. This has been fixed.
NA
Security
Default web server 500 error page leaked version information. This is now resolved.
View Article
Silent Install Desktop Explorer with MSI package

Overview
In this article, we will provide the IT administrator with detailed instructions on how to silently install qTest Explorer to multiple machines in an organization.
System Requirements
1. A Windows Server with Group Policy Management installed
2. For client machines
OS: Windows 7/8/10 with .NET Framework 4.6 installed
RAM: at least 2GB
Hard disk space: at least 500MB available
Step by step guide
MSI Installation Package
The latest qTest Explorer MSI installation package can be downloaded HERE.After downloading, copy the file to a network share folder that can be accessed by client machines that need qTest Explorer installed.
Setting up silent installation process
Step 1: Create installation script file
Open a text editor and create a new text file. Copy and pass the script below to the content of the file.
msiexec.exe /i "[\\path\to\MSI package]" ALLUSERS=1 /m MSISPQJA /qn /l*v "C:\explorer_install.log" APPLICATIONFOLDER="\%PROGRAMFILES(X86)\%\QASymphony\qTest eXplorer Integrated" LAUNCHAPPONEXIT=1 INSTALLDESKTOPSHORTCUT=1 ARPNOMODIFY=1
Note: make sure you change the [\\path\to\MSI package] portion of the script withthe real UNC path to the downloaded MSI package
Below is an example of the script:
msiexec.exe /i "\\192.168.74.81\share\qTestExplorer.msi" ALLUSERS=1 /m MSISPQJA /qn /l*v "C:\explorer_install.log" APPLICATIONFOLDER="\%PROGRAMFILES(X86)\%\QASymphony\qTest eXplorer Integrated" LAUNCHAPPONEXIT=1 INSTALLDESKTOPSHORTCUT=1 ARPNOMODIFY=1
Save the script file and name it install.cmd. Make sure you put this file in a network share folder that can be accessed from client machines.
Step 2: Configure Startup script using Group Policy Management console
From Windows Server, open the 'Group Policy Management' console.
From the 'Group Policy Management' console, navigate to your domain, right click on the domain name and choose 'Create a GPO in this domain, and Link it here...' item from the pop-up menu.
The 'New GPO' dialog is now displayed. Enter eXplorerDeploymentinto the 'Name' text box and click 'OK.' This Group Policy Object will be created under the selected domain.
Right click on the new Group Policy Object named eXplorerDeployment and choose 'Edit...' from the context menu.
From the 'Group Policy Management Editor', browse to Computer Configuration> Policies > Windows Settings then select Scripts (Startup/Shutdown). On the right pane, right click on Startup item and choose Properties.
From 'Startup Properties' window, click 'Add...' button
From 'Add a Script' dialog, click 'Browse...' button, and select the file install.cmd created in Step 1. Make sure you change file path portion to UNC, as shown in the example below, then click 'OK.'
Step 3: Verify
Start a client machine in your network and verify that eXplorer is installed after logging in to the system.
View Article
Upgrade Insights Logi License for OnPremise before 9.9.1 (Insights version prior to 1.21.14)

If you are an OnPremise customer and using a version of Insights that was released prior to Insights 1.21.14 (Manager 9.9.1),you will need to upgrade your Logi Analytics license.Logi Analytics is qTest Insight's third-party reporting application.
Insights is built on the Logi Platform and the associated Logi license will expireon March 22nd, 2020. Therefore, OnPremise customers who are using a version of Insights that was installed or upgraded before 1.21.14 (Manager 9.9.1) will be required to either:
Upgrade Insights to 1.21.4 (Manager 9.9.1).
OR
Follow this guide to update the Logi license for your currently installed Insights version.
Note: Follow the instructions below based on your operating system and associated version numbers. We have supplied the OnPremise Insights version and its associated Manager version for clarity.
Docker
Insights OnPremise before 1.15.3 (Manager 9.0)
An OnPremise Docker customer that is using any version of Insights earlier than 1.15.3 or Manager 9.0 will need to upgrade the Logi license using the following steps.
Open docker-deployment-x.x/bin/Insights/_Settings.lgx, line 82.
Change the value of OemDistributionLicense to the following:
&lt;LicenseFile Version=&quot;12&quot;&gt;&lt;Product Name=
&quot;Logi Info Server v.12&quot; /&gt;&lt;Customer Name=&quot;QASymphony_InfoServer&quot;
Email=&quot;[email protected]&quot; Contact=&quot;Chung Nguyen&quot; /&gt;&lt;License
ComputerName=&quot;LOGIOEM&quot; CountUniqueUsers=&quot;False&quot; ExpirationDate=&quot;
2022-03-21&quot; LicenseKey=&quot;120102_000029_QASymphony InfoServer_20220321&quot; AssignmentKey=
&quot;6B82-43A3E-67DB-4AFD9-1CB7-01F90&quot; /&gt;&lt;/LicenseFile&gt;
Note: Make sure to keep all of the encoding.
Save the file and restart the program.
Insights OnPremise version between 1.15.3 (Manager 9.0) and 1.21.14 (Manager 9.9.1)
An OnPremise Docker customer that is using any version of Insights between 1.15.3 (Manager 9.0) and 1.21.14 (Manager 9.9.1) will need to upgrade the Logi license using the following steps.
Download the file post-start.in and save it at docker-deployment-x.x/insights.
Restart the program.
Windows
Insights OnPremise 1.2 (Manager 8.1.5)
An OnPremise Windows customer that is using Insights version 1.2 or Manager 8.1.5will need to upgrade the Logi license following these steps:
Open qTest Insights 2\local\Insights\webapps\ROOT\_Definitions\_Settings.lgx, line 10.
Change the value of OemDistributionLicense to the following:
&lt;LicenseFile Version=&quot;12&quot;&gt;&lt;Product Name=
&quot;Logi Info Server v.12&quot; /&gt;&lt;Customer Name=&quot;QASymphony_InfoServer&quot;
Email=&quot;[email protected]&quot; Contact=&quot;Chung Nguyen&quot; /&gt;&lt;License
ComputerName=&quot;LOGIOEM&quot; CountUniqueUsers=&quot;False&quot; ExpirationDate=&quot;2022-03-21&quot;
LicenseKey=&quot;120102_000029_QASymphony InfoServer_20220321&quot; AssignmentKey=
&quot;6B82-43A3E-67DB-4AFD9-1CB7-01F90&quot; /&gt;&lt;/LicenseFile&gt;
Note: Make sure to keep all of the encoding.
Save the file and restart the program.
Insights OP version between 1.2 (Manager 8.1.5) and 1.21.14 (Manager 9.9.1)
An OnPremise customer that is usingany version of Insights between 1.2 (Manager 8.1.5) and 1.21.14(Manager 9.9.1) will need to upgrade the Logi license using the following steps.
Open qtestctl/insights/build.gradle.
Change the value of OemDistributionLicense to the following:
&lt;LicenseFile Version=&quot;12&quot;&gt;&lt;Product Name=&quot;
Logi Info Server v.12&quot; /&gt;&lt;Customer Name=&quot;QASymphony_InfoServer&quot;
Email=&quot;[email protected]&quot; Contact=&quot;Chung Nguyen&quot; /&gt;&lt;License
ComputerName=&quot;LOGIOEM&quot; CountUniqueUsers=&quot;False&quot; ExpirationDate=&quot;2022-03-21&quot;
LicenseKey=&quot;120102_000029_QASymphony InfoServer_20220321&quot; AssignmentKey=
&quot;6B82-43A3E-67DB-4AFD9-1CB7-01F90&quot; /&gt;&lt;/LicenseFile&gt;
Note: Make sure to keep all of the encoding.
Save the file and restart qtestctl.
Linux
Insights OP between 1.11.2 or 1.12.2 (Manager 8.4.4 or 8.7.3) and 1.21.14 (Manager 9.9.1)
An OnPremise customer that is using any version of Insights version between 1.11.2 or 1.12.2 (Manager 8.4.4 or 8.7.3) and 1.21.14 (Manager 9.9.1) will need to upgrade the Logi license using the following steps.
Open qtestctl/insights/build.gradle.
Change the value of OemDistributionLicense to the following:
&lt;LicenseFile Version=&quot;12&quot;&gt;&lt;Product Name=&quot;
Logi Info Server v.12&quot; /&gt;&lt;Customer Name=&quot;QASymphony_InfoServer&quot;
Email=&quot;[email protected]&quot; Contact=&quot;Chung Nguyen&quot; /&gt;&lt;License
ComputerName=&quot;LOGIOEM&quot; CountUniqueUsers=&quot;False&quot; ExpirationDate=&quot;2022-03-21&quot;
LicenseKey=&quot;120102_000029_QASymphony InfoServer_20220321&quot; AssignmentKey=
&quot;6B82-43A3E-67DB-4AFD9-1CB7-01F90&quot; /&gt;&lt;/LicenseFile&gt;
Note: Make sure to keep all of the encoding.
Save the file and restart qtestctl.
Before upgrading Logi License:
After upgrading Logi License:
View Article
Manager 9.7.1+ Release Notes

Manager 9.7.11 Sept 22, 2019
Bug Fixes
Ticket
Component
Description
31469
qTest API
There are no longer any issues related to inviting qTest users with SSO authentication via API's.
27637
JIRA Integration
qTest no longer allows linked non-bug JIRA issues to be created as Defects in qTest. Previously, there was an issue where users were able to link defects to any JIRA issue type regardless of what was configured in their Defect Integration settings. For instance, although Bug may have been the only JIRA issue type configured in the Defect Integration settings, users were still able to link to Task, Story, Epic, etc.
This behavior has since been corrected and only JIRA issues types that are configured in the Integration Settings can be linked/searched as a Defect in qTest.
30837
Test Execution
There is no longer an incomplete scrolling issue within the Test Execution tab.
31928
qTest API
The Search Comment API's pagination is no longer broken.
Manager 9.7.10 Sept 11, 2019
Bug Fixes
Ticket #
Component
Description
31291
JIRA Plugin
If a user renamed a FixVersion in JIRA, then both FixVersions would display in the Release drop-down within the Test Execution iFrame of the qTest JIRA Plugin. This is now resolved.
29876
API
The Search API did not return results as expected when test steps contained HTML characters. This is fixed.
Manager 9.7.9 Sept 3, 2019
The qTest Manager SSO Service Provider certificate has been updated. If you are using SSO to login to qTest, you must follow the instructions in this guide before September 9, 2019 to update the SP metadata in your configured IdP.
In the event, you are unable to update your IdP before September 9, 2019, follow these instructions to bulk update your users to authenticate via qTest internal (username/password) from your current SSO authentication.
If you configured your IDP topull SP metadata automatically, you will not be impacted by the certificate update. No action is required on your part to update your SSO IdP.
Manager 9.7.8 Aug 28, 2019
Bug Fixes
Ticket #
Component
Description
31921
31878
Audit Log
When attempting to load and export the Audit Log in the Security tab no action would occur. This is now resolved.
27463
Test Log APIs
When sending a POST request to the qTest V3 API /auto-test-logs URI https://api.qasymphony.com/#/test-log/submitAutomationLog the HTTP response for qTest 9.3.0 has differently formatted self relationship link URLs than version 9.5.3. This is resolved.
Manager 9.7.7 Aug 23, 2019
Bug Fixes
Ticket #
Component
Description
27965
Defect Summary
An intermittent issue occurred when attempting to view the Defect Summary of a Release. If there were more than 50 defects in the list, the details would sometimes not appear. This is now resolved.
31179
Defect API
Previously, Defect API pagination would not return the expected number of defects. This is fixed.
31270, 31488
31501, 31451
30734, 31548
31482, 31584
31525, 31295
31769, 31692
Test Steps
When making amendments to Test Steps within Test Design, some users experienced not being able to save these Test Step changes when using Chrome v76. This is now fixed.
Manager 9.7.5 Aug 8, 2019
Bug Fixes
Ticket #
Component
Description
29892
API
Previously, Site Field names were missing from the Test Suite API response. This is now resolved.
29551
SSO
SSO now works as expected when using with an existing SSO session. Previously, some users experienced a lock-out, after attempting multiple logins with username/password authentication. This occurred when users were not notified in advance to utilize organizational SSO enablement.
Manager 9.7.4 Aug 2, 2019
Bug Fixes
Ticket #
Component
Description
27884
Site fields
There is no longer an issue with adding a new site field to an existing template.
30306
Test Runs
Users can now run Test Runs regardless of whether those Test Runs are shared and derived from a Test Case in a project that the user does not have permission to access.
29082
Site Fields Template
When viewing a Site Field Template, and navigating between the object types, not all fields displayed. This is now fixed.
Manager 9.7.3 July 30, 2019
Enhancements
Improved Usability With Jira Requirements and Release Progress Dialogues
Users are now able to close the "Retrieve Jira Requirements" and "Retrieve Jira Release Progress" dialogues. The Jira Issues Objects will still synch to qTest Manager in the background.
Improvements in Test Run Detail Reporting
In the Test Run dialog, users are able to add attachments to their Test Step Logs. These attachments will be included exported Excel files.
Bug Fixes
Ticket #
Component
Description
29977
Integration Settings
Users received an "Error" message when adding requirement types in their Integration Settings. This has now been resolved.
Manager 9.7.2-1 July 22, 2019
Bug Fixes
Ticket #
Component
Description
30714
30713
30711
30710
30708
30707
30706
30705
30704
30703
Resources page
We have downgraded OAuth2 for Spring Security to version 2.0.7. This remediates the issue with users receiving an Oops error when accessing the Resources page.
Manager 9.7.2 July 22, 2019
New Features and Enhancements
Next-Gen Jira Compatibility
You can now retrieveSprintsfrom Next-Gen Jira Projects and have them populate as Releases in qTest Manager.
Bug Fixes
Ticket #
Component
Description
30182
Login
qTest now accepts email addresses with the ' character.
View Article
Insights 1.21.1+ OnDemand Release Notes

Insights 1.21.14 OD January 14, 2020
Bug Fixes
Ticket
Component
Description
35977, 35979
Shared Reports
An issue has been fixed for shared Insights reports that produced a bookmark error.
Insights 1.21.13 ODDecember 19, 2019
Bug Fixes
Ticket
Component
Description
30227
Saved Reports/Schedule
An issue has been fixed in which scheduled Insights reports did not run properly.
32800
Saved Report/Send Now,Saved Reports/Schedule
An issue has been fixed in which HTML format reports sent by email were displaying empty.
32868
An issue has been fixed in which saved personal Insights reports could not be accessed.
33049
Explore Data/Defects (Linked),Settings/Jira Defect Custom Fields
The Due Date Jira field now appears correctly in Insights reports.
33217
Coverage Analysis
The Coverage table is now showing the filtered requirements according to the global filter.
33317
Dashboards
An issue has been fixed in which multi-selection custom site fields were taking too long to load.
Insights 1.21.12 OD September 25, 2019
Bug Fixes
Ticket
Component
Description
27575
Explore Data
Changing the "Max Rows" value on a report from the default value of 500 to another selection no longer results in data not loading properly.
30844
Rapid Dashboard
There is no longer a problem with Rapid Dashboards causing them to automatically update to an untitled dashboard without any charts.
30268
Saved Reports/ Schedule
Dates in scheduled PDF reports are now successfully kept up to date.
31609
Embed Feature/ Explore Data
There is no longer an issue that causes an Insights embed script to fail to generate chart images.
32048
Explore Data/ Test Run
An issue has been fixed that caused Custom Field Data to not display properly in the Manager Combined Report.
Insights 1.21.11 OD September 8th, 2019
Bug Fixes
Ticket
Component
Description
26769
Dashboards
The data segregation works normally within Insights Dashboards.
27081
Rapid Dashboard
There is no longer an issue with the Rapid Dashboard URL getting created.
30820
Explore Data/ Test Run
The planned time for Test Runs with a status of "Unexecuted" now displays correct information.
31042
Dashboards
Data now displays correctly in the Automation Execution Dashboard.
31081
Quality Analysis
Information concerning configuration fields now displays correctly in the Quality Analysis Report.
31339
Explore Data/ Defects (Linked), Explore Data/ Test Run
There are no longer discrepancies within the the Explore Data Defects (Linked) and Test Run Reports.
Insights 1.21.10 OD August 7th, 2019
Performance Enhancements
Ticket 29090: We have optimized the execution time of the Test Run Explore Data report.
Bug Fixes
Ticket
Component
Description
26773
Export
There is no longer an issue with exporting reports in the Explore Data Test Run report.
28125, 30844, 26664
Dashboard
There is no longer an issue with Dashboards disappearing.
30046
Custom Charts, Embed Feature, Saved Reports
We have resolved an issue with inconsistent Insights Graph Data due to timezone issues.
28161
Reports
Planned Time is now present on Insights Reports when added on Test Execution.
28874
Requirements Data
There is no longer a JSON parse error while generating Requirements Test Run Coverage
29445
Dashboards
When renaming dashboards in "Manage Dashboard," the new name can now contain spaces.
29535
Embed Feature
There is no longer an issue with embedded dashboards being blank on the initial load.
Insights 1.21.9 OD July 8th, 2019
Enhancements and New Features
New VersionOne Fields in Explore Data
There are two new Explore Data Fields that will populate in both theManager Combined/VersionOneand theDefects (external)/ VersionOnesections of Explore Data:
V1 Project Begin Date
V1 Project End Date
Bug Fixes and Improvements
Ticket #
Component
Description
28892
Dashboards
The Dashboard Global Filter's "Test Cycle" section now refreshes upon the changing of your project.
Insights 1.21.8 OD June 18, 2019
Security Enhancements
Parameter Manipulation
We have checked each report to make sure that users only have access to data that they have been given permission to view.
Bug Fixes and Improvements
Ticket #
Component
Description
26414
Saved Reports
You can nowSaveandSave assuccessfully after making a change to a report.
27969
Dashboards
Saving a Dashboard no longer triggers an improper Dashboard name change.
26341
Dashboards
Opening or changing to a new Tab no longer causes Projects in the Global Filter to disappear in Insights Dashboard or Confluence Cloud.
26309
Dashboards
The list of the Test Case types in the drop-down menu now matches the Test Case types listed in qTest Manager.
27165
Editing a Saved Report
You can now Savewhile editing a report. Previously, the Save button would occasionally disappear while editing a report.
Insights 1.21.7 May 22, 2019
New Features and Enhancements
Manager Combined Reports with VersionOne Data
You can now createManager Combined ReportsusingVersionOne data. For more information on Manager Combined Reports, refer to this article.
Note:All of the VersionOne fields will, by default, not be selected when you first open the Manager combined report. You will need to select the fields yourself if you want to include them in your report.
VersionOne Data in the Explore Data Defects (External) Section
VersionOne datacan now be reported on from within theExplore Data Defects (External)section.
There have been two VersionOne fields added to the Explore Data Defects (External) section:
V1 Project (Standard Field)
Severity (Custom Field)
Note: Only users who have defined a VersionOne Custom Field "Severity" will see the "Severity" field populate in Explore Data.
New "Release Date" Standard Fields in Explore Data
Both the"qTest Release Start Date"and the"qTest Release End Date"standard fields have been added to the following Explore Data sections:
Requirements
Test Runs
Test Run Logs
Manager Combined
These additions allow you to report on the standard "Release Date" fields across all reports within Explore Data.
Insights 1.21.6 May 07, 2019
New Features and Enhancements
New Canned Reports
Insights 1.21.6 OnDemand offers five newDashboard Gallery Panels:
Test Execution Latest Result
Test Case Status by Project
Defect Status by Project
Defect (qTest) by Priority by Project
Defect (qTest) by Impact
Bug Fixes and Improvements
Ticket #
Component
Description
26235
Embedded Reports
You can now successfully embed reports with charts and crosstabs. Previously, charts were disappearing from embedded reports.
Insights 1.21.5 April 5 2019
Bug Fixes and Improvements
Ticket
Component
Description
26131
Dashboards
Charts in dashboards now appear correctly.
26402
Dashboards/ Jira
Charts that use Jira fields now display correctly after saved in Dashboards.
26661, 26774, 26659
Explore Data/Test Case, Explore Data/Test Run
Data retrieval issues in Explore Data have been resolved.
26062
Velocity Report
Alignment issues for overall stats within the Velocity Report have been resolved.
26691
Dashboards
Issues related to the presentation of Dashboard Panels have been fixed.
Insights 1.21.4 April 1st, 2019
Enhancements
Designer Mode
There is a newDesigner Modeavailable for all Explore Data Reports. When a user opens a report, the report will load in Designer Mode. You can build charts, define formulas, add filters, etc. From there, you can select theRun Reportoption, and all of that report's inputs would execute.
Test Case Type Monthly Trend Panel
We have added a Test Case Type Monthly Trend Panel to the Dashboard Gallery. With this, you are able to report on the general trend of Test Case types per month.

Bug Fixes and Improvements
Ticket
Component
Description
25718
Performance/Filter
There have been performance enhancements associated with the use of filters in Insights.
23724
Reports
Insights Reports saved as PDF's now show all necessary fields.
25317
Global Filter
The Global Filter now works properly when using IE11.
22488
Explore Data
There are no longer errors associated with Explore Data's Test Run Data when using a field whose site-field value is set to Korean.
24331
Scheduled Report
There is no longer an issue associated with Scheduled Reports being sent as PDF's when requesting XLS's.
24560
Explore Data/Crosstabs
There is no longer an issue associated with using "Assigned to" as the "Label Values Column" in a Crosstab. Previously, there were instances in which multiple people showed up in one cell.
24623
Portfolio
Jira Custom Fields show correctly in Portfolio.
26173
Explore Data
Explore Data and Global Filters were not working properly in Chrome: Version 73.0.3683.75 (Official Build) (64-bit). This has been resolved.
Insights 1.21.3.3 March 7, 2019
Bug Fixes and Improvements
Ticket
Component
Description
24765
Performance/Defect External Jira Report
Performance issues are now resolved when pulling JIRA bugs to create a dashboard.
Insights 1.21.3 February 18, 2019
Bug Fixes and Improvements
Ticket
Component
Description
24489, 23900
Reports
TheExternal Defects Report no longer displays duplicate defects.
24520
Performance
Enhanced loading time when opening saved "Explore Data" reports that contain formulas.
24225
Performance
Optimize code of startup tasks in order for Insights to open faster from the 9box.
Insights 1.21.2 January 29, 2019
Enhancements
Editing Saved Dashboards
You can now edit a saved Dashboard and its filters without having to create a brand new Dashboard. The modified Dashboard will also have the same shareable URL as it did prior to editing.
Bug Fixes and Improvements
Ticket #
Component
Description
23364
Dashboards
The drill-down for the External Defect Status chart now displays properly. Previously, customers would sometimes be hit with an error message.
23615
Explore Data PDF Report
The numbers associated with Test Cases are now properly aligned in their column within the "Check Manual Test Cases" chart. Previously, these numbers were slightly out of alignment.
Insights 1.21.1 January 17, 2019
Enhancements
Enhanced Test Case Automation Initiative Panel
The Test Case Automation Initiative by Release Panel has been enhanced with a new Test Case Type filter.
Note:Existing Dashboards already including this Panel will remain unchanged. In order for the user to make use of the new filter, he or she must remove the old Panel and add a new Panel.
Enhanced Reports in Explore Data
Several Reports within Explore Data have been enhanced for performance purposes. The following Reports have had a Build Date Field added:
Test Runs
Requirements
Test Run Logs
Manager Combined/ qTest Manager
Manager Combined/ Jira
Manager Combined/ Rally
Bug Fixes and Improvements
Ticket #
Component
Description
21877
Saved Reports/ Excel Extract
Excel extraction of saved reports has been improved. The extraction speed and load time have been bolstered.
21460
Performance
Improved performance for Explore Data/Defect Report.
View Article
Getting Started with qTest 9.7.1 OnPremise: July 2019

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
You will find information below for Supported Operating Systems and Browsers, Prerequisite Applications, Installation/Upgrade Guides, Deployment Models, along with Hardware Requirements and Supported Versions specific to qTest 9.7.1 OnPremise.
Exciting News!
qTest Manager 9.7.1 is now compatible with the newly released Tricentis Analytics 1.3.1,which requires a separate server in addition to the standard qTest deployment hardware.
Important Announcement
qTest Manager SSO Service Provider (SP) uses an x509 certificate to sign authentication requests and decrypt SAML assertions. As part of qTest Manager's security process, we update our SP certificate every 3 years in August.
If you are using SSO to login to qTest, you must update the SSL certificate in each Manager server before September 9, 2019 as well as, update the SP metadata in your configured IdP. If you do not complete these steps, your users will not be able to login to qtest Manager after the date above.
Replace Signed Certificate File for qTest SSO Integration
Update qTest Manager SSO Service Provider Certificate on SSO IdP
Note: If your IDP is configured topull SP metadata automatically, you will not need to complete this step.
In the event, you are unable to update your IdP before September 9, 2019, follow these instructions to bulk update your users to authenticate via qTest internal (username/password) from your current SSO authentication.
New Enhancements
In the 9.7.1 OnPremise release, qtestctl 6.4 package, we moved from Oracle Jdk 1.8.0_144 to Open JDK 1.8.0_212.
Release Notes
Below are the Release Notes for each qTest application associated with this OnPremise release.
Manager 9.7.1
Sessions 4.2.7
Parameters 2.2.4
Insights 1.21.9.2
Launch 1.5.3
Scenario 3.1.1
Pulse 9.2.2
Tricentis Analytics 1.3.1
Hardware Requirements
qTest 9.7.1
Your team size and the applications included in your subscription plan will determine the right hardware requirements needed before the installation. Please see this article: Server Sizing Guide
Tricentis Analytics 1.3.1
For information on Tricentis Analytics 1.3.1 hardware requirements, refer to this article.
Deployment Models
qTest 9.7.1
qTest components (and prerequisite applications) communicate with each other via TCP and HTTP, so they can be installed on different systems as long as they can connect via specific ports. Files that may need to be shared among services can be supported by a distributed file system like NFS or SMB. In QASymphony's production cloud deployment, each application has a dedicated server to ensure the best control, but that may not be necessary for an OnPremise deployment. For best practices, please see the examples provided in this article: Selecting your OS and Deployment Model
Deployment Model and Architecturefor Tricentis Analytics 1.3.1
For information on the Tricentis Analytics architecture, please refer to this article.
Supported Systems
Operating Systems
qTest installation packages are offered for these 3 types of environments:
Docker on Linux (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Linux native (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Windows native (2008 R2, 2012 R2, 2016)
Browsers
qTest works best on the latest stable versions of:
Chrome
Firefox
Safari
IE11
Prerequisite Applications
qTest 9.7.1
Based on the OS environment, please see the list of prerequisites below:
Docker
Must have access to the outside internet (cannot be used in closed network)
Docker Host v17.03-ce - v17.12-ce See: Instructions to install Docker
Kernel must be at least 3.10
Once you have Docker installed, you'll automatically have access to the prerequisite applications
If you're using CentOS, See: Adjust Docker Storage Drive for CentOS
Windows or Linux (non-Docker)
The table below shows the required versions of prerequisite applications. These must be installed and running before deploying qTest applications.
Here are some basic instructions for installing these prerequisites.If you need more detailed instructions to install these prerequisites, click on the hyperlinks in the table below.
Install Prerequisite Applications on Windows
Setup an NFS Folder on Windows
Install Prerequisite Applications on Ubuntu/CentOS (non-Docker)
Setup an NFS Folder on Linux
PREREQUISITE APPS
DESCRIPTION
SUBSCRIPTION PLAN
Sessions + Explorer
Premium
Elite
PostgreSQL 9.5.4 - 10
NOTE:
A PostgreSQLsuper useris required
This user must be named "postgres" and granted with read/write permissions
Database Server for Manager, Sessions, Insights, Parameters, Launch, Pulse and Scenario.
this article.
Elasticsearch 6.3 - 6.8
Database Server for Manager
An NFS directory
NOTE:
This is only required if you are deploying qTest applications using load balancing model
To store attachments
(optional)
(optional)
(optional)
IMPORTANT:If you are planning on installing Tricentis Analytics 1.3.1, you will need to make some changes to your ElasticSearch. For more information, please refer to the Tricentis Analytics 1.3.1 patch notes.
Tricentis Analytics 1.3.1
For information on prerequisite material for the Tricentis Analytics 1.3.1 install, please refer to this article.
qTest Products
Each product in the qTest platform delivers a tailored experience for its users. Below is a list of the products that you should install for each subscription plan:
PRODUCT
DESCRIPTION
SUBSCRIPTION PLAN
Sessions + Explorer
Premium
Elite
Manager
Test Case Management
*
Sessions
Screen Capture and Recording
Parameters
Reusable Test Input Data
Insights
Testing Metrics and Analytics
Launch
Centralized Test Automation
Scenario
Jira Plugin for BDD
Pulse
Agile and DevOps Workflows
*qTest Manager component for Sessions + Explorer package is simply for Administration purposes and does not contain test case management features.
Install and Upgrade Guides
qTest 9.7.1
Below are links to our Master Install and Upgrade Guides for the qTest Product Suite. These Master Guides provide you access to previous versions and operating system instructions.
Install Guides
Upgrade Guides
Tricentis Analytics 1.3.1
Install Guide
Upgrade Guide
Ports
qTest 9.7.1
Please note, that you must open the ports belowpriorto any self/assisted installation or upgrade. You should only open the HTTPS ports if you plan to serve SSL from the application.
PREREQUISITE APPLICATIONS
Product
Port
Postgres
5432
ElasticSearch
9200
Network Drive
2049
LINUX DOCKER
Product
HTTP Port
HTTPS Port
Manager
80
443
Sessions
8080
8443
qMap
7080
7443
Scenario
6080
6443
Insights
9080
9443
Parameters
10080
10443
Pulse
4080
4443
Launch
3080
3443
LINUX NON-DOCKER AND WINDOWS
Product
HTTP Port
HTTPS Port
Manager
8080
8443
Sessions
9080
9443
Scenario
6080
6443
Insights
10080
10443
Parameters
5080
5443
Pulse
4080
4443
Launch
3080
3443
Tricentis Analytics 1.3.1
Tricentis Analytics uses the following ports by default:
Default TCP Ports: (these are not interchangeable or configurable. Validate to check that these ports are not being used by other applications):
80 (open both in and outbound)
443 (open both in and outbound)
4242 (open inbound)
4247 (open inbound)
Tricentis AnalyticsAuthority Web AppPort (this is configurable):
5000 (open both in and outbound)
Port forTricentis AnalyticsinternalPostgres(this is configurable if necessary):
4432
Internal port forAppSync(this is configurable if necessary):
8080
For more information on Tricentis Analytics 1.3.0 install prerequisites, refer to this article.
Supported Versions
As outlined in the Terms of Use (Appendix A - Support Services), QASymphony OnPremise support expires for any software version more than 12 months after any superseding update. Therefore, we recommend that customers keep up with the latest updates and upgrade their software. For information on OnPremise software versions and their support status, refer to
View Article
Getting Started with qTest 9.6.1 OnPremise

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
This article is for the release of qTest 9.6.1 OnPremise. You will find information for Supported Operating Systems and Browsers, Prerequisite Applications, Installation/Upgrade Guides, Deployment Models, along with Hardware Requirements and Supported Versions.
New Enhancements
PostgreSQL SSL enablement
Pulse and Scenario migrating from MongoDB to PostgreSQL
Release Notes
Below are the Release Notes for each qTest application associated with the 9.6.1 OnPremise release.
Manager 9.6.1
Sessions 4.2.4
Parameters 2.2.3
Insights 1.21.5
Launch 1.4.7
Scenario 3.0
Pulse 9.2.1
Hardware Requirements
Based on your team size and the applications included in your subscription plan determine the right hardware requirements before the installation. Please see this article: Server Sizing Guide
Deployment Models
qTest components (and prerequisites applications) communicate with each other via TCP and HTTP, so they can be installed on different systems, as long as they can connect via specific ports. Files that may need to be shared among services can be supported by a distributed file system like NFS or SMB. In QASymphony's production cloud deployment, each application has a dedicated server to ensure the best control, but that may not be necessary for an OnPremise deployment. For best practices, please see the examples provided in this article: Selecting your OS and Deployment Model
Supported Systems
Operating Systems
qTest installation packages are offered for these 3 types of environment:
Docker on Linux (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Linux native (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Windows native (2008 R2, 2012 R2, 2016)
Browsers
qTest works best on the latest stable versions of:
Chrome
Firefox
Safari
IE11
Prerequisite Applications
Based on the OS environment, please see the list of prerequisites below:
Docker
Must have access to the outside internet (cannot be used in closed network)
Docker Host v17.03-ce - v17.12-ce See: Instructions to install Docker
Kernel must be at least 3.10
Once you have Docker installed, you'll automatically have access to the prerequisite applications
If you're using CentOS, See: Adjust Docker Storage Drive for CentOS
Windows or Linux (non-Docker)
The table below shows the required versions of prerequisite applications. These must be installed and running before deploying qTest applications.
Here are some basic instructions for installing these prerequisites.If you need more detailed instructions to install these prerequisites, click on the hyperlinks in the table below.
Install Prerequisite Applications on Windows
Setup an NFS Folder on Windows
Install Prerequisite Applications on Ubuntu/CentOS (non-Docker)
Setup an NFS Folder on Linux
PREREQUISITE APPS
DESCRIPTION
SUBSCRIPTION PLAN
Sessions + Explorer
Premium
Elite
PostgreSQL 9.5.4 - 10
NOTE:
A PostgreSQLsuper useris required
This user must be named "postgres" and granted with read/write permissions
Database Server for Manager, Sessions, Insights, Parameters, Launch, Pulse and Scenario.
this article.
Elasticsearch 6.3 - 6.8
Database Server for Manager
An NFS directory
NOTE:
This is only required if you are deploying qTest applications using load balancing model
To store attachments
(optional)
(optional)
(optional)
qTest Products
Each product in the qTest platform delivers a tailored experience for its users. Below is a list of the products that you should install for each subscription plan:
PRODUCT
DESCRIPTION
SUBSCRIPTION PLAN
Sessions + Explorer
Premium
Elite
Manager
Test Case Management
*
Sessions
Screen Capture and Recording
Parameters
Reusable Test Input Data
Insights
Testing Metrics and Analytics
Launch
Centralized Test Automation
Scenario
Jira Plugin for BDD
Pulse
Agile and DevOps Workflows
*qTest Manager component for Sessions + Explorer package is simply for Administration purposes and does not contain test case management features.
Install and Upgrade Guides
Below are links to our master Install and Upgrade Guides for the qTest Product Suite. These master guides provide you access to previous versions and operating system instructions.
Install Guides
Upgrade Guides
Ports
Please note, that you must open the ports belowpriorto any self/assisted installation or upgrade. You should only open the HTTPS ports if you plan to serve SSL from the application.
PREREQUISITE APPLICATIONS
Product
Port
Postgres
5432
ElasticSearch
9200
Network Drive
2049
LINUX DOCKER
Product
HTTP Port
HTTPS Port
Manager
80
443
Sessions
8080
8443
qMap
7080
7443
Scenario
6080
6443
Insights
9080
9443
Parameters
10080
10443
Pulse
4080
4443
Launch
3080
3443
LINUX NON-DOCKER AND WINDOWS
Product
HTTP Port
HTTPS Port
Manager
8080
8443
Sessions
9080
9443
Scenario
6080
4443
Insights
10080
10443
Parameters
5080
5443
Pulse
4080
4080
Launch
3080
3443
Supported Versions
As outlined in the Terms of Use (Appendix A - Support Services), QASymphony OnPremise support expires for any software version more than 12 months after any superseding update. Therefore, we recommend that customers keep up with the latest updates and upgrade their software. For information on OnPremise software versions and their support status, refer to
View Article
Getting Started with qTest 9.5.3 OnPremise

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
This article is for the Q1 2019 release of qTest 9.5.3 OnPremise. You will find information for Supported Operating Systems and Browsers, Prerequisite Applications, Installation/Upgrade Guides, Deployment Models, along with Hardware Requirements and Supported Versions.
Release Notes
Below are the Release Notes for each qTest application associated with the 9.5.3 OnPremise release.
Manager 9.5.3
Sessions 4.2.3
Parameters 2.2.2
Insights 1.21.3
Launch 1.4.3
Scenario 2.2.2
Pulse 9.1.2
Hardware Requirements
Based on your team size and the applications included in your subscription plan determine the right hardware requirements before the installation. Please see this article: Server Sizing Guide
Deployment Models
qTest components (and prerequisites applications) communicate with each other via TCP and HTTP, so they can be installed on different systems, as long as they can connect via specific ports. Files that may need to be shared among services can be supported by a distributed file system like NFS or SMB. In QASymphony's production cloud deployment, each application has a dedicated server to ensure the best control, but that may not be necessary for an OnPremise deployment. For best practices, please see the examples provided in this article: Selecting your OS and Deployment Model
Supported Systems
Operating Systems
qTest installation packages are offered for these 3 types of environment:
Docker on Linux (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Linux native (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Windows native (2008 R2, 2012 R2, 2016)
Browsers
qTest works best on the latest stable versions of:
Chrome
Firefox
Safari
IE11
Prerequisite Applications
Based on the OS environment, please see the list of prerequisites below:
Docker
Must have access to the outside internet (cannot be used in closed network)
Docker Host v17.03-ce - v17.12-ce See: Instructions to install Docker
Kernel must be at least 3.10
Once you have Docker installed, you'll automatically have access to the prerequisite applications
If you're using CentOS, See: Adjust Docker Storage Drive for CentOS
Windows or Linux (non-Docker)
The table below shows the required versions of prerequisite applications. These must be installed and running before deploying qTest applications.
Here are some basic instructions for installing these prerequisites.If you need more detailed instructions to install these prerequisites, click on the hyperlinks in the table below.
Install Prerequisite Applications on Windows
Setup an NFS Folder on Windows
Install Prerequisite Applications on Ubuntu/CentOS (non-Docker)
Setup an NFS Folder on Linux
Prerequisite Apps
Description
Subscription Plan
Sessions + Explorer
Premium
Elite
PostgreSQL 9.5.4 - 9.6.6
NOTE:
A PostgreSQL super useris required
This user must be named "postgres" and granted with read/write permissions
PostgreSQL 10 is NOT certified for this release.
Database Server for Manager, Sessions, Insights, Parameters, and Launch.
this article.
Elasticsearch 6.3 - 6.6
Database Server for Manager
MongoDB 3.4 - 3.6
Database Server for Scenario and Pulse.
An NFS directory
NOTE:
This is only required if you are deploying qTest applications using load balancing model
To store attachments
(optional)
(optional)
(optional)
qTest Products
Each product in the qTest platform delivers a tailored experience for its users. Below is a list of the products that you should install for each subscription plan:
Product
Description
Subscription Plan
Sessions + Explorer
Premium
Elite
Manager
Test Case Management
*
Sessions
Screen Capture and Recording
Parameters
Reusable Test Input Data
Insights
Testing Metrics and Analytics
Launch
Centralized Test Automation
Scenario
Jira Plugin for BDD
Pulse
Agile and DevOps Workflows
*qTest Manager component for Sessions + Explorer package is simply for Administration purposes and does not contain test case management features.
Install and Upgrade Guides
Below are links to our master Install and Upgrade Guides for the qTest Product Suite. These master guides provide you access to previous versions and operating system instructions.
Install Guides
Upgrade Guides
Ports
Please note, that you must open the ports below prior to any self/assisted installation or upgrade. You should only open the HTTPS ports if you plan to serve SSL from the application.
Prerequisite Applications
Product
Port
Postgres
5432
ElasticSearch
9200
Network Drive
2049
MongoDB
27017
Linux Docker
Product
HTTP Port
HTTPS Port
Manager
80
443
Sessions
8080
8443
qMap
7080
7443
Scenario
6080
6443
Insights
9080
9443
Parameters
10080
10443
Pulse
4080
4443
Launch
3080
3443
Linux non-Docker and Windows
Product
HTTP Port
HTTPS Port
Manager
8080
8443
Sessions
9080
9443
Scenario
6080
4443
Insights
10080
10443
Parameters
5080
5080
Pulse
4080
4080
Launch
3080
3080
Supported Versions
As outlined in the Terms of Use (Appendix A - Support Services), QASymphony OnPremise support expires for any software version more than 12 months after any superseding update. Therefore, we recommend that customers keep up with the latest updates and upgrade their software. For information on OnPremise software versions and their support status, refer to
View Article
Getting Started with qTest OnPremise Summer 2018

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
This article is for the qTest 9.1.5 OnPremise release for Summer 2018. You will find information for Supported Operating Systems and Browsers, Prerequisite Applications, Installation/Upgrade Guides, Deployment Models, and Hardware Requirements and Supported Versions.
Release Notes
Below are the Release Notes for each qTest application associated with the 9.1.5OnPremise release.
Manager 9.1.5
Sessions 4.2
Parameters 2.1.2
Insights 1.16.10.2
Launch 1.2
Scenario 2.0.3
Pulse 9.0.3
Hardware Requirements
Based on your team size and the applications included in your subscription plan determine the right hardware requirements before the installation. Please see this article: Server Sizing Guide
Deployment Models
qTest components (and prerequisites applications) communicate with each other via TCP and HTTP, so they can be installed on different systems, as long as they can connect via specific ports. Files that may need sharing among services can be supported by a distributed file system like NFS or SMB. In QASymphony's production cloud deployment, each application has a dedicated server to ensure the best control, but that may not be necessary for an OnPremise deployment. For best practices, please see the examples provided in this article: Selecting your OS and Deployment Model 9.1.5 and Later.
Supported Systems
Operating Systems
qTest installation packages are available for these three types of environments:
Docker on Linux (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Linux native (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Windows native (2008 R2, 2012 R2, 2016)
Browsers
qTest works best on the latest stable versions of:
Chrome
Firefox
Safari
IE11
Prerequisite Applications
Based on the OS environment, please see the list of prerequisites below:
Docker
Must have access to the outside internet (cannot be used in a closed network)
Docker Host v17.03-ce - v17.12-ce See: Instructions to install Docker
Kernel must be at least 3.10
Once you have Docker installed, you'll automatically have access to the prerequisite applications
If you're using CentOS, See: Adjust Docker Storage Drive for CentOS
Windows or Linux (non-Docker)
The table below shows the required versions of prerequisite applications. These must be installed and running before deploying qTest applications.
Here are some basic instructions for installing these prerequisites.If you need more detailed instructions to install these prerequisites, click on the hyperlinks in the table below:
Install prerequisite applications on Windows
Install prerequisite applications on Ubuntu/CentOS (non-Docker)
Set up an NFS folder on Windows
Setup an NFS folder on Linux
Prerequisite Apps
Description
Subscription Plan
Sessions + Explorer
Premium
Elite
PostgreSQL 9.5.4 - 9.6.6
NOTE:
A PostgreSQL super useris required
This user must be named "postgres" and granted with read/write permissions
Database Server for Manager, Sessions, Insights and Launch
Terms of Use
MongoDB 3.2 - 3.6
Database Server for Parameters, and Pulse
An NFS directory
NOTE:
This is only required if you are deploying qTest applications using load balancing model
To store attachments
(optional)
(optional)
(optional)
IMPORTANT: RabbitMQ and Redis have been removed for the prerequisite list for 9.1.5 OP.
qTest Applications
Each application in the qTest platform delivers a tailored experience for its users. Below is a list of the applications that you should install for each subscription plan:
Product
Description
Subscription Plan
Sessions + Explorer
Premium
Elite
Manager
Test Case Management
*
Sessions
Screen Capture and Recording
Parameters
Reusable Test Input Data
Insights
Testing Metrics and Analytics
Launch
Centralized Test Automation
Scenario
Enterprise BDD for Jira
Pulse
Agile and DevOps Workflows
*qTest Manager component for Sessions + Explorer package is simply for Administration purposes and does not contain test case management features.
Install and Upgrade Guides
Below are links to our master Install and Upgrade Guides for the qTest Product Suite. These master guides provide you access to previous versions and operating system instructions.
Install Guides
Upgrade Guides
Ports
Please note, that you must open the ports below prior to any self/assisted installation or upgrade. You should only open the HTTPS ports if you plan to serve SSL from the application.
Prerequisite Applications
Product
Port
Postgres
5432
Network Drive
2049
MongoDB
27017
Linux Docker
Product
HTTP Port
HTTPS Port
Manager
80
443
Sessions
8080
8443
qMap
7080
7443
Scenario
6080
6443
Insights
9080
9443
Parameters
10080
10443
Pulse
4080
4443
Launch
3080
3443
Linux non-Docker and Windows
Product
HTTP Port
HTTPS Port
Manager
8080
8443
Sessions
9080
9443
Scenario
6080
4443
Insights
10080
10443
Parameters
5080
5080
Pulse
4080
4080
Launch
3080
3080
IMPORTANT:Suggestedapplication portsare listed above. However, you are allowed to use a port of your choosing for theqTest applicationsyou install.
Supported Versions
As outlined in our (Appendix A - Support Services), QASymphony OnPremise support expires for any software version more than 12 months after any superseding update. Therefore, we recommend that customers keep up with the latest updates and upgrade their software.
Below are the OnPremise software versions and their support status:
qTest Platform
Version
Release Date
Out of Support Date
Status
9.1.5
June 2018
February 2019
Supported
9.0
February 2018
June 2019
Supported
8.7.3
October 2017
February 2019
Supported
8.4.4
June 2017
October 2018
Out of support
8.1.5
November 2016
June 2018
Out of support
7.7.3
June 2016
November 2017
Out of support
7.3.7
March 2016
June 2017
Out of support
View Article
Getting Started with qTest OnPremise Fall 2018

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
This article is for the Fall 2018 release of qTest 9.3 OnPremise. You will find information for Supported Operating Systems and Browsers, Prerequisite Applications, Installation/Upgrade Guides, Deployment Models, along with Hardware Requirements and Supported Versions.
Release Notes
Below are the Release Notes for each qTest application associated with the 9.3 OnPremise release.
Manager 9.3
Sessions 4.2.1
Parameters 2.1.7
Insights 1.19.1
Launch 1.3.2
Scenario 2.0.4-1
Pulse 9.1
IMPORTANT: Read the JIRA Cloud Connection--Important Deprecation Notice for Username/Password Method. The current username/password integration option will be deprecated December 1, 2018.
Hardware Requirements
Based on your team size and the applications included in your subscription plan determine the right hardware requirements before the installation. Please see this article: Server Sizing Guide
Deployment Models
qTest components (and prerequisites applications) communicate with each other via TCP and HTTP, so they can be installed on different systems, as long as they can connect via specific ports. Files that may need to be shared among services can be supported by a distributed file system like NFS or SMB. In QASymphony's production cloud deployment, each application has a dedicated server to ensure the best control, but that may not be necessary for an OnPremise deployment. For best practices, please see the examples provided in this article: Selecting your OS and Deployment Model
Supported Systems
Operating Systems
qTest installation packages are offered for these 3 types of environment:
Docker on Linux (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Linux native (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Windows native (2008 R2, 2012 R2, 2016)
Browsers
qTest works best on the latest stable versions of:
Chrome
Firefox
Safari
IE11
Prerequisite Applications
Based on the OS environment, please see the list of prerequisites below:
Docker
Must have access to the outside internet (cannot be used in closed network)
Docker Host v17.03-ce - v17.12-ce See: Instructions to install Docker
Kernel must be at least 3.10
Once you have Docker installed, you'll automatically have access to the prerequisite applications
If you're using CentOS, See: Adjust Docker Storage Drive for CentOS
Windows or Linux (non-Docker)
The table below shows the required versions of prerequisite applications. These must be installed and running before deploying qTest applications.
Here are some basic instructions for installing these prerequisites.If you need more detailed instructions to install these prerequisites, click on the hyperlinks in the table below.
Install prerequisite applications on Windows
Install prerequisite applications on Ubuntu/CentOS (non-Docker)
Set up an NFS folder on Windows
Prerequisite Apps
Description
Subscription Plan
Sessions + Explorer
Premium
Elite
PostgreSQL 9.5.4 - 9.6.6
NOTE:
A PostgreSQL super useris required
This user must be named "postgres" and granted with read/write permissions
Database Server for Manager, Sessions, Insights and Launch.
this article.
MongoDB 3.2 - 3.6
Database Server for Parameters, Scenario and Pulse.
An NFS directory
NOTE:
This is only required if you are deploying qTest applications using load balancing model
To store attachments
(optional)
(optional)
(optional)
qTest Products
Each product in the qTest platform delivers a tailored experience for its users. Below is a list of the products that you should install for each subscription plan:
Product
Description
Subscription Plan
Sessions + Explorer
Premium
Elite
Manager
Test Case Management
*
Sessions
Screen Capture and Recording
Parameters
Reusable Test Input Data
Insights
Testing Metrics and Analytics
Launch
Centralized Test Automation
Scenario
Jira Plugin for BDD
Pulse
Agile and DevOps Workflows
*qTest Manager component for Sessions + Explorer package is simply for Administration purposes and does not contain test case management features.
Install and Upgrade Guides
Below are links to our master Install and Upgrade Guides for the qTest Product Suite. These master guides provide you access to previous versions and operating system instructions.
Install Guides
Upgrade Guides
Ports
Please note, that you must open the ports below prior to any self/assisted installation or upgrade. You should only open the HTTPS ports if you plan to serve SSL from the application.
Prerequisite Applications
Product
Port
Postgres
5432
Network Drive
2049
MongoDB
27017
Linux Docker
Product
HTTP Port
HTTPS Port
Manager
80
443
Sessions
8080
8443
qMap
7080
7443
Scenario
6080
6443
Insights
9080
9443
Parameters
10080
10443
Pulse
4080
4443
Launch
3080
3443
Linux non-Docker and Windows
Product
HTTP Port
HTTPS Port
Manager
8080
8443
Sessions
9080
9443
Scenario
6080
4443
Insights
10080
10443
Parameters
5080
5080
Pulse
4080
4080
Launch
3080
3080
Supported Versions
As outlined in the Terms of Use (Appendix A - Support Services), QASymphony OnPremise support expires for any software version more than 12 months after any superseding update. Therefore, we recommend that customers keep up with the latest updates and upgrade their software. For information on OnPremise software versions and their support status, refer to
View Article
Getting Started with qTest OnPremise Spring 2018

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
This article is for the qTest 9.0 OnPremise release for Spring 2018. You will find information for Supported Operating Systems and Browsers, Prerequisite Applications, Installation/Upgrade Guides, Deployment Models, along with Hardware Requirements and Supported Versions.
Hardware Requirements
Based on your team size and the applications included in your subscription plan determine the right hardware requirements before the installation. Please see this article: Server Sizing Guide
Deployment Models
qTest components (and prerequisites applications) communicate with each other via TCP and HTTP, so they can be installed on different systems, as long as they can connect via specific ports. Files that may need to be shared among services can be supported by a distributed file system like NFS or SMB. In QASymphony's production cloud deployment, each application has a dedicated server to ensure the best control, but that may not be necessary for an OnPremise deployment. For best practices, please see the examples provided in this article: Selecting your OS and Deployment Model
Supported Systems
Operating Systems
qTest installation packages are offered for these 3 types of environment:
Docker on Linux (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Linux native (CentOS 7.2-7.3) or (Ubuntu 16.04-16.10) 64-bit
Windows native (2008 R2, 2012 R2, 2016)
Browsers
qTest works best on the latest stable versions of:
Chrome
Firefox
Safari
IE11
Prerequisite Applications
Based on the OS environment, please see the list of prerequisites below:
Docker
Must have access to the outside internet (cannot be used in closed network)
Docker Host v17.03-ce - v17.12-ce See: Instructions to install Docker
Kernel must be at least 3.10
Once you have Docker installed, you'll automatically have access to the prerequisite applications
If you're using CentOS, See: Adjust Docker Storage Drive for CentOS
Windows or Linux (non-Docker)
The table below shows the required versions of prerequisite applications. These must be installed and running before deploying qTest applications.
Here are some basic instructions for installing these prerequisites.If you need more detailed instructions to install these prerequisites, click on the hyperlinks in the table below.
Install prerequisite applications on Windows
Install prerequisite applications on Ubuntu/CentOS (non-Docker)
Set up an NFS folder on Windows
Prerequisite Apps
Description
Subscription Plan
Sessions + Explorer
Premium
Elite
PostgreSQL 9.5.4 - 9.6.6
NOTE:
A PostgreSQL super useris required
This user must be named "postgres" and granted with read/write permissions
Database Server for Manager, Sessions, Insights and Launch
Terms of Use
RabbitMQ 3.5.4 - 3.7
Message Broker
Erlang (Compatible version of RabbitMQ )
Prerequisite of Rabbit MQ
Redis 2.8.19 - 3.2.10
Memory Cache
MongoDB 3.4 - 3.6
Database Server for Parameters, and Pulse
An NFS directory
NOTE:
This is only required if you are deploying qTest applications using load balancing model
To store attachments
(optional)
(optional)
(optional)
qTest Applications
Each application in the qTest platform delivers a tailored experience for its users. Below is a list of the applications that you should install for each subscription plan:
Product
Description
Subscription Plan
Sessions + Explorer
Premium
Elite
Manager
Test Case Management
*
Sessions
Screen Capture and Recording
Parameters
Reusable Test Input Data
Insights
Testing Metrics and Analytics
Launch
Centralized Test Automation
Pulse
Agile and DevOps Workflows
*qTest Manager component for Sessions + Explorer package is simply for Administration purposes and does not contain test case management features.
Install and Upgrade Guides
Below are links to our master Install and Upgrade Guides for the qTest Product Suite. These master guides provide you access to previous version and operating system instructions.
Install Guides
Upgrade Guides
Ports
Please note, that you must open the ports below prior to any self/assisted installation or upgrade. You should only open the HTTPS ports if you plan to serve SSL from the application.
Prerequisite Applications
Product
Port
RabbitMQ
5672/61613
Redis
6379
Postgres
5432
Network Drive
2049
MongoDB
27017
Linux Docker
Product
HTTP Port
HTTPS Port
Manager
80
443
Sessions
8080
8443
qMap
7080
7443
Scenario
6080
6443
Insights
9080
9443
Parameters
10080
10443
Pulse
4080
4443
Launch
3080
3443
Linux non-Docker and Windows
Product
HTTP Port
HTTPS Port
Manager
8080
8443
Sessions
9080
9443
Scenario
6080
4443
Insights
10080
10443
Parameters
5080
5080
Pulse
4080
4080
Launch
3080
3080
Supported Versions
As outlined in the (Appendix A - Support Services), QASymphony OnPremise support expires for any software version more than 12 months after any superseding update. Therefore, we recommend that customers keep up with the latest updates and upgrade their software.
Below are the OnPremise software versions and their support status:
qTest Platform
Version
Release Date
Out of Support Date
Status
9.0
February 2018
Supported
8.7.3
October 2017
February 2019
Supported
8.4.4
June 2017
October 2018
Supported
8.1.5
November 2016
June 2018
Supported
7.7.3
June 2016
November 2017
Out of support
7.3.7
March 2016
June 2017
Out of support
View Article
Getting Started with Q4 2019 qTest OnPremise

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
You will find information below for Supported Operating Systems and Browsers, Prerequisite Applications, Installation/Upgrade Guides, Deployment Models, along with Hardware Requirements and Supported Versions specific to the Q4 2019 qTest OnPremise release.
To request assistance with installation or obtain the self-install links, complete the OnPremise New Install Form.
To request assistance with upgrade or obtain the self-upgrade links, use the Upgrade Request Form.
New for This Release:Enhanced Security Enablement for Sessions and Insights
During an attempted CSRF attack, user credentials may potentially be inherited and then used to maliciously perform undesirable actions, usually affecting a change of state of server. Please note that this does not result in any data theft. Additional details are provided within the Install/Upgrade guides.
Release Notes
Below are the Release Notes for each qTest application associated with the Q4 2019 OnPremise release.
Manager 9.8.3
Sessions 4.2.8
Insights 1.21.12
Scenario 3.2.0
Tricentis Analytics 1.4
compatible with qTest Manager 9.8.3 and Tosca 13.0
Hardware Requirements
qTest 9.8.3
Your team size and the applications included in your subscription plan will determine the right hardware requirements needed before the installation. Please see this article: Server Sizing Guide
Tricentis Analytics 1.4
For information on Tricentis Analytics 1.4 hardware requirements, refer to this article.
Deployment Models
qTest 9.8.3
qTest components (and prerequisite applications) communicate with each other via TCP and HTTP, so they can be installed on different systems as long as they can connect via specific ports. Files that may need to be shared among services can be supported by a distributed file system like NFS or SMB. In QASymphony's production cloud deployment, each application has a dedicated server to ensure the best control, but that may not be necessary for an OnPremise deployment. For best practices, please see the examples provided in this article: Selecting your OS and Deployment Model
Deployment Model and Architecturefor Tricentis Analytics 1.4
For information on the Tricentis Analytics architecture, please refer to this article.
Supported Systems
Operating Systems
qTest installation packages are offered for these 3 types of environments:
Docker on Linux (CentOS 7.2-7.4) or (Ubuntu 16.04-18.04) 64-bit
Linux native (CentOS 7.2-7.4) or (Ubuntu 16.04-18.04) 64-bit
Windows native (2008 R2, 2012 R2, 2016, 2019)
Browsers
qTest works best on the latest stable versions of:
Chrome
Firefox
Safari
IE11
Prerequisite Applications
qTest 9.8.3
Based on the OS environment, please see the list of prerequisites below:
Docker
Must have access to the outside internet (cannot be used in closed network)
Docker Host v17.03-ce to v18.03-ce See: Instructions to install Docker
Kernel must be at least 3.10
Once you have Docker installed, you'll automatically have access to the prerequisite applications
If you're using CentOS, See: Adjust Docker Storage Drive for CentOS
Windows or Linux (non-Docker)
The table below shows the required versions of prerequisite applications. These must be installed and running before deploying qTest applications.
Here are some basic instructions for installing these prerequisites.If you need more detailed instructions to install these prerequisites, click on the hyperlinks in the table below.
Install Prerequisite Applications on Windows
Setup an NFS Folder on Windows
Install Prerequisite Applications on Ubuntu/CentOS (non-Docker)
Setup an NFS Folder on Linux
PREREQUISITE APPS
DESCRIPTION
SUBSCRIPTION PLAN
Premium
Elite
PostgreSQL 9.5.4 - 10
NOTE:
A PostgreSQLsuper useris required
This user must be named "postgres" and granted with read/write permissions
Database Server for Manager, Sessions, Insights, Parameters, Launch, Pulse and Scenario.
this article.
Elasticsearch 6.5 - 6.8.1
Database Server for Manager
An NFS directory
NOTE:
This is only required if you are deploying qTest applications using load balancing model
To store attachments
(optional)
(optional)
Tricentis Analytics 1.4
For prerequisite information on the Tricentis Analytics 1.4 install, please refer to this article.
qTest Products
Each product in the qTest platform delivers a tailored experience for its users. Below is a list of the products that you should install for each subscription plan:
PRODUCT
DESCRIPTION
SUBSCRIPTION PLAN
Premium
Elite
Manager
Test Case Management
*
Sessions/
Explorer
Screen Capture and Recording
Parameters
Reusable Test Input Data
Insights/
Tricentis Analytics
Testing Metrics and Analytics
Launch
Centralized Test Automation
Scenario
Jira Plugin for BDD
Pulse
Agile and DevOps Workflows
*qTest Manager component for the Premium package is simply for Administrative purposes and does not contain test case management features.
Install and Upgrade Guides
qTest 9.8.3
Below are links to our Master Install and Upgrade Guides for the qTest Product Suite. These Master Guides provide you access to previous versions and operating system instructions.
Install Guides
Upgrade Guides
Tricentis Analytics 1.4
Install Guide
Upgrade Guide
Ports
qTest 9.8.3
Please note, that you must open the ports belowpriorto any self/assisted installation or upgrade. You should only open the HTTPS ports if you plan to serve SSL from the application.
PREREQUISITE APPLICATIONS
Product
Port
Postgres
5432
ElasticSearch
9200
Network Drive
2049
LINUX DOCKER
Product
HTTP Port
HTTPS Port
Manager
80
443
Sessions
8080
8443
qMap
7080
7443
Scenario
6080
6443
Insights
9080
9443
Parameters
10080
10443
Pulse
4080
4443
Launch
3080
3443
LINUX NON-DOCKER AND WINDOWS
Product
HTTP Port
HTTPS Port
Manager
8080
8443
Sessions
9080
9443
Scenario
6080
6443
Insights
10080
10443
Parameters
5080
5443
Pulse
4080
4443
Launch
3080
3443
Tricentis Analytics 1.4
Tricentis Analytics uses the following ports by default:
Port Type
Port #
Open Direction
Configurable
Default TCP Ports
80
inbound and outbound
no
443
inbound and outbound
no
4242
inbound
no
4247
inbound
no
Tricentis AnalyticsAuthority Web AppPort
5000
in and outbound
yes
Tricentis AnalyticsinternalPostgres
4432
if necessary
Internal port forAppSync
8080
if necessary
For more information on Tricentis Analytics 1.4 install prerequisites, refer to this article.
Supported Versions
As outlined in the Terms of Use (Appendix A - Support Services), QASymphony OnPremise support expires for any software version more than 12 months after any superseding update. Therefore, we recommend that customers keep up with the latest updates and upgrade their software. For information on OnPremise software versions and their support status, refer to
View Article
OnPremise Upgrade Guides

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
Use the following installation guidesto upgrade your qTest applications.
Note: If you are wanting to perform a fresh install of a qTest application refer to the OnPremise InstallGuide.
Before You Begin
It is important to review the Recommended Hardware Requirements article before you begin and Backup your Data before you upgrade.
Additionally, prerequisite applications need to be installed and running before deploying your qTest applications. Below are instructions to install and configure these prerequisite applications when upgrading from qTest applications associated with the Q4 2019 OnPremise release.
Install prerequisite applications on Windows
Install prerequisite applications on Ubuntu/CentOS
Setup an NFS folder on Windows
Setup an NFS folder on Linux
Upgrading a qTest Manager Version Older than 8.7.3?
In the event you are upgrading from a qTest Manager version that is older than 8.7.3 you will also need to perform additional upgrades to your prerequisite applications.
If you are upgrading qTest Manager from:
7.7.3 to 8.1.5-install Postgres 9.4
8.1.5 to 8.4.4-upgrade to Postgres 9.5 and Java 8
8.4.4 to 8.7.3-no prerequisite application upgrades required
8.7.3 to 9.0- upgrade to the following:
Redis2.8.19
RabbitMQ 3.7
Postgres 9.5.4 to 9.6.6
MongoDB 3.2-3.6
9.0 to 9.1.5-no prerequisite application upgrades required. Redis and RabbitMQ removed from the prerequisite list.
9.1.5 to 9.3-no prerequisite application upgrades required.
9.3 to 9.5.3
Elasticsearch 6.3 to 6.6-NEW!
9.5.3-9.6.1-Mongo removed from the list
Postgres 9.5.4 to 10
Important: We provide arange of supported versionsfor the prerequisite components so that OnPremise customers can easily maintain qTest OnPremise over time. This reduces the need for you to upgrade every prerequisite component each time you upgrade qTest to the most recent version.
'Old' Insights Report Scheduler Removed
The 'Old' Report Scheduler for Insights is now removed from production and all customers will be using the 'New' Report Scheduler that released with Insights 1.14, on November 8, 2017.
Customers who have yet to migrate your report schedules areautomatically moved to the 'new' Report Scheduler, which is more reliable and schedules reports to run in your local timezone instead of the previous UTC-0.
All of your saved reports will remain, but you will lose the report schedules. You will need to reschedule your desired reports using the 'new' Report Scheduler.
Suggested Action Item Before Upgrade: Note your existing report schedules (one way is to capture ascreenshot) of your current schedule from the Manage Saved Reports screen. You can use your existing report schedule as a referencewhen implementing your report schedules in the 'new' Report Scheduler.To remedy this, read the Manage and Schedule reports with the 'new' Report Scheduler article.
Installation Upgrade Guides
The tables below provide Upgrade Guides for each applicationand version.Please use a monitor screen larger than 14 inches to ensure all of the Upgrade Guide links will open properly.
IMPORTANT:Upgrade qTest applications, for your operating system, in this exact order:
Manager
Sessions
Parameters
Insights
Launch
Pulse
Scenario
Windows
Windows
Release Date
Version
Manager
Sessions
Parameters
Insights
Launch
Pulse/Scenario
9.8.3
Manager 9.7.1 to 9.8.3
Sessions 4.2.7 to 4.2.8
Parameters 2.2.4 to 2.2.4
Insights 1.21.9.2 to 1.21.12
Launch 1.5.3 to 1.5.3
Scenario 3.1.1 to 3.2.0
Pulse 9.2.2 to 9.2.2
Single Server
Load Balancer
9.7.1
Manager 9.6.1 to 9.7.1
Sessions 4.2.4 to 4.2.7
Parameters 2.2.4 to 2.2.4
Insights 1.21.5 to 1.21.9.2
Launch 1.4.7 to 1.5.3
Scenario 3.0 to 3.1.1
Pulse 9.2 to 9.2.2
Single Server
Load Balancer
9.6.1
Manager 9.5.3 to 9.6.1
Sessions 4.2.3 to 4.2.4
Parameters 2.2.2 to 2.2.3
Insights 1.21.3 to 1.21.5
Launch 1.4.3 to 1.4.7
Scenario 2.2.2 to 3.0
Pulse 9.1.2 to 9.2
Single Server
Load Balancer
9.5.3
Manager 9.3 to 9.5.3
Sessions 4.2.1 to 4.2.3
Parameters 2.1.7 to 2.2.2
Insights 1.19.1 to 1.21.3
Launch 1.3.2 to 1.4.3
Scenario 2.0.4-1 to 2.2.2
Pulse 9.1.0 to 9.1.2
Single Server
Load Balancer
9.3
Manager 9.1.5 to 9.3
Sessions 4.2 to 4.2.1
Parameters 2.1.2 to 2.1.7
Insights 1.16.10.2 to 1.19.1
Launch 1.2 to 1.3.2
Scenario 2.0.3 to 2.0.4-1
Pulse 9.0.3 to 9.1.0
Single Server
Load Balancer
9.1.5
Manager 9.0 to 9.1.5
Sessions 4.1.0 to 4.2
Parameters 2.1 to 2.1.2
Insights 1.15.3 to 1.16.10.2
Launch 1.0 to 1.2
Scenario 2.0.1 to 2.0.3
Pulse 9.0 to 9.0.3
Single Server
Load Balancer
9.0
Manager 8.7.3 to 9.0
Sessions 4.0.2 to 4.1.0
Parameters 1.1 to 2.1
Insights1.12.2 to1.15.3
Scenario 2.0 to 2.0.1
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
N/A
Single Server
Fall 2017
Manager 8.4 to 8.7.3
Sessions 3.0.9 to 4.0.2
Insights1.11.2 to 1.12.2
Single Server

Load Balancer
Single Server
Load Balancer
N/A
Single Server
N/A
N/A
Summer 2017
Manager 8.1.5 to 8.4
Sessions 3.0.1 to 3.0.9
Parameters 1.1
Insights 1.2 to 1.11.2
Single Server
Load Balancer
Single Server
Load Balancer
N/A
Single Server
N/A
N/A
Fall 2016
Manager 7.7.3 to 8.1.5
Sessions 3.0.1
Insights 1.2
Single Server
Load Balancer
Single Server
N/A
N/A
N/A
N/A
June 2016
Manager 7.2.3 to 7.7.3
Single Server
Load Balancer
N/A
N/A
N/A
N/A
N/A
Docker (Ubuntu / CentOS)
Docker
Release Date
Version
Manager
Sessions
Parameters
Insights
Launch
Pulse/Scenario
9.8.3
Manager 9.7.1 to 9.8.3
Sessions 4.2.7 to 4.2.8
Parameters 2.2.4 to 2.2.4
Insights 1.21.9.2 to 1.21.12
Launch 1.5.3 to 1.5.3
Scenario 3.1.1 to 3.2.0
Pulse 9.2.2 to 9.2.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
9.7.1
Manager 9.6.1 to 9.7.1
Sessions 4.2.4 to 4.2.7
Parameters 2.2.4 to 2.2.4
Insights 1.21.5 to 1.21.9.2
Launch 1.4.7 to 1.5.3
Scenario 3.0 to 3.1.1
Pulse 9.2 to 9.2.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
9.6.1
Manager 9.5.3 to 9.6.1
Sessions 4.2.3 to 4.2.4
Parameters 2.2.2 to 2.2.3
Insights 1.21.3 to 1.21.5
Launch 1.4.3 to 1.4.7
Scenario 2.2.2 to 3.0
Pulse 9.1.2 to 9.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
9.5.3
Manager 9.3 to 9.5.3
Sessions 4.2.1 to 4.2.3
Parameters 2.1.7 to 2.2.2
Insights 1.19.1 to 1.21.3
Launch 1.3.2 to 1.4.3
Scenario 2.0.4-1 to 2.2.2
Pulse 9.1.0 to 9.1.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
9.3
Manager 9.1.5 to 9.3
Sessions 4.2 to 4.2.1
Parameters 2.1.2 to 2.1.7
Insights 1.16.10.2 to 1.19.1
Launch 1.2 to 1.3.2
Scenario 2.0.3 to 2.0.4-1
Pulse 9.0.3 to 9.1.0
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
9.1.5
Manager 9.0 to 9.1.5
Sessions 4.1.0 to 4.2
Parameters 2.1 to 2.1.2
Insights 1.15.3 to 1.16.10.2
Launch 1.0 to 1.2
Scenario 2.0.1 to 2.0.3
Pulse 9.0 to 9.0.3
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
9.0
Manager 8.7.3 to 9.0
Sessions 4.0.2 to 4.1.0
Parameters 1.1 to 2.1
Insights1.12.2 to1.15.3
Launch 1.0
Scenario 2.0 to 2.0.1
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
N/A
Single Server
Fall 2017
Manager 8.4 to 8.7.3
Sessions 3.0.9 to 4.0.2
Insights1.11.2 to 1.12.2
Single Server
Load Balancer
Single Server
Load Balancer
N/A
Single Server
N/A
N/A
Summer 2017
Manager 8.1.5 to 8.4
Sessions 3.0.1 to 3.0.9
Parameters 1.1
Insights 1.2 to 1.11.2
Single Server
Load Balancer
Single Server
Load Balancer
N/A
Single Server
N/A
N/A
Fall 2016
Manager 7.7 to 8.1.5
Sessions 3.0.1
Insights 1.2
Single Server
Single Server
N/A
N/A
N/A
N/A
Summer 2016
Manager 7.7
Single Server
N/A
N/A
N/A
N/A
N/A
Native Linux (Ubuntu/ CentOS)
Linux
Release Date
Version
Manager
Sessions
Parameters
Insights
Launch
Pulse/Scenario
9.8.3
Manager 9.7.1 to 9.8.3
Sessions 4.2.7 to 4.2.8
Parameters 2.2.4 to 2.2.4
Insights 1.21.9.2 to 1.21.12
Launch 1.5.3 to 1.5.3
Scenario 3.1.1 to 3.2.0
Pulse 9.2.2 to 9.2.2
Single Server
Load Balancer
9.7.1
Manager 9.6.1 to 9.7.1
Sessions 4.2.4 to 4.2.7
Parameters 2.2.4 to 2.2.4
Insights 1.21.5 to 1.21.9.2
Launch 1.4.7 to 1.5.3
Scenario 3.0 to 3.1.1
Pulse 9.2 to 9.2.2
Single Server
Load Balancer
9.6.1
Manager 9.5.3 to 9.6.1
Sessions 4.2.3 to 4.2.4
Parameters 2.2.2 to 2.2.3
Insights 1.21.3 to 1.21.5
Launch 1.4.3 to 1.4.7
Scenario 2.2.2 to 3.0
Pulse 9.1.2 to 9.2
Single Server
Load Balancer
9.5.3
Manager 9.3 to 9.5.3
Sessions 4.2.1 to 4.2.3
Parameters 2.1.7 to 2.2.2
Insights 1.19.1 to 1.21.3
Launch 1.3.2 to 1.4.3
Scenario 2.0.4-1 to 2.2.2
Pulse 9.1.0 to 9.1.2
Single Server
Load Balancer
9.3
Manager 9.1.5 to 9.3
Sessions 4.2 to 4.2.1
Parameters 2.1.2 to 2.1.7
Insights 1.16.10.2 to 1.19.1
Launch 1.2 to 1.3.2
Scenario 2.0.3 to 2.0.4-1
Pulse 9.0.3 to 9.1.0
Single Server
Load Balancer
9.1.5
Manager 9.0 to 9.1.5
Sessions 4.1.0 to 4.2
Parameters 2.1 to 2.1.2
Insights 1.15.3 to 1.16.10.2
Launch 1.0 to 1.2
Scenario 2.0.1 to 2.0.3
Pulse 9.0 to 9.0.3
Single Server
Load Balancer
9.0
Manager 8.7.3 to 9.0
Sessions 4.0.2 to 4.1.0
Parameters 1.1 to 2.1
Insights1.12.2 to1.15.3
Launch 1.0
Scenario 2.0 to 2.0.1
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
N/A
Single Server
Fall 2017
Manager 8.4 to 8.7.3
Sessions 3.0.9 to 4.0.2
Insights1.11.2 to 1.12.2
Single Server
Load Balancer
Single Server
Load Balancer
N/A
Single Server
N/A
N/A
Summer 2017
Manager 8.1.5 to 8.4
Sessions 3.0.1 to 3.0.9
Parameters 1.1
Insights 1.2 to 1.11.2
Single Server
Load Balancer
Single Server
Load Balancer
N/A
N/A
N/A
N/A
Fall 2016
Manager 7.7 to 8.1.5
Sessions 3.0.1
Insights 1.2
Single Server
Single Server
N/A
N/A
N/A
N/A
Summer 2016
Manager 7.7
N/A
N/A
N/A
N/A
N/A
N/A
Fall 2015
Manager 6.2.4
N/A
N/A
N/A
N/A
N/A
View Article
OnPremise Install Guides

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
Use the following installation guides fora fresh install of your qTest applications.
Note: If you are upgrading a previously installed qTest application, refer to the OnPremise Upgrade Guide.
Before You Begin
It is important to review the Recommended Hardware Requirements article before you begin the installation.
Additionally, prerequisite applications need to be installed and running before deploying your qTest applications. Below are instructions to install and configure these prerequisite applications associated with the Q4 2019 OnPremise release.
Install prerequisite applications on Windows
Install prerequisite applications on Ubuntu/CentOS
Setup an NFS folder on Windows
Setup an NFS folder on Linux
Installation Guides
The tables below list applications that you can install based on your qTest license. Please use a monitor screen larger than 14 inches to ensure all of the install guide links will open properly.
IMPORTANT: Install qTest applications, for your operating system, in this exact order:
Manager
Sessions
Parameters
Insights
Launch
Pulse
Scenario
Note: Scenario is a Jira plug-in and you will find additional configuration instructions here to integrate Scenario with your Jira instance.
Windows
Windows
Release
Version
Manager
Sessions
Parameters
Insights
Launch
Scenario/Pulse
9.8.3
Manager 9.8.3
Sessions 4.2.8
Parameters 2.2.4
Insights 1.21.12
Launch 1.5.3
Scenario 3.2.0
Pulse 9.2.2
Single Server Install
Load Balancer Install
9.7.1
Manager 9.7.1
Sessions 4.2.7
Parameters 2.2.4
Insights 1.21.9.2
Launch 1.5.3
Scenario 3.1.1
Pulse 9.2.2
Single Server Install
Load Balancer Install
9.6.1
Manager 9.6.1
Sessions 4.2.4
Parameters 2.2.3
Insights 1.21.5
Launch 1.4.7
Scenario 3.0
Pulse 9.2
Single Server
Load Balancer
9.5.3
Manager 9.5.3
Sessions 4.2.3
Parameters 2.2.2
Insights 1.21.3
Launch 1.4.3
Scenario 2.2.2
Pulse 9.1.2
Single Server
Load Balancer
9.3
Manager 9.3
Sessions 4.2.1
Parameters 2.1.7
Insights 1.19.1
Launch 1.3.2
Scenario 2.0.4-1
Pulse 9.1.0
Single Server
Load Balancer
9.1.5
Manager 9.1.5
Sessions 4.2
Parameters 2.1.2
Insights 1.16.10.2
Launch 1.2
Scenario 2.0.3
Pulse 9.0.3
Single Server
Load Balancer
9.0
Manager 9.0
Sessions 4.1.0
Parameters 2.1
Insights1.15.3
Launch 1.0
Scenario 2.0
Pulse 9.0
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
Fall 2017
Manager 8.7.3
Sessions 4.0.2
Insights 1.12.2
Single Server
Load Balancer
Single Server
Load Balancer
N/A
Single Server
N/A
N/A
Summer 2017
Manager 8.4
Sessions 3.0.9
Parameters 1.1
Insights 1.11.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
N/A
N/A
Fall 2016
Manager 8.1.5
Sessions 3.0.1
Insights 1.2
Single Server
Load Balancer
Single Server
N/A
Single Server
N/A
N/A
Docker (Ubuntu / CentOS)
Docker
Release
Version
Manager
Sessions
Parameters
Insights
Launch
Scenario/Pulse
9.8.3
Manager 9.8.3
Sessions 4.2.8
Parameters 2.2.4
Insights 1.21.12
Launch 1.5.3
Scenario 3.2.0
Pulse 9.2.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
9.7.1
Manager 9.7.1
Sessions 4.2.7
Parameters 2.2.4
Insights 1.21.9.2
Launch 1.5.3
Scenario 3.1.1
Pulse 9.2.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
9.6.1
Manager 9.6.1
Sessions 4.2.4
Parameters 2.2.3
Insights 1.21.5
Launch 1.4.7
Scenario 3.0
Pulse 9.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
9.5.3
Manager 9.5.3
Sessions 4.2.3
Parameters 2.2.2
Insights 1.21.3
Launch 1.4.3
Scenario 2.2.2
Pulse 9.1.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
Fall 2018
Manager 9.3
Sessions 4.2.1
Parameters 2.1.7
Insights 1.19.1
Launch 1.3.2
Scenario 2.0.4-1
Pulse 9.1.0
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
Summer 2018
Manager 9.1.5
Sessions 4.2
Parameters 2.1.2
Insights 1.16.10.2
Launch 1.2
Scenario 2.0.3
Pulse 9.0.3
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
Spring 2018
Manager 9.0
Sessions 4.1.0
Parameters 2.1
Insights1.15.3
Launch 1.0
Scenario 2.0
Pulse 9.0
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
Fall 2017
Manager 8.7.3
Sessions 4.0.2
Insights 1.12.2
Single Server
Load Balancer
Single Server
Load Balancer
N/A
Single Server
N/A
N/A
Summer 2017
Manager 8.4
Sessions 3.0.9
Parameters 1.1
Insights 1.11.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
N/A
N/A
Fall 2016
Manager 8.1.5
Sessions 3.0.1
Insights 1.2
Single Server
Single Server
N/A
Single Server
N/A
N/A
Summer 2016
Manager 7.7
Single Server
N/A
N/A
N/A
N/A
N/A
Native Linux (Ubuntu/ CentOS)
Linux
Release
Version
Manager
Sessions
Parameters
Insights
Launch
Scenario/Pulse
9.8.3
Manager 9.8.3
Sessions 4.2.8
Parameters 2.2.4
Insights 1.21.12
Launch 1.5.3
Scenario 3.2.0
Pulse 9.2.2
Single Server
Load Balancer
9.7.1
Manager 9.7.1
Sessions 4.2.7
Parameters 2.2.4
Insights 1.21.9.2
Launch 1.5.3
Scenario 3.1.1
Pulse 9.2.2
Single Server
Load Balancer
9.6.1
Manager 9.6.1
Sessions 4.2.4
Parameters 2.2.3
Insights 1.21.5
Launch 1.4.7
Scenario 3.0
Pulse 9.2
Single Server
Load Balancer
9.5.3
Manager 9.5.3
Sessions 4.2.3
Parameters 2.2.2
Insights 1.21.3
Launch 1.4.3
Scenario 2.2.2
Pulse 9.1.2
Single Server
Load Balancer
9.3
Manager 9.3
Sessions 4.2.1
Parameters 2.1.7
Insights 1.19.1
Launch 1.3.2
Scenario 2.0.4-1
Pulse 9.1.0
Single Server
Load Balancer
9.1.5
Manager 9.1.5
Sessions 4.2
Parameters 2.1.2
Insights 1.16.10.2
Launch 1.2
Scenario 2.0.3
Pulse 9.0.3
Single Server
Load Balancer
9.0
Manager 9.0
Sessions 4.1.0
Parameters 2.1
Insights1.15.3
Launch 1.0
Scenario 2.0
Pulse 9.0
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
Single Server
Single Server
Fall 2017
Manager 8.7.3
Sessions 4.0.2
Insights 1.12.2
Single Server
Load Balancer
Single Server
Load Balancer
N/A
Single Server
N/A
N/A
Summer 2017
Manager 8.4
Sessions 3.0.9
Parameters 1.1
Insights 1.11.2
Single Server
Load Balancer
Single Server
Load Balancer
Single Server
Single Server
N/A
N/A
Fall 2016
Manager 8.1.5
Sessions 3.0.1
Insights 1.2
N/A
N/A
N/A
N/A
N/A
N/A
Summer 2016
Manager 7.7
N/A
N/A
N/A
N/A
N/A
N/A
Fall 2015
Manager 6.2.4
Single Server
Load Balancer
N/A
N/A
N/A
N/A
N/A
View Article
qTest Manager 9.8.3 Q4 2019 OnPremise Release Notes

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Overview
We are happy to announce the November 2019 release of qTest Manager 9.8.3 associated with the Q4 2019 OnPremise release! Here are a few release highlights:
Imported JIRA fields now searchable from the Data Query
Project Admin enhancements
Archiving qTest Projects
Copy/paste filtered results from qTest Navigation Trees
New Features and Enhancements
Improved Usability With Jira Requirements and Release Progress Dialogues
Users are now able to close the "Retrieve Jira Requirements" and "Retrieve Jira Release Progress" dialogues. The Jira Issues Objects will still synch to qTest Manager in the background.
Next-Gen Jira Compatibility
You can now retrieveSprintsfrom Next-Gen Jira Projects and have them populate as Releases in qTest Manager.
Imported JIRA Fields Searchable from the Data Query
The Data Query now includes the ability to search qTest Requirements, Test Cases, and Test Runs with linked JIRA Requirement and Defect fields. This enables you to locate JIRA data that is associated with qTest much easier! You can select the following qTest data and JIRA fields/values in the Data Query Criteria fields and view the results in the Query Result grid view.
qTest Requirements by JIRA Requirements fields
qTest Test Cases by JIRA Requirements fields
qTest Test Runs by JIRA Defects fields
An example query using Test Runs by JIRA Defect fields:
https://api.qasymphony.com/#/test-log/submitAutomationLog
You mustFetch JIRA Defects and Retrieve JIRA Data from the Integration Settings page, beforeattempting to query JIRA fields. This manual step re-indexes your database, to allow for the query to return results using JIRA data.
Limitation:
Due to a JIRA API limitation, JIRA fieldsthat use a drop-down box for the value, display as a textbox in the value field of a clause. Example:
Below is a cumulative list of the affected JIRA fields.
For additional information on using the Data Query, read this article.
Project-Level User Management Enhancements
The Add Project Usersdialog is enhanced for greater flexibility when managing your Project users. Project Admins, with the Edit Project Settings permission, can now Search for, Apply All, Add and Remove users when maintaining Projects. This enhancement is especially useful for organizations with many qTest users associated to one Project .
Additionally, a newSearch Users field is available above the User List on the User Management screen. This provides a quicker approach for searching individual users when managing their Project permissions.
For more information on maintaining your Users' Projects, and Profiles read this article.
Archive qTest Projects
Site Administrators with the Manage Projects permission, are now able to archive qTest Projects without fully deleting them from your qTest Manager repository. Projects which are archived, move to an inactive state but are available for accessing historical information. Archived Projects will be visible in Tricentis Analytics. You can also restore archived Projects.
Archiving a Project automatically deactivates the associated integrations with external ALM's.
Archived Projects will become inaccessible via API's.
After restoring an archived Project, integrations with external ALM's are not automaticallyreactivated.
Archive a Project
Restore a Project
For additional information on archiving and restoring qTest Projects, read this article.
Copy/Paste Filtered Results from qTest Navigation Trees
In the qTest Navigation Trees listed below, you can now copy/paste Modules (folders) and their containing objects with filters applied.This update allows you to choose if you want to copy and paste all objects associated with the Modules, or only objects associated with the Modules while viewing with the selected filters.
Example Use Case: You have filtered the Test Design tab, to display Modules (folders of Test Cases) and their associated Test Cases, that are very common and you wish to copy/paste those filtered Modules and specific Test Cases to another Project. This new feature allows the option to copy/paste those specific Test Cases, without having to copy all of the Test Cases within those Modules (which was the previous copy/paste option.)
Test Plan Tree:copy/paste filtered results forModules ofReleases and Builds within the same Project
Requirements Tree:copy/paste filtered results forModules and Requirements within the same Project
Copying Modules in the Requirements tab will not clone Test Cases in the same Modules
Test Design Tree:copy/paste filtered results forModules and Test Caseswithin the same Project or across Projects
Copying Modules in the Test Design tree will not clone Requirements in the same Modules.
Test Execution Tree: copy/paste filtered results forModules ofReleases, Test Cycles, Test Suites, and Test Runswithin the same Project
Upon copy/paste, or drag/drop + CTRL, you will receive this message:
For additional information on Copy/Pasting Modules or Test Cases, read these articles:
Reusing Test Cases
Create, Edit, Copy, Delete Requirements
Copy and Move Objects in Test Execution
Test Case Page Enhancements
The Test Case page within the Test Design tab now has an enhanced UI, in our continued effort to optimize qTest.Additionally, this UI redesign increases load speeds for the Test Case page when there are more than 1K Test Steps associated with one Test Case.
The following lists the new features and updates:
A new Add button is available below the last Test Step in the Test Steps grid, so users can quickly define a new step without the need to use the Action icon.
Using the Tab key while in the Expected Results field of the last Test Step, also adds a blank Test Step row.
The Precondition field is removed from the Properties section and relocated to the Test Steps grid, provided the Precondition field is active in your Field Settings. This allows you to view the Precondition in the same view as your Test Steps so that you no longer need to leave the Test Case Properties open and can view all Test Step information in one place.
The Linked Requirements change notification is now present in the top banner for greater visibility.
Requirements are moved to a new tab. Previously, Requirements were found below the Test Case Properties and Test Steps.
The Add Requirements module also received a new UI!
Ability to Define Custom Mapping Attributes for SSO Integration
Site Admins now have the ability to define custom mapping attributes for your SSO Integration. The attribute values are prepopulated by default, with the values below:
user.email
user.firstname
user.lastname
If you choose to change a default attribute value, to a custom mapping, qTest will use the new values to retrieve data from SAML responses.
The following SSO integrations are currently supported:
Single Sign-On (SSO) Integration with ADFS Active Directory Federation Services
Single Sign-On (SSO) Integration with Ping Federate
Single Sign-On (SSO) Integration with Okta
Single Sign-On (SSO) Integration with Microsoft Azure Active Directory
Improvements in Test Run Detail Reporting
In the Test Run dialog, users are able to add attachments to their Test Step Logs. These attachments will be included exported Excel files.
Security Improvements
Role-based authorization is improved to now use a One-Time Password Token (OTP.)
Bug Fixes
Ticket
Component
Description
31469
qTest API
There are no longer any issues related to inviting qTest users with SSO authentication via API's.
27637
JIRA Integration
qTest no longer allows linked non-bug JIRA issues to be created as Defects in qTest.
30837
Test Execution
There is no longer an incomplete scrolling issue within the Test Execution tab.
31928
qTest API
The Search Comment API's pagination is no longer broken.
31291
JIRA Plugin
If a user renamed a FixVersion in JIRA, then both FixVersions would display in the Release drop-down within the Test Execution iFrame of the qTest JIRA Plugin. This is now resolved.
29876
API
The Search API did not return results as expected when test steps contained HTML characters. This is fixed.
31921
31878
Audit Log
When attempting to load and export the Audit Log in the Security tab no action would occur. This is now resolved.
27463
Test Log APIs
When sending a POST request to the qTest V3 API /auto-test-logs URIthe HTTP response for qTest 9.3.0 has differently formatted self relationship link URLs than version 9.5.3. This is resolved.
27965
Defect Summary
An intermittent issue occurred when attempting to view the Defect Summary of a Release. If there were more than 50 defects in the list, the details would sometimes not appear. This is now resolved.
31179
Defect API
Previously, Defect API pagination would not return the expected number of defects. This is fixed.
31270, 31488
31501, 31451
30734, 31548
31482, 31584
31525, 31295
31769, 31692
Test Steps
When making amendments to Test Steps within Test Design, some users experienced not being able to save these Test Step changes when using Chrome v76. This is now fixed.
29892
API
Previously, Site Field names were missing from the Test Suite API response. This is now resolved.
29551
SSO
SSO now works as expected when using with an existing SSO session. Previously, some users experienced a lock-out, after attempting multiple logins with username/password authentication. This occurred when users were not notified in advance to utilize organizational SSO enablement.
27884
Site fields
There is no longer an issue with adding a new site field to an existing template.
30306
Test Runs
Users can now run Test Runs regardless of whether those Test Runs are shared and derived from a Test Case in a project that the user does not have permission to access.
29082
Site Fields Template
When viewing a Site Field Template, and navigating between the object types, not all fields displayed. This is now fixed.
29977
Integration Settings
Users received an "Error" message when adding requirement types in their Integration Settings. This has now been resolved.
30714
30713
30711
30710
30708
30707
30706
30705
30704
30703
Resources page
We have downgraded OAuth2 for Spring Security to version 2.0.7. This remediates the issue with users receiving an Oops error when accessing the Resources page.
30182
Login
qTest now accepts email addresses with the ' character.
32255
API
Previously, when creating Test Runs from Test Cases via the API, the Test Runs would intermittently get stuck in the que and not be created. This led to some users not being able to schedule Test Runs as expected. This is now fixed.
33223
JIRA Integration
An issue was encountered with JIRA Requirements no syncing properly. This is now resolved.
33224
Project Admin
The Project Admin User Profile could not add users to a Project. This is fixed.
33141
Test Case
If the Version field was disabled, users were unable to save a Test Case as expected. This is now resolved.
30612
JIRA Integration
When selecting the Retrieve JIRA Data button on theJIRA Integration > Requirements section, the manual sync would stall for some JIRA Server users. This is now resolved.
PIR-148
JIRA Integration
The JIRA integration and qTest synchronization were not performing properly for many users. This is fixed.
33411, 33598
33406, 33407
33416
Email Notification
Many users received duplicate email notifications stating they had been assigned to a Project, or assigned to a Project as an Admin, when the users were previously assigned. This issue is now resolved.
33094
Data Query
The Data Query for JIRA fields were not updating as expected. This issue was related to the data sync with JIRA integration. This is now fixed.
23921
TestPad
Notes added to an execution log, displayed the qTest servers timezone instead of the timezone associated with the PC. The timestamp displayed in the note was UTC. This is now fixed.
31327, 31908
31373,33175
32821
Test Execution
Exported reports for Test Execution would not display all headers for the selected columns of the "Export Test Run Detail" feature. Additionally, after exporting, some of the previously selected fields would no longer be visible for selection again. This is resolved.
32588, 33264
Test Execution
Some users encountered an issue when attempting to export Test Run Details when a custom field was removed from the Test Run. This placed a null value in the selected columns for the report, which returned an error. This is now resolved.
33222
Notifications
Previously, notification settings were not saving properly when activating/deactivating. This is now fixed.
The JIRA Requirements integration was not auto-linking properly in qTest. This is now fixed. Previously, some users experienced an issue with JIRA requirements already synced to qTest, when changes were made to the Fix Version/Sprint of a User Story in JIRA.
View Article
Insights 1.21.12 Q4 OnPremise Release Notes

PLEASE UPDATE YOUR LOGI LICENSE BEFORE IT EXPIRES. CLICK HERE FOR MORE INSTRUCTIONS.
Performance Enhancements
Ticket 29090: We have optimized the execution time of the Test Run Explore Data report.
Bug Fixes
Ticket
Component
Description
26773
Export
There is no longer an issue with exporting reports in the Explore Data Test Run report.
28125, 30844, 26664
Dashboard
There is no longer an issue with Dashboards disappearing.
30046
Custom Charts, Embed Feature, Saved Reports
We have resolved an issue with inconsistent Insights Graph Data due to timezone issues.
28161
Reports
Planned Time is now present on Insights Reports when added on Test Execution.
28874
Requirements Data
There is no longer a JSON parse error while generating Requirements Test Run Coverage
29445
Dashboards
When renaming dashboards in "Manage Dashboard," the new name can now contain spaces.
29535
Embed Feature
There is no longer an issue with embedded dashboards being blank on the initial load.
267769
Dashbaords
The data segregation works normally within Insights Dashboards.
27081
Rapid Dashboard
There is no longer an issue with the Rapid Dashboard URL getting created.
30820
Explore Data/ Test Run
The planned time for Test Runs with a status of "Unexecuted" now displays correct information.
31042
Dashboards
Data now displays correctly in the Automation Execution Dashboard.
31081
Quality Analysis
Information concerning configuration fields now displays correctly in the Quality Analysis Report.
31339
Explore Data/ Defects (Linked), Explore Data/ Test Run
There are no longer discrepancies within the the Explore Data Defects (Linked) and Test Run Reports.
27575
Explore Data
Changing the "Max Rows" value on a report from the default value of 500 to another selection no longer results in data not loading properly.
30844
Rapid Dashboard
There is no longer a problem with Rapid Dashboards causing them to automatically update to an untitled dashboard without any charts.
30268
Saved Reports/ Schedule
Dates in scheduled PDF reports are now successfully kept up to date.
31609
Embed Feature/ Explore Data
There is no longer an issue that causes an Insights embed script to fail to generate chart images.
32048
Explore Data/ Test Run
An issue has been fixed that caused Custom Field Data to not display properly in the Manager Combined Report.
View Article
Integrate JUnit for Java with Universal Agent

In this article, you will learn how to integrate JUnit for Java with the Universal Agent.
The sample source code of JUnit for Java project is located at a https://github.com/QASymphony/junit-sample
Prerequisites
Activate Automation Integration
Install and Register the Automation Host
You machine needs to have Java installed. The Java version should be the one compatible withwhat you use to run your JUnit for Java project
This example use Maven to execute the tests.Make sure you install maven to the automation host machine
Along with Maven, this example also uses maven-compiler-plugin and maven-surefire-plugin to execute tests and generate report. Refer to the IMPORTANT NOTES section to configure the pom.xml file when you integrate your actual JUnit for Java project with Universal Agent
Create JUnit for Java Universal Agent
From Launch, open the host machine where you want to create the new agent.
Select the + New Agent button.
https://github.com/QASymphony/junit-sample/blob/master/pom.xml
You will be presented with a New Agent dialog.
Enter the information listed below to create the new agent.
General Information
Agent Name: name of the agent, e.g. JUnit for Java Universal Agent
qTest Manager Project: select a qTest Manager project from which the agent is going to execute scheduled tests, e.g. qConnect Sample Project
Agent Type: selectUniversal Agent
Pre-Execute Script
Enter below script in Pre-Execute Script editor which is specific to the Operating System that the host is running.
Linux/Mac
#!/bin/bash
if [ ! -d "/usr/local/var/junit-sample" ]
then
cd "/usr/local/var"
git clone https://github.com/QASymphony/junit-sample
else
cd /usr/local/var/junit-sample
git pull --all
fi
Windows
if not exist "D:\junit-sample" (
cd /d D:\
git clone https://github.com/QASymphony/junit-sample
) else (
cd /d "D:\junit-sample"
git pull --all
)
Execute Command
Executor
Select nodeas the executor.
Working Directory
If your host machine is running on Linux or Mac: enter /usr/local/var/junit-sample
If your host machine is running on Windows, enter D:\junit-sample
Execute Command
You will configure the Execute Command to execute our JUnit project with maven with the following nodejs script. What it does is to resolve the value of magic variableTESTCASES_AC thenperforms the following:
if the value ofTESTCASES_ACmagic variable is empty, which means there is no test cases in qTest Manager being scheduled for execution, executes all the tests
otherwise, execute only the tests that match the automation content of the test case(s)
Notes:
make sure you install maven to your host machine for the command to be executed successfully by Universal Agent.
the execute command will need to specify full path to maven executable. You can execute the following command to find the Maven executable path from either Terminal (Linux/Mac) or Command Prompt (Windows),in bold.
$ mvn -v
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T14:41:47-04:00)
Maven home: /usr/local/opt/apache-maven-3.6.0
Java version: 10.0.2, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk-10.0.2.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.2", arch: "x86_64", family: "mac"
Enter the code snippet below to the Execute Command editor dependent on the OS that the automation host is running.
Windows
const { execSync } = require("child_process");
// NOTE: change the value to reflect the actual path to maven executable in your host machine
let mavenExePath = 'C:\\apache-maven-3.5.4\\bin\\mvn';
// if $TESTCASES_AC has values, build command to run tests that match automation content only. Otherwise, execute all the tests.
let command = `"${mavenExePath}" clean test`;
let testcases_AC = $TESTCASES_AC;
if (testcases_AC && 0 < testcases_AC.length) {
command = `"${mavenExePath}" -Dtest=${testcases_AC} clean test`;
}
console.log(`=== executing command ===`);
console.log(command)
execSync(command, {stdio: "inherit"});
console.log(`=== command completed ===`)
Linux or Mac
const { execSync } = require("child_process");
// NOTE: change the value to reflect the actual path to maven executable in your host machine
let mavenExePath = `/usr/local/opt/apache-maven-3.5.4/bin/mvn`;
// if $TESTCASES_AC has values, build command to run tests that match automation content only. Otherwise, execute all the tests.
let command = `"${mavenExePath}" clean test`;
let testcases_AC = $TESTCASES_AC;
if (testcases_AC && testcases_AC.length) {
command = `"${mavenExePath}" -Dtest=${testcases_AC} clean test`;
}
console.log(`=== executing command ===`);
console.log(command)
execSync(command, {stdio: "inherit"});
console.log(`=== command completed ===`);
Path to Results
Optional field. Enter the value below to specify the path to the test result generated by JUnit.
If your host machine is running on Linux or Mac:/usr/local/var/junit-sample/target/surefire-reports
If your host machine is running on Windows:D:\junit-sample\target\surefire-reports
Result Parser
Optional field. Select JUnit for Java as the Result Parser.
IMPORTANT NOTE
If you want the Universal Agent to submit test results to qTest Manager, you must specify values for both Path to Results and Result Parser. Otherwise, you must do that yourself via Execute Command.
The screenshot below shows how the new JUnit for Java Universal Agent is configured, on Mac.
Select SAVE to finish creating the agent. The agent will be available to next time host machine polls to qTest Launch.
Execute JUnit for Java Universal Agent
Access the host machine where the JUnit for Java Universal Agent was created.
Locate the agent in the Agents list and select theRun now button.

The Universal Agent execution dialog will display.
Select the Execute button to kick off the agent execution and you will see the logs shown in theConsole Log section. If the execution is successful, you'll see the test run logs being submitted to qTest Manager, as highlighted in below screenshot.

Now, access to qTest Manager. Navigate to the qConnect Sample project and select Test Execution module. You'll find the execution results has been submitted as test run logs under a Test Suites naming Automation YYYY-MM-DD, as shown below.
Schedule test execution for specific Test Runs with JUnit for Java Universal Agent
Access to qTest Manager. Navigate to qConnect Sample project. Select Test Execution and select the Test Suite created from the first execution of Universal Agent.
From the Test Run list in the right, select first 3 test runs. Click on MORE button and select Schedule.
The SCHEDULE AUTOMATION TEST EXECUTIONS DIALOG will display, enter the following:
Name: name of the schedule, e.g. JUnit Test Execution
Agent: select JUnit for Java Universal Agent. Notes the agent is displayed following this pattern <Automation Host Name> - <Agent Name>
Click OK to complete the scheduling
Now go back to Automation Host UI, click on Poll Now button.
At this stage, the Automation Host does the followings:
immediately polls to qTest Manager for scheduled jobs and
execute the job execution for the three test runs in JUnit project that match the automation content of the three scheduled test runs
When the execution completes, click onView Logicon to view execution log.
A log screen will display that shows the last execution logs. Notice that the log reported only three (3) tests have been executed.
Now get back toTest ExecutionofqConnect Sample Projectin qTest Manager. Click on each test run that was scheduled to be executed, you'll see the Execution History of each test run was updated with2test run logs: one test log created when the agent was executed in the first time, and one test log for the scheduled job execution.
You have successfully integrated your JUnit for Java project with Universal Agent.
IMPORTANT NOTES
When integrating your actual JUnit for Java project with Universal Agent and you choose to execute it with Maven (highly recommended),make sure to add the plugin maven-sure-fire-plugins and maven-compiler-plugin to yourpom.xmlfile, as shown below.
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
...
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.22.1</version>
<configuration>
<parallel>methods</parallel>
<threadCount>10</threadCount>
<testFailureIgnore>true</testFailureIgnore>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<encoding>iso-8859-1</encoding>
<source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
</plugins>
</build>

</project>
You can also refer to the pom.xml file used in our sample here:
View Article
Configure Scenario for Versions 2.1.0 and Beyond

Overview
After installing the qTest Scenario plugin, you must configure the Scenario settings on a per project basis to use Scenario in that project. The configuration will allow you to link your Jira project, Scenario, and yourGit repository. The first time you use qTest Scenario, you will be prompted to enter your Git username and password and select your preferences.
IMPORTANT: To configure qTest Scenario in a Jira project and use Scenario inside of Jira, the Git Repository Administrator will need to turnon your Git repository for the Jira project and assign the user(s) his or her credentials in the Git repository.
The user(s) must be a collaborator on that Git project, and the administrator must grant them push access. Currently, Scenario integrates with:
Bitbucket
GitHub
GitLab
Note:When integrating with GitLab, you must use a Personal Access Token instead of a Password. To learn how to retrieve your Personal Access Token, refer to this article.
How to Configure Scenario
Open your Jira application.
Select theJiraProject for whichyouwould like useScenario.
Trigger Jenkins Pulse Rule
Navigate to the Settingstab for the Jira project.
Scroll down within the Jira Project settings column, and selectqTest Scenario
The"Project Settings" page displays.
Note: The webhook displayed here is your Scenario webhook.You will use this to connect to your Git Repository.
Note:The picture here shows anEnterprise Settingstab. Please note that this will not show up unless you have enabled Enterprise Features. More on this in theEnable Enterprise Featuressection.
Project Settings
SelectConfigure your Project.
The "Configure Your Project Settings" dialog displays. Input the following:
Git RepositoryURL
Git Provider:choose the appropriate server environment
Feature File Folder:provide the directory path for the highest level feature file directory.
Feature File Extension:Choose either the .feature or .story extension.
Note:Even though Scenario offers a.storyextension, JBehave syntax is still not supported.
IMPORTANT:For versions 2.3.0 and beyond, qTest Scenario now supports JBehave syntax. Refer to the 2.3.0 Release Notes for more information.
Git Username
Git Password
Important: If you are using SSO, your Git Password will be your Git API Token instead of your personal Git Password.
Select Next, and choose your Default Branch tocommit yourcode. This is the repository code branch where your features files will be entered.
Select Next, and choose your Editor Issue Type(s). The issue type(s) selected here will be the default for the Scenario gherkin editor.
Select Next, and you will receive a message validating your setup is complete. Save.
Now your Scenario application is configured with your Jira application.
Enable Enterprise Features
Select the Enable Enterprise Features button if you are using a private repository and the paid version of Scenario.
Enter the following:
qTest Domain
qTest Username
qTest Password
Select Ready.
Your Enterprise Features are now enabled for qTest Scenario, and you will have an Enterprise Settings tab within your Scenario plugin.
Enterprise Settings
To access these settings, select theEnterprise Settings tabright next to theProject Settings tab.
Input the following information:
qTest Domain: enteryour qTest Pulse URL
Scenario Project Id: this is unique for each Jira project configured with Scenario. You will input this as a Pulse Constant.
Actions:used to configure Scenario with the. To add a new Action, do the following:
Select the New Action button.
Ensure the Active checkbox is selected.
Name the Action.
Input the Webhook Endpointwhich is the Pulse Event webhook associated with the Pulse Rule you are configuring with Scenario.
Save
View Article
qTest Controller - Applying 9.8.3-2 application patch for qTest Manager

Read the associated Release Notes here to understand the changes applied to the qTest Manager 9.8.3-2 patch.
Verify your qTest Manager version
Make sure your qTest Controller (qTest Docker) is working properly and that theqTest Managerweb app is accessible via the web browser.
Using a web browser go to <QTEST_MANAGER_URL>/version, and capture the current JSON value.
Example:
Apply patch for qTest Controller Windows/Linux
Stop the qtest service, and make sure no process is left running from the qtestctl folder.
Windows:net stop qtest
Linux:systemctl stop qtest
Download the provided patch and place it into "qtestctl/.gradle/libs". Make sure to keep the original file name.
".gradle" is a hidden folder on Linux (because there is a dot "." in its name).
You don't need to delete the existing WAR file because you will tell qtestctl exactly which one to use in the later step.
Use a text editor and open "qtestctl/app.config"
Find the version configuration for qTest Manager.
Example:
Change it to the new version, which should be found in the patch name.
Example:
Keep everything else the same and restart the qtest service.
Wait for the web application to be available and double-check the /version resource to make sure the new version has been applied.
Apply patch for qTest Docker
Stop the qtest service, and make sure no container belonging to qTest is left running. Shutdown the qtest application with the following command:
./shutdown
Download the provided patch and place it into "docker-deployment-x.x/dist/qtest/<PATCH-VERSION>/qtest-<PATCH-VERSION>.war". The patch version should be in the original name of the patch package that you have downloaded.
Example:
Use a text editor and open "docker-deployment-x.x/app.config.in"
Find the version configuration for qTest Manager (named "qtest_version") and change it to the new version, which should match with the "PATCH-VERSION" defined in step 2.
qTest Docker has yet to support version range and it uses the exact string compare to find the patch package.
Locate the "cachedir" of your qTest Docker by reading "docker-deployment-x.x/profiles/default.in"
The default value for the "cachedir" if you didn't override it during qTest Docker setup is "/var/cache/qasymphony"
Clean up everything inside the cache directory of qTest Manager, which is "<cachedir>/qtest/"
Keep everything else the same and restart qtest service
Wait for the web application to be available and double-check the /version resource to make sure the new version has been applied.
View Article
9.8.3-2 OnPremise Patch Release Notes

9.8.3-2 OnPremise Patch Release Notes
Module API security fix
API Update: In response to the Module API security fix #35067, we have updated the following API's which enhances security to view/retrieve responses from Projects and requires users to have appropriate Project level-permissions. Therefore, from 9.8.8 and going forward, users will require Project-level permissions for any API and UI actions unless the API is specifically at the Site-level and does not target a specific Project.
Module:
Get Modules: /api/v3/projects/projectId/modules
Get a Module: qtestUrl/api/v3/projects/projectId/modules/moduleId
Permission: Requirement and Test Design Tree
Test Execution:
qtestUrl/api/v3/projects/projectId/test-runs/execution-statuses
Permission: View Test Run
Link Objects:
Remove link objects - Success with link between build and requirements
qtestUrl/api/v3/projects/projectId/builds/newBuildId1/link?type=requirements
Permission Notes:
Build: support requirement
Permission: Edit Release\Build + View Requirements
Release: support requirement
Permission: Edit Release/Build + View Requirements
Requirement: support Test Case
Permission: Edit Requirement + View Test Cases
Test Logs: support Defects
Permission: Edit Test Run
Test Step Logs: Defects
Permission: Edit Test Run
Custom fields
Get fields: /api/v3/projects/projectId/settings/{objectType}/fields
Create custom field: ( release / build / requirement / test case / test suite / test run / defect/api/v3/projects/projectId/settings/objectType/fields
Update system field: /api/v3/projects/projectId/settings/defects/systemfields/6421
Permission: Manage Field Settings
Additionally, the Automation Integration API's listed below will also be affected with this
change and users will need "Automation Schedules" Project-level permissions for the
associated {projectId}:
Create an Automation Agent
POST /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents
Update an Automation Agent
PUT /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents/{agent_server_id}
Delete an Automation Agent
DEL /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents/{agent_server_id}
Activate an Automation Agent
POST /api/v3/projects/{projectId}/automation/hosts/{host_server_Id}/agents/{agent_server_id}/activate
Deactivate an Automation Agent
POST /api/v3/projects/{projectId}/automation/hosts/{host_server_Id}/agents/{agent_server_id}/deactivat
Update a Job’s Status
PUT /api/v3/projects/{projectId}/automation/jobs/{job_id}/status
Requirement Data Query Update
In response to PIR-154, the "Data Query with JIRA fields" enhancement that was released with Manager 9.8 has been modified to reduce the number of database connections. The following changes are applied to the Requirement Data Query:
The "JIRA ID" field has been replaced with the "External ID" field.
In the Criteria drop-down, the "JIRA Issue Type" field has been replaced with the "External Object Type" field. However, users will still see “JIRA Issue Type” in Customize View, Query Results grid and Export.
If there are any saved queries that used the "JIRA ID" or "JIRA Issue Type" fields before, they will be changed automatically without any effect on the query result. The user will also see "External ID" and "External Object Type" in Customize View, Query Results grid, and Export.
JIRA Integration
Atlassian API changes affected the JIRA integration and some users could notcreate new defects from qTest to Jira nor could they save the JIRA connection. Error messages were received when saving the connection "Connection failed. Permissions queries data is required". Issue types linked to JIRA were not visible from the Integration Settings page. This is resolved.
View Article
Sessions 4.3.2 OnPremise February 2020 Release Notes

Enhancements
If user has TA access, there will be TA icon in the 9-box
Added new built-in script generator plugin to generate Flood elements from a recorded session
When selectingExport to ExcelonSubmit Test Casedialog on session review page, the Sessions (P-)ID will also be exported to Excel file
Removed the text "Title:" in the exported Word/PDF/HTML document
Fixed vulnerabilities
Bug Fixes
Ticket #
Component
Description
NA
Session Editor / Submit Defect
Fixed VersionOne Defect Submission: Cannot attach screenshot into the defect
NA
Session Editor / Submit Defect
Fixed VersionOne - Update defect: Always show "Cannot find defect/issue with id: <valid id>
NA
Session Editor / Submit Defect
Fixed Rally Defect Submission: Cannot attach screenshot into the defect
NA
Session Editor / Submit Defect
Fixed Rally Update defect: Always show "Cannot find defect/issue with id: <valid id>
NA
Vulnerabilities
Fixed potential vulnerability issue
View Article
Launch 1.5.6 OnDemand Release Notes - December 26, 2019

Feature Enhancements
When creating custom parser via Launch's settings, the parser will be scanned for virus or malware before processing. This feature only available for On Demand users.
View Article
Parameters 2.2.7 OnDemand December 26, 2019 Release Notes

Enhancements
When importing Parameters or Datasets via UI. The import file will be scanned for virus or malware before processing
When importing Parameters or Datasets via Parameters APIs. The import file will be scanned for virus or malware before processing
View Article
Linking Test Cases and Requirements

Overview
qTest Manager provides essential traceability between test cases and requirements. You can establish this traceability on either the requirement or test case object.
Tricentis recommends the following as Best Practice when linking Requirements to Test Cases, either from within the UI or via API. Note the maximum thresholds and associated impact. These numbers are generalized for providing context.
One Requirement linked to 2,500 Test Cases: expect difficult navigation within the UI at 2,500 and load time will increase.
One Requirement linked to 60,001 or more Test Cases: not recommended as the system will become unstable.
Link Requirement to Existing Test Case
To link a requirement to an existing test case, perform the following steps:
Select Requirements in qTest Manager.
Inthe left navigation panel, expand your module. Then, select the requirement.
In the "Resources" section, selectAdd. The "Test Cases" dialog displays.
Select yourTest Casethat you would like to link to your Requirement. SelectAdd.
SelectSave.
HINT: A requirement can be linked to more than one test case.To quickly link a test case to many requirements, use the SHIFT and/or CTRL key to select multiple Test Cases in the dialog. Then, selectAdd.
Link Requirements to Test Cases Video
Note:For highest quality, watch this video in full-screen mode.
Link Requirement to New Test Case
To link a requirement to a new test case, perform the following steps:
In Requirements,refer to the Create Associated Test Cases area at the bottom of the page.
Enter a name, type, description, and precondition and click the Create button.
The created test case is automatically linked to the requirement and displays in the Linked Test Cases section in the Resources area of the requirement page.
Once the linked test case is created, you can select the test case to add more details.
Link Test Case to Requirements
In addition to linking a requirement to a new or existing test case, you can also link a test case to an existing requirement. Perform the steps as follows:
Select the Test Design.
In the left navigation panel, expand the folder to select the applicable test case.
In the "Resources" area of the Test Case screen, selectAdd.
The "Add Requirements" dialog displays. Select the applicable requirement to link to the test case. SelecttheRequirementstab.
Select the proper Requirement in the dialog. SelectAdd.
HINT: A test case can be linked to more than one requirements. To quickly link a test case to many requirements, use the SHIFT and/or CTRL key to select multiple requirements in the dialog. Then click the Add button.
View Article
Launch 1.5.3 OnPremise Release Notes: July 2019

Enhancements and New Features
Tosca DEX Integration
Launch now offers the ability to schedule Test Executions for Tosca Test Cases. These Test Cases will execute against Tosca DEX. Refer to this article to learn how to schedule test execution for Tosca Test Cases in qTest Launch: Schedule and Kick Off Tosca Test Cases against Tosca Distributed Execution Server
View Last Execution Logs of a Scheduled Job
Users are now able to view last execution logs of a scheduled job.
Filter Schedule Job by Name and Statuses
When viewing jobs in the JOBS view, you can now quickly search for schedules job(s) by name, status or last run status.
Enhanced Job Detail Screen
The Job Detail Screen now offers users the ability to take quick actions within the scheduled job. These actions include:
Cancel
Delete
Delete occurrence
Delete series
View and copy last execution logs
Performance Upgrades
Filtering
You can now filter Hosts and Jobs by multiple projects. This allows for quicker and more efficient Job and Host management.
Summary and Scheduling
The Execution Summary and Job Scheduling have also been enhanced to be faster and more user-friendly.
Bug fixes
Ticket #
Component
Description
27389
Parser
Postman JSON parser now correctly handles the parent-children structure of test results.
27653
Scheduling
Shared automation test cases are now showing in Launch for test scheduling.
25276
Universal Agent
All Universal Agent parsers now support wildcards specified in thePath to Resultfield.
27798
Parser
The Tosca parser has been enhanced. You can now execute multiple automated test suites or test folders from within Tosca and have results successfully created in qTest.
29394
Session Termination
There are no longer issues with user sessions terminating unexpectedly.
NA
Security
Fixed security issue.
NA
Jobs
Users can now delete a scheduled job.
NA
UI
Fixed broken layout on low resolution screen
NA
UI
Wrong dialog message when cancelling a DELETED job. This has been fixed
NA
UI
When all test runs associated with a job were deleted, the job detail view should change color of Schedule name from blue to red. The Result Folder should also change color from blue to red too
30816
Parser
Fixed NUnit parser to cover the case where multiple test-suite tags are presented in the results
View Article
Batch Actions

Overview
Batch Actionshelp administrators manage and modify potentially large groups of users simultaneously. You will find the Batch Action icon on the License Information page.
The Batch Actionsinclude:
Assign projects
Reset Passwords
IMPORTANT:Resetting a user's password will reset all of that user's tokens.
Export Users
Update Users
Activate Users
Deactivate Users
Resend Invite Emails
Why Use Batch Actions?
Some Administrators may be in charge of very large numbers of users and having to act upon each of these users one by one can become very costly. Batch Actions can vastly cut down the time administrators spend when modifying users and their information in qTest.
Prerequisites
Users will need to be a Site Administrator in order to be able to access the Administration features and use Batch Actions.
Assign Users to Projects: Use Case
If a Site Administrator wants to assign multiple users to multiple projects using theBatch Actionfeature, follow these steps:
In qTest Manager, selectAdministrationfrom the username drop-down menu.
TheLicensestab page displays. Here, select the checkbox(es) associated with the users whom you want to be added to your project(s).
Select theBatch Actionicon.From the drop-down menu, selectAssign to Projects.
The "Add Users to Projects" dialog displays. Select the Project(s) from the menu on the left, and then select theright arrow.
SelectSave.Your selected users have now been added to the selected project(s).
Bulk Edit User Profiles: Use Case
Site Administrators can also bulk edit User Profiles for one user across multiple Projects. This is helpful for adding a user to multiple Projects, while also managing their User Profiles (which might vary based on the Project.)
For example:
Edit Projects and Profiles:
Allows you to update the user's User Profile on a per Project basis.
This can also be used for adding this individual user to other Projects.
User Authentication: Use Case
Site Administrators can batch manageUser Authentication.The following actions can be performed in batches:
Admins can import user info from an XLS file allowing you to change authentication system information.
Admins can save the external username of an internal user. That way, you can reuse these usernames if there is a switch from LDAP to SSO authentication. Previously, these external usernames were not imported when changing the authentication system, and if changing back, the admin had to re-enter external usernames.
Users are automatically activated when an admin changes their authentication system from Internal to LDAP/SSO using the import tool.
Update Users (Import) Batch Action
TheBatch Actionassociated with updating user information allows site administrators to export an Excel file from qTest. Users can then modify the Excel file and re-import the file into qTest. The imported file differs from the exported file, and columns will need to be removed from the exported file, to accommodate the acceptable import file format.
The imported file is scanned for viruses or malware. If the file is clean, it is processed and users will see results after the import is done.
If the file is infected or the scanning service is down, then an error will be shown on the Import dialog:"Some of the imported file(s) are found virus or malware infected and cannot be processed. Please remove the infected file(s) to proceed."
qTest will read the file and can update the following user information accordingly:
Email
First Name
Last Name
Auth system
SSO username
LDAP username
Status
Note:If an internal user was once authenticated by an SSO system, his or her old SSO username would be included in the export file.
Admins can also check logs for exact error reports for each user. These logs can be exported into Excel, modified, and then re-imported back into qTest Manager to send an invitation with the correct information.
Example Use Case:
When changing the authentication system from LDAP to SSO, in most cases, SSO usernames will be the same as LDAP usernames. The site admin may want to export users with LDAP usernames first and then re-use the LDAP usernames as SSO usernames.
In qTest, enabling SSO will automatically disable LDAP, and all LDAP usernames are cleared out. In this case, the site admin should export users BEFORE disabling LDAP or enabling SSO.
View Article
Importing Requirements Using Excel Import

Overview
qTest Manager allows you to store requirements so tha t testers can easily access information for test coverage. You can create RequirementsorImport Requirements.
Note:Many users will have already created requirements in another tool, such as JIRA. To import Requirements from an external tool using an out-of-the-box integration, see the following articles.
Import Requirements from JIRA
Import Requirements from Rally
Import Requirements from VersionOne
Even if you import requirements from an external tool, you can still separately manage requirements that are not integrated.
Note:If you import requirements from Excel, these requirements will be created in qTest Manager without being integrated with these external tools.
Create New Requirements Using Excel Import
You can import requirements from an Excel spreadsheet. This feature can be useful if you prefer not to create each requirement one at a time in the interface. ToImport Requirements, we recommend using the Sample Import Template.If you already have requirements in a different spreadsheet, you will need to modify the spreadsheet to mirror the Sample Import Template format so fields can be mapped properly into qTest Manager.
HINT: If you want to create requirements with custom fields or values, make sure to create custom fields or modify any system fields in Field Settings first. For more details, see the Field Settings article.
To import requirements from the template, perform the following steps.
Select the Requirements module. The Requirements page is displayed.
Click the Import Excel icon, located in the left panel.
Field Settings
The Import Requirement Wizard pop-up is displayed. Click the Sample Import template link (located in the second paragraph of the Import Requirement Wizard) to download the Sample Import template.
Fill out the spreadsheet, entering the Requirement ID, Requirement Name, requirement text, requirement status (i.e., New, etc.), tester assigned to the requirement, requirement priority, and requirement type (i.e., functional, non-functional). If you wish, you can create custom fields on the spreadsheet.
Save the Excel file.
On the Import Requirement Wizard pop-up window, select the click here to pick from a folder link.
Drag and drop the Excel file or select the applicable file from a folder to import it into qTest Manager. The file must be in the .xls or xlsx format. Click the Next button on the Import Requirement Wizard pop-up window. The Import Requirement Wizard redisplays.
Drag and drop the column names from the imported spreadsheet next to the corresponding qTest Manager requirement field to complete the field mapping. If you are importing new requirements, do NOT map the Requirement ID, since qTest Manager will system-generate an identifier to each requirement you import.
HINT: Tocreate requirements with custom fields or values, make sure to create custom fields or modify any system fields in first. Otherwise, those fields cannot be mapped in the Import Wizard.
Click the Import button to import the spreadsheet into qTest Manager.
When an Excel file is being uploaded, a loading icon will be shown that when hovered over will advise: "The file is being scanned for virus and malware before being processed."Upon clicking the Next button: "Imported file(s) are being scanned for virus and malware. Please wait until the scanning process is done to proceed."
When the imported file is scanned successfully and is "clean", you can proceed to the mapping step. If the imported file is scanned successfully and is "infected", the file name will show as:(Infected) filename.xls.
Upon clicking the Next button, a message will display: "Some of the imported file(s) are found virus or malware infected and cannot be processed. Please remove the infected file(s) to proceed." If multiple files are being imported and at least one of them is "infected", you will be unable to import any of the files until the infected ones are removed.
If the imported file fails to be scanned, an error message will display and the import process will stop: "The file cannot be scanned for virus or malware at the moment. Please try again later."
Modify Existing Requirements using Excel Import
You can upload changes to requirements that currently exist in qTest Manager by using an Excel import. To do this, export requirements from qTest Manager into an Excel file. Edit the file in Excel and then import the file to qTest Manager to update existing requirements. This functionality enables you to upload all updates at one time, rather than modify one requirement at a time in the qTest Manager interface.

The process is similar to importing new requirements from an Excel file only there are some important rules to keep in mind.
To determine the Module ID, click theToggle icon on the top toolbar of Requirements, next to theExport Requirement Reports icon and check to toggle Modules.
Make sure to enter the correct Module ID and Module Name you want to import for the Excel sheet name. Otherwise, the system cannot find the right Module you want to import/update.
Although qTest Manager supports the Module name's length of up to 500 characters, the Excel sheet name is limited to 31 characters. Therefore, do not enter a long Module name.
An easy way to start modifying existing requirements is to first export theRequirements Detail Report from the toolbar above the left navigation panel in the Requirements tab. The downloaded Excel file will show the existing content which you can continue to modify in the Excel file before uploading it back to qTest Manager with the updated information.
When importing information in an Excel spreadsheet to update an existing requirement, you must map the exact Requirement IDs to indicate which requirements you are updating. The Requirement ID is displayed in an individual requirement at the top of the page, as shown in the following screenshot.

The Requirement ID can also be displayed in front of the requirement name in the left panel by selecting the Toggle IDs display icon (the top right icon in the left panel) and selecting the Requirements checkbox from the pop-up window. The ID appears in front of the requirement name in the left panel.

The Excel sheet name you are importing must include the Module ID and Folder Name and must not exceed 31 characters. To update requirements in the MD-25 Untitled folder (see the screen shot below), the sheet name should be the content inside the brackets:<MD-25 Untitled>. The Module ID can be displayed in front of the Module Name in the left panel by selecting the Toggle IDs display icon and selecting the Modules checkbox from the pop-up window.

IMPORTANT: If you do not map Requirement IDs, but rename the Excel sheet by Module ID + Name, you will add new requirements into existing modules. If you map requirement IDs with an incorrectly mapped Module ID / Name in the Excel sheet name, qTest Manager will generate an invalid Requirement ID Value error and the import will fail.
View Article
Importing Test Cases Using Excel Import

Overview
In qTest Manager, you can import test cases from an Excel spreadsheet to create new test cases as well asto make changes to existing test cases. While there is an Example Sample Template, any column value can be mapped to a custom field within qTest Manager, as long as the test cases and steps are individual rows. Our import wizard provides the ability to import test cases directly into specific modules by altering the Excel file's individual sheet names to align to the modules within qTest Manager.
Importing Test Cases
Importing Test Cases from Excel consists of the following steps:
Download the Sample Import Template.
Fill out Test Case information on the Sample Import Templateinside Excel.
Adjust Field settingsas needed in qTest Manager.
Import the Excel file to qTest Manager.
Download Sample Import Template
To import Test Cases from the Sample Import Template, perform the following steps:
SelectTest Design, and then select your project.
Field Settings.
Select the Import Excel icon in the navigation panel.
The "Import Test Case Wizard" dialog displays. Select theSample Import Templatehyperlink.
Fill Out Sample Import Template Inside Excel
Fill out the Sample Import template by entering the Name, Type, Status, and Description of the test case. If you wish, you can create custom fields on the spreadsheet. Save the Excel file.
Make sure the field values on the spreadsheet match the available values in qTest Manager. If the values do not match, you must add the values for these fields in Field Settings within qTest Manager. For additional information, refer to the ‘ Modify System Field ’ user guide.Similarly, if any columns in the spreadsheet represent a field that does not exist in Field Settings, you must first create the custom field in qTest Manager and assign the values for the field (if the field is a combo-box field type) so the import runs smoothly. For more information, see the ‘ Add Custom Field ’ article.
IMPORTANT:If you plan to report on these custom fields using qTest Insights, make sure to make the field settings changes at the Site Level and not the Project Level. Custom fields added at the Project level cannot be reported on within qTest Insights. For information on Site-level field changes, please refer to our Site Fields Article.
Hint:If you are uploading data to a multiple selection combo box or a checkbox field, you can include multiple values by separating each value with a comma: 1,2,3,4. Do not include spaces between the values.
Adjust Field Settings As Needed
In the following example, the Type field in qTest Manager has four existing values in qTest Manager: Manual, Automation, Performance, and Scenario.
The Excel spreadsheet shown below contains two test cases. In Test Case 003 the value ‘Manual’ for the Type field matches an existing value for this field in qTest Manager. However, in Test Case 004, the value ‘New Value’ for the Type field does not match an existing value for this field in qTest Manager.
Add Custom Fields for Your Test Case in qTest Manager
Select theSettingsicon and then select
The Edit System Field Page displays. SelectTest Casein the artifacts panel.
SelectTypein the "Display Name" column.
SelectAdd Value and add a value called ‘New Value’ for the Type field. Then, click the OK button.
Import Excel File to qTest Manager
After you have modified any existing system fields or added any new custom fields in Field Settings in qTest Manager, perform the following steps to import the Excel file to qTest Manager:
SelectTest Design in qTest Manager. The Test Design page displays.
Select your Project.
Select theImport Excel icon, located in the navigation panel.
The "Import Test Case Wizard" dialog displays. To use your own custom spreadsheet, drag and drop your file into the file upload box or select theclick here to pick from a folderlink.
HINT: If you want to import the test cases into an existing folder, then before importing, make sure to update the Excel sheet’s name to match the existing folder, using the syntax: MD - ## and the Folder name. As shown in the screenshot below, the syntax MD-27 is located next to the folder name Existing Folder in test design.
In this example, the spreadsheet’s sheet name has been updated below to be called MD-27 Existing Folder so the test cases will be imported into this folder.
Ifyou do not wish to import the test cases into an existing folder, leave the sheet name empty and the import process will create a new folder.
When an Excel file is being uploaded, a loading icon will be shown that when hovered over will advise: "The file is being scanned for virus and malware before being processed." Upon clicking the Next button: "Imported file(s) are being scanned for virus and malware. Please wait until the scanning process is done to proceed."
When the imported file is scanned successfully and is "clean", you can proceed to the mapping step. If the imported file is scanned successfully and is "infected", the file name will show as:(Infected) filename.xls.
Upon clicking the Next button, a message will display: "Some of the imported file(s) are found virus or malware infected and cannot be processed. Please remove the infected file(s) to proceed." If multiple files are being imported and at least one of them is "infected", you will be unable to import any of the files until the infected ones are removed.
If the imported file fails to be scanned, an error message will display and the import process will stop: "The file cannot be scanned for virus or malware at the moment. Please try again later."
SelectNext.The Import Test Case Wizard redisplays. The fields in the ‘Available fields for mapping’ area at the top of the screen are the fields in the Excel spreadsheet. The fields in the ‘qTest’s Test Case Fields area in the left column of the screen are the fields in Field Settings in qTest Manager.
To perform the field mapping, drag and drop each column name from the ‘Available fields for mapping’ area to the ‘Imported Spreadsheet’s Columns’ in the right column, to the right of the corresponding qTest Test Case field.
IMPORTANT: Do not map the Test Case ID. qTest Manager will auto-generate this value.
HINT: The Excel column name and corresponding qTest field name do not have to match. For example, if the Excel column is called ‘Test Case Status’ and the qTest field is called Status, that’s fine.
SelectImport.
The following screenshot shows the newly created folder with the uploaded test cases and the test cases we imported into our existing folder.
Modify Existing Test Cases Using Excel Import
You can upload changes to test cases that currently exist in qTest Manager by using an Excel import. To do this, export the test cases to Excel. Then, edit the file in Excel and import the file to qTest Manager to update existing test cases. This functionality enables you to upload all updates at one time, rather than modify one test case at a time in the qTest Manager interface.

When importing information in an Excel spreadsheet to update an existing test case, make sure the spreadsheet contains the Test Case ID so that qTest Manager updates the correct object. The process is similar to importing new test cases from an Excel file only there are some rules to keep in mind.
An easy way to start is to export the Test Case Detail report from the top of the left navigation panel in Test Design. Update the content in Excel and save the changes in Excel before importing the updated file into Test Design.
When importing information from an Excel spreadsheet to update an existing test case, you must map the exact Test Case IDs to indicate which test cases you are updating. The Test Case ID is displayed in an individual test case at the top of the page, as shown in the following screenshot.

The Test Case ID and Module ID can also be displayed in front of the test case name in the left panel by selecting the Toggle IDs display icon (the top right icon in the left panel). Select the Test Casesand Modulescheckbox from the dialog. The ID appears in front of the Test Case name in the left panel.

The Excel sheet name you are importing must include the Test Case ID and Folder Name and must not exceed 31 characters. Use the form Test Case ID space Folder Name as your sheet name. For example: MD-23 Login Process.

IMPORTANT: If you do not map Test Case IDs, but rename the Excel sheet by Module ID + Name, you will add new Test Cases into existing Modules.If you map Test Case ID's with an incorrectly mapped Module ID/Name in the Excel sheet name, qTest Manager will generate an invalid Test Case ID Value error, and the import will fail.
View Article
Launch 1.5.5 OnDemand Release Notes - December 19, 2019

Enhancements
If user has access to Tricentis Analytics, there will be Tricentis Analytics icon in the 9-box.
View Article
OnPremise Product and Integrating App Compatibility

Overview
Below displays compatibility between qTest OnPremise versions and integrating Applications.
For additional information on the JIRA integration versions and download links, visit the Atlassian Marketplace.
Read these important release notes for add-on versions6.11.14 and8.0.4.
qTest
Tosca
Tricentis Analytics
Rally/
Version One/
JIRA Cloud
JIRA Server/
JIRA Server Add-on
JIRA Data Center/
JIRA Data Center Add-on
9.8.3
Tosca Server
12.0, 13.0.715
1.4
The latest OnDemand version
8.0-8.5.1 = 8.0.4
8.0-8.3.1 = 8.0.3
8.0-8.2.1 = 8.0.2
7.7-7.13.11 = 6.11.14
7.5-7.13.5 = 6.11.13
7.5-7.13.5 = 6.11.12
8.0-8.5.1 = 8.0.4
8.0-8.3.1 = 8.0.3
8.0-8.2.1 = 8.0.2
7.7-7.13.11 = 6.11.14
7.5-7.13.5 = 6.11.13
7.5-7.13.5 = 6.11.12
9.7.1+
Tosca Server 12.0, 12.1, 12.2, 12.3
1.3.1
The latest OnDemand version
8.0-8.5.1 = 8.0.4
8.0-8.3.1 = 8.0.3
8.0-8.2.1 = 8.0.2
7.7-7.13.11 = 6.11.14
7.5-7.13.5 = 6.11.13
7.5-7.13.5 = 6.11.12
8.0-8.5.1 = 8.0.4
8.0-8.3.1 =8.0.3
8.0-8.2.1 =8.0.2
7.7-7.13.11 = 6.11.14
7.5-7.13.5 =6.11.13
7.5-7.13.5 = 6.11.12
9.6.1+
Tosca Server 12.0, 12.1, 12.2
12.2
The latest OnDemand version
8.0-8.2.4 =8.0.1
7.5-7.13.5 =6.11.11
8.0-8.2.4 =8.0.1
7.5-7.13.5 =6.11.11
9.5.3+
Tosca Server 12.0
NA
The latest OnDemand version
8.0.0-8.0.3 = 8.0.0
7.4.0-7.13.5 = 6.11.10
NA
9.1.4+
NA
NA
The latest OnDemand version
7.3-7.13.5 =6.11.9
NA
*NOTE:Tricentis Analytics version numbers were updated beginning July 2019, associated with the qTest 9.7.1 OnPremise deployment, to reflect new features for qTest reporting capabilities. Therefore, the version of Tricentis Analytics 1.3 is accurate in the table above.
View Article
Scenario 3.3.0 OD Release Notes

December 12, 2019
Enhancements
OAuth Authentication
qTest Scenario now supports OAuth integration with JIRA Server and JIRA Data Center. For more information on how to configure qTest Scenario with OAuth, please refer to this article.
NGINX Configuration
qTest Scenario now supports configuration with NGINX as a reverse proxy. For more information on configuring Scenario to work with NGINX, please refer to this article.
View Article
Parameters 2.2.6 OnDemand Release Notes

December 19, 2019
Bug Fixes and Improvements
Ticket #
Component
Description
34100
Parameter
Project being removed from Parameter: Previously, when a user edited a Parameter, including associating the Parameter to the Projects they have permissions in, the Projects that were previously assigned to the Parameter were removed when the Parameter is saved. This resulted in other users, who have permissions in the Projects where the Parameters were previously assigned, to not be able to use the Parameter anymore. This issue has been fixed.
NA
Security
Fixed potential security issues.
View Article
Integration with VersionOne

Overview
qTestManager's integration with VersionOne allows for teams to see full traceability between test runs,VersionOne requirements, and defects.
qTest Manager currently supports integration with VersionOneOnDemand for submitting Defects to VersionOneand import Requirements from VersionOne. You can add as many connections with VersionOneOnDemand but only one connection is active at a time.
How to Get Here
In the Project you are integrating with VersionOne, select the Gear icon and chooseIntegration Settings.
Select VersionOne in the External Systems section and the Configure Integration page loads.
Select theAdd VersionOne Connectionbutton.
Setting upthe Connection
There are two methods to configuring your connection:
VersionOne without SSO enabled
VersionOne with SSO enabled
VersionOne without SSO enabled
In the Add VersionOne Connection dialog, enter the required information for the connection:
Connection Name
V1 Server URL
V1 Account Credentials
Insights
Select theTest Connection icon to check the server availability.
Select theSave & Configure iconafter a successful connection test.
Now, you can configure the integration with V1for defects and requirements.
For anew Connection, the "Configure Connection" Page will display after you select Save & Configure.
For anexisting Connection, select theConfigureicon of that connection to open the "Configure Connection" Page.
After configuring Defect and Requirement integration, select Save & Activate.
SelectRefresh on the "Confirmation" dialog. Your newly configured connection will be activated. The Activation StatusisOnand your configured connection is checked as Active in the Connection List.
After your V1 Connection integration is successfully activated, it will be notified with a green status label "in use" next to VersionOne (On-demand), and the Defect menu will be hidden. Thus, the only way to submit a defect is through Test Execution.
To edit your connection, select the Configure icon of that Connection in the Connection List.
You can delete your V1 connection in the Connection List by selecting the Delete icon in the Actions column.
VersionOne with SSO Enabled
Read these instructions on how to generate a VersionOne access token before attempting to establish a connection with SSO.
In the Add VersionOne Connection dialog, enter the required information for the connection:
Connection Name
V1 Server URL
Username=apikey
Password=VersionOne access token
Select theTest Connection icon to check the server availability.
Select theSave & Configure iconafter a successful connection test.
You can start to configure integration with V1for defects and requirements.
For anew Connection, the "Configure Connection" Page will display after you select Save & Configure.
For anexisting Connection, select theConfigureicon of that connection to open the "Configure Connection" Page.
After configuring Defect and Requirement integration, select Save & Activate.
SelectRefresh on the "Confirmation" dialog. Your newly configured connection will be activated. The Activation StatusisOnand your configured connection is checked as Active in the Connection List.
After your V1 Connection integration is successfully activated, a green status label of "in use" appears next to VersionOne (On-demand) in the External Systems panel. Additionally, the Defect tab will be hidden in Manager. Thus, the only way to submit a defect is through Test Execution.
Connection Maintenance
To edit your connection, select the Configure (wrench) icon of that Connection in the Connection List.
You can delete your V1 connection in the Connection List by selecting the Delete icon in the Actions column.
Configuring Defects with VersionOne
After you successfully set up the connection with your V1 OnDemand instance, you can set up defect integration.
IMPORTANT:
You can set integration with multiple V1 projects.
You can select multiple V1 object types to map as qTest Manager Defects.
qTest Manager requires you to have at least one project and object type selected.
Mapped V1 objects will be treated as Defects in qTest Manager.
To configure Defects Integration with V1
Go to theConfigure Connectionscreen after a successful Connection Set-up.
In Defect Integration, selectAdd Defect Type.
SelectVersionOne ProjectandVersionOne Object typefrom the drop-down lists.
In theActioncolumn of the Defect Integration's Mapping list, select theConfigureicon to configure individual mapped Defects.
TheEdit Auto-Fillingform displays. By default, qTest Manager will load all available fields of the mapped V1 object type onto the Defect Field column.
SelectReset Fieldsto reload the latest Field Settings of the mapped object type.
Select theRepopulateicon in the Action column of each Defect field to reload the latest values of individual fields from V1.
Select theDeleteicon to remove the display of specific fields from the qTest Manager defect submission form. Those deleted fields are still on the V1 form.
Use theMove UpandDownarrows to re-arrange the display of defect fields in the qTest Manager defect submission form. Their positions remain unchanged in the V1 form.
Select theAdd Fieldbutton to manually add fields that can't be automatically populated from V1 to qTest Manager.
SetAuto-Fillingfor mapped V1 object type's fields. qTestManager will auto-fill data fromTest RunorTest Caseinto the mapped V1 object's field as settings.
Select a defect field to open theEdit Field Screen.
Edit the field as your own style, such asrequiredor field type.
Check theAuto Filloption in Input Option or you can setDefault Valuefor field.
Select theAddicon to add a field for mapping.
Select theDrop-downicon to select a qTest Manager field to map to V1 field.
Select theOKicon to finish your mapping configuration.
HINTS:
The values of mapped input and output fields must be symmetric between V1 and qTest Manager.
Only fields in Text format can be auto-filled.
You can select to fill multiple qTest Manager fields into one V1 field.
Retrieving Requirements from VersionOne
Configure Requirement Integration with VersionOne
Users can optionally turn the Requirement Integration feature on to retrieve V1 objects and import into qTest Manager as Requirements.
To configure, follow these steps:
Turn ON the Requirement Integrationfeature to activate.
Select theAdd Requirement Typebutton.
The Add Issue Types modal displays.
Select the down-arrow to the right ofThe VersionOne project field to expand the drop-down list. Select the applicable VersionOneproject from which you will import requirements to qTest Manager.
Select the down-arrow to the right of the VersionOneObject types field to expand the drop-down list. Select the object type you use to represent requirements in the VersionOne project selected above (e.g., story, feature, epic, task, work item). This procedure will retrieve that object type, so it is imported into qTest Manager as Requirements.
HINT: The purpose of this step is to identify the object type from the VersionOne project and import that object type into qTest Manager as Requirements.
SelectOK to save, and aline item is now visible in the Requirement Integration area of the Configure Connection page.
Details include:
the name of the VersionOneProject you selected
the associated VersionOneobject typeyou selected
Edit Data Retrieval
Now, you need to edit how qTest is going to retrieve your VersionOne data.
Position the cursorinto the ACTION column, of the new line, which indicates the VersionOne Project and VersionONe Object Types you want to edit the data retrieval. Three icons are displayed but select the middle icon, the wrench.
The Edit Data Retrieval screen loads and you can configure three things, (more information is provided in the sections below.)
Establish how requirements from VersionOne will be organized, based on one or two VersionOne fields.
Select the VersionOne fields you wish to display in qTest Manager.
Organize into Folder Structure
By default, the Requirements from VersionOne are imported into one 'Imported from VersionOne'folderin qTest Manager, resulting in a flat structure.
We do not recommend using this default structure for Requirements.
Therefore, you can organize your imported Requirements, using up to two VersionOneObject fields,which results in a nested folder structure below the standard 'Imported from VersionOne' folder.
The screenshot below shows a two-level structure of V1 requirements, meaning that your V1 object fields have been selected for organizing your Requirements. We strongly recommend using this structure for requirements.
To organize your Requirement folders, do the following:
In the Select fields to organize imported Requirementssection, select the arrow to the right of Field 1 and choose the desired V1 field in the drop-down list, such as Portfolio.
Select the arrow to the right of Field 2 and choose the desired VersionOne Issue field in the drop-down list, such as Build.
The steps above enable you to create a 2-level folder structure to help organize your imported requirements according to the two V1 object fields selected here.
NOTES:
If you select only one V1 object field to organize your Requirements folders, then you will have a one-level folder structure under the default Imported from V1 folder.
If you select a V1 object field for folder organization, that can have more than one assigned value in V1(multi-selection), then the folder name that is created will include:
all values assigned to the Requirement of the selected V1 object field
and the values will be separated by a semicolon ' ; '
Example:
selected V1 object field = 'Component'
'Component' values assigned to this V1 Requirement= Database and API
Folder name= Database;API
In the following example, the ‘Portfolio Item’ object has been selected in Field 1, and the‘Build’ object selected in Field 2.

IMPORTANT: Using the integration, qTest Manager willpoll V1 every two minutes to get the updated + new objects. You have toRe-select,Reload, orRefreshto get the updated data of V1 objects you are standing onafter the initial import (e.g., move requirement from In Progress to Done folder.)
Select VersionOne Fields to Displayon Requirements
The V1 fields you select here will beaccessible to testers for informational purposes. They display in the V1 Properties-Read Only section of the Requirement page in qTest.
The following image shows multiple V1 fields displayed. We highly recommend using this approach.

This image shows the bare minimum of fields displayed. We do not recommend using this approach.
To select the V1 fields to display on your Requirements, do the following:
In the V1ISSUE FIELDSsection, select any additional data from V1 you want to import to qTest Manager, such as the Fix Version and Priority.
To select a field, select the ACTIVE check-boxfor the item.
Note: We recommend checking all the checkboxes to import all of this data into qTest Manager.
HINT: For each qTest Manager Project, you can customize the V1 fields to show in the Requirements page of qTest Manager. The fields you use in one project may differ from the fields used in another project.
SelectOK and the Edit Data Retrieval modal closes.
Save and Activate the VersionOne Requirement Integration
Once the Edit Data Retrieval modal closes, you MUST select theSave & Activatebutton (which is located at the top right) on the Configure Connectionpage.
The CONFIRMATION pop-up window displays.
SelectRefresh and the Configure Integration page displays.
Select theRetrieve VersionOne Data button. This is a manual process to kick off the integration connection to initially pull your data.
The EXTERNAL ISSUES RETRIEVING PROGRESS pop-up window displays. A progress bar is visible in the window.
When qTest Manager has imported all V1 requirements, a confirmation message is displayed.
SelectOK. The requirements which were created in V1 will be accessible to testers in read-only form in qTest Manager.
HINT: You can retrieve data of all V1 object types or any specific types you map.
Select theRetrieve VersionOne Dataicon to populate the latest data of all mapped V1 object types.
Select theRe-Populateicon to get the latest data of a specific mapped V1 object type.
In specific imported V1 imported Requirements in qTest Manager, selectRetrieve datato reload the latest data of that V1 object.
View Imported VersionOne Requirements
Imported VersionOne objects will be treated asRequirementsin qTest Manager.
By default, these integrated requirements will be loaded into a common Module folder named"Imported from VersionOne"as shown below.
IMPORTANT:
Imported V1 objects are represented by special integration icons to differ from internal qTest Requirements.
An imported V1 object has two Properties sections - VersionOne's PropertiesandqTest's Properties
V1's Properties containActiveV1 object fields configured on theEdit Data Retrievalscreen. These Properties areRead-only. qTest Properties contain all qTest Manager Requirement's fields, excludingDescription.
qTest Manager will poll V1 every two minutes to get the updated + new objects. You have toRe-select,Reload, orRefreshto get the updated data of V1 objects you are standing on.
Imported V1 objects can be copied or moved across Modules within a qTest Project to re-organize Module Structure.
Copied objects will become qTest Requirements which only retain theDescriptionof V1 objects.
Moved objects' Properties will remain unchanged.
Imported V1 objects can be associated to qTest Manager Test Cases.
V1 IDs of imported objects will be included in theRequirements and Test Execution Results Report
HINT:
An object in V1 has two different types of ID - the display ID and the OID. Those IDs are displayed in qTest as shown below.
Linking Test Caseswith VersionOne Requirements
Imported V1 objects can be linked to qTest Manager Test Cases. The linking with qTest Manager Test Cases will be generated in the corresponding V1 object's Links section.
When you link or create associated Test Cases to an Imported V1 object, qTest Manager also generates a link under the corresponding V1 object.
Submitting Defects to VersionOne
You can submit defects to V1 from qTestManager during TestPad Execution or from the Test Log.
Select theBugiconlinked to Test Steps orSubmit Defectlinked to a Test Run in the TestPad.
You can also select theBugiconin the Execution History and Test Log Details sections to create defects.
Select theNewbutton to create a newDefect.
Select one of the configured V1 object types to submit the Defect.
The Mapped Project will be attached before the Defect Type and auto displayed in the Project drop-down list, corresponding to the selected Defect Type.
The Defect Submission form loads.
If you have theqTest Integration Browser Plugininstalled, qTest Manager will open theVersionOne Defectform. You must log in before submitting defects.
If you DO NOT install the browser plugin, qTest Manager will open theqTest Defect Submissionform with integrated fields from V1.
Defect fields will be auto-filled as configured
The system will return theDefect ID and Summaryfrom VersionOne that is attached to theBugicon.
HINT:
An object in V1 has two different types of ID - the display ID and the OID. Those IDs are displayed in qTest as shown below.
Review VersionOne Defect After Submission
From V1, you can see the link to the qTest Test Run in the Link section of the defect.
Review VersionOne Defects in Manager
InqTestTest Execution, you can find V1 defect information in many areas:
Test Run page:
To view V1 defects in a particular Test Log, select the defect icon from the Execution History grid.
For an aggregate list, select the Defects tab for a roll-up of all V1 defects related to any of the test logs of the Test Run. The Defects tab can be customized so you can display additional V1 Defect fields as columns.
Test Suite, Cycle, and Release pages:
To view V1 defects for a single Test Run, select the Defect icon from the Test Run grid.
For an aggregate list, select the Defect Summary tab for a roll-up of all V1 defects related to associated Test Runs. This Defect Summary tab can be customized so that you can display additional V1 Defect fields as columns.
For advanced reporting, use qTest to gain more defect visibility.
View Article
Develop Custom Test Result Parser for Universal Agent

Overview
When you configure the Universal Agent to execute your test project, you have an option to choose a parser, which will translate the test results generated by your test project to a unified format defined by the Automation Host. The output of the parser will then submit to qTest Manager as test run logs.
Currently, there are built-in parsers available from qTest Launch that will parse these test result formats:
JUnit for Java
Tosca JUnit
Postman Json
Postman JUnit
Allure Results
Unified Functional Testing (UFT)
Cucumber JUnit
JMeter
NUnit
Universal Agent Settings
If your test project generates test results under a format that these built-in parsers do not support, you can create your own parser and upload it to qTest Launch under Universal Agent Settings.
The Automation Host will download these parsers and they will be available for you to choose when you create or configure your Universal Agent.
Prerequisites
Since parser is implemented in NodeJS, you are expected to have some knowledge of NodeJS development in order to build your own custom parser.
Steps to create a custom parser:
Install NodeJS to your development machine
Create a NodeJS application
Implement the parser
Package the parser
Upload the parser to qTest Launchunder Universal Agent Settings
Install NodeJS to your Development Machine
Notes:
Since the Automation Host already bundles NodeJS in order to execute the parser, you do not have to install NodeJS in the machine that the Automation Host is running.
For the development machine, it is highly recommended you install the same NodeJS version as the one being bundled with Automation Host, which is 8.11.3 LTS.
Follow this link to download and install NodeJS: https://nodejs.org.
Tips: if you want to manage multiple node versions on your machine, we recommend you to try nvm.
After installing, open the Command Prompt on Windows (or Terminal if you're on Linux or Mac) then execute the commandbelow and make sure you see an output like this:
node --version
v8.11.3
Create NodeJS Application
Create a directory on your machine with the name of your custom parser. You can choose whatever name you want. For this article we will use my-custom-parser.
Open a Command Prompt (or Terminal if you're on Linux or Mac), and navigate to 'my-custom-parser' directory and execute the command below to initialize the NodeJS application:
npm init
This is an interactive command that will ask you for information about your NodeJS project. So make sure you enter the appropriate information for this parser.
Once finished, the command will create a package.json file inside your 'my-custom-parser' directory.
Now you can install any node modules that your parser needs with the `npm install` command:
npm install <node module name> --save
Next, create a JavaScript file namedparser.jsin your NodeJS project. This file is the implementation of your parser and it has to be named parser.js.
Open your 'my-custom-parser' NodeJS project in your preferred IDE, then copy and paste the code snippets below to parser.js.
/**
* Description of your custom parser
*/
"use strict"
const fs = require("fs");
module.exports.parse = (pathToTestResult, options) => {
return new Promise((resolve, reject) => {
if (!fs.existsSync(pathToTestResult)) {
return reject(new Error(`Test result not found at ${pathToTestResult}`));
}
// implement the parser from here
// ..
});
}
Now your project will look something like the example below.
As you can guess from the code snippet, your parser implementation logic starts from these lines:
// implement the parser from here
// ..
Implement the Parser
Understanding the parse() Function
module.exports.parse = (pathToTestResult, options)
The parser implements a module that exposes a parse(...) function. This function accepts 2 parameters: pathToTestResult and options.
pathToTestResult parameter
This parameter carries the path to the test result(s) generated by your test project. It has the value of thePath to Resultsfield that you configured in the Universal Agent.
The possible value of pathToTestResult can be one of the following:
An absolute path to the directory where one or multiple test result files are generated. For example, TestNG can generate multiple XML test results file inside a specific directory. So the path could be like this: /path/to/your/testng-project/target/surefire-reports
An absolute path to a test result file, e.g. newman command line tool saves test results to a file after executing Postman tests, and so the value could be something like this /path/to/your/postman-project/test-result.json
options parameter
This parameter is for extensibility purposes and you should ignore it at this moment.
function output
The parse function must return an output under a format defined by the Automation Host. The Automation Host, in turn, will submit the output to qTest Manager as test run logs. The output is a literal JavaScript object which can be easily transformed to JSON in order to submit to qTest Manager.
Basically, the output is an array of test case objects:
[
// test case #1
{
name,
status,
attachments,
exe_start_date,
exe_end_date,
automation_content,
order: 1,
test_step_logs,
attachments
},
// test case #2
{
name,
status,
attachments,
exe_start_date,
exe_end_date,
automation_content,
order: 2,
test_step_logs,
attachments
},
// other test case(s)
...
]
test case object explained
name <string>name of the test case. This field is required.
status <string>execution status of this test case. Possible values are PASSED or FAILED. This field is required.
order <number> order of the test case. Increased by one (1) for every test case
exe_start_date <string>date the test case is executed under ISO 8601 format. This field is required.
exe_end_date <string>date the test case finished execution under ISO 8601 format. This field is required.
automation_content<string>this is the unique identifier of the automated test case. This field is required
attachments <Array> an array of attachment objects. This field is optional. Default: empty array []. Below is how an attachment object looks like
name <string> file name
data <string>based64 encoded data of the attachment
content_type <string> content type of the attachment. Default: text/plain
test_step_log <Array> an array of test step log object.Default: empty array. Below is how a test step log object looks like
order<number> order of the test step. Default: 0.
status <string> execution status of the test step. Possible values are PASSED or FAILED
description <string> description of the test step
expected_result <string> expected result of the test step
Below is an example of function output:
[
{
"status": "FAILED",
"name": "sample.junit.CalculateTest#testSum_second",
"attachments": [
{
"name": "testSum_second.txt",
"data": "amF2YS5sYW5nLkFzc2VydGlvbkVycm9yOiBleHBlY3RlZDo8Nz4gYnV0IHdhczo8MTA+CglhdCBvcmcuanVuaXQuQXNzZXJ0LmZhaWwoQXNzZXJ0LmphdmE6ODgpCglhdCBvcmcuanVuaXQuQXNzZXJ0LmZhaWxOb3RFcXVhbHMoQXNzZXJ0LmphdmE6NzQzKQoJYXQgb3JnLmp1bml0LkFzc2VydC5hc3NlcnRFcXVhbHMoQXNzZXJ0LmphdmE6MTE4KQoJYXQgb3JnLmp1bml0LkFzc2VydC5hc3NlcnRFcXVhbHMoQXNzZXJ0LmphdmE6NTU1KQoJYXQgb3JnLmp1bml0LkFzc2VydC5hc3NlcnRFcXVhbHMoQXNzZXJ0LmphdmE6NTQyKQoJYXQgc2FtcGxlLmp1bml0LkNhbGN1bGF0ZVRlc3QudGVzdFN1bV9zZWNvbmQoQ2FsY3VsYXRlVGVzdC5qYXZhOjUwKQo=",
"content_type": "text/plain"
}
],
"exe_start_date": "2018-06-07T14:43:44.834Z",
"exe_end_date": "2018-06-07T14:43:44.834Z",
"automation_content": "sample.junit.CalculateTest#testSum_second",
"test_step_logs": [
{
"order": 0,
"status": "FAILED",
"description": "testSum_second",
"expected_result": "testSum_second"
}
],
"order": 1
},
{
"status": "FAILED",
"name": "sample.junit.CalculateTest#testSum_One",
"attachments": [
{
"name": "testSum_One.txt",
"data": "amF2YS5sYW5nLkFzc2VydGlvbkVycm9yOiBleHBlY3RlZDo8MTE+IGJ1dCB3YXM6PDc+CglhdCBvcmcuanVuaXQuQXNzZXJ0LmZhaWwoQXNzZXJ0LmphdmE6ODgpCglhdCBvcmcuanVuaXQuQXNzZXJ0LmZhaWxOb3RFcXVhbHMoQXNzZXJ0LmphdmE6NzQzKQoJYXQgb3JnLmp1bml0LkFzc2VydC5hc3NlcnRFcXVhbHMoQXNzZXJ0LmphdmE6MTE4KQoJYXQgb3JnLmp1bml0LkFzc2VydC5hc3NlcnRFcXVhbHMoQXNzZXJ0LmphdmE6NTU1KQoJYXQgb3JnLmp1bml0LkFzc2VydC5hc3NlcnRFcXVhbHMoQXNzZXJ0LmphdmE6NTQyKQoJYXQgc2FtcGxlLmp1bml0LkNhbGN1bGF0ZVRlc3QudGVzdFN1bV9PbmUoQ2FsY3VsYXRlVGVzdC5qYXZhOjQwKQo=",
"content_type": "text/plain"
}
],
"exe_start_date": "2018-06-07T14:43:44.834Z",
"exe_end_date": "2018-06-07T14:43:44.834Z",
"automation_content": "sample.junit.CalculateTest#testSum_One",
"test_step_logs": [
{
"order": 0,
"status": "FAILED",
"description": "testSum_One",
"expected_result": "testSum_One"
}
],
"order": 2
}
]
TIP: it is highly recommended that you download the built-in parser provided in qTest Launch's, learn the implementation logic before starting to develop your own custom parser.
Package the Parser
When you finish implementing the parser, you can package it under a .zip file. Ensure your zip package, once unzipped, has a structure like below (they should NOT be nested in a folder)
IMPORTANT: you must pre-install all the node modules needed for your parser and zip them along with the package. The Automation Host will NOT install those node modules for you due to some network restriction that might cause the modules installation failed unexpectedly.
Upload the Parser to qTest Launch
Access qTest Launch and open the Settings dialog.
Select the Universal Agent tab and then theADD button.
The Add New Parser dialog will display. Then, enter the following:
Name: name of your custom parser
Version: version of your parser
Zip package: browse to the location of your .zip package
Save and then your parser will be uploaded to qTest Launch as shown in the following screenshot.
From now on, the parser will be available in qTest Launch and you can use it in your Universal Agent configuration.
The parser will also be downloaded and made available in Automation Host that you can use in your Universal Agent configuration.
View Article
Scenario 3.2.0 Q4 2019 OnPremise Release Notes

New Features and Enhancements
Editing your Commit Message
You can now edit your commit message whenever you save a feature file.
Bug Fixes
Ticket
Component
Description
29997
Jira Feature file
There is no longer a 500 error when trying to update a Jira Feature file a second time in Scenario.
30057
Jira
There is no longer an issue loading Scenario content in Jira.
View Article

1 2 3 4 5 6 7 8 9 10

Curious about QASymphony?

Anonymously Ask QASymphony Any Question

Ask Anonymous Question

Working at QASymphony

Compensation

Top 35%Top 35% of Similar Size Companies on Comparably

Compensation Score at QASymphony is rated a B by 4 employees.

Overall Culture

Top 25%Top 25% of Similar Size Companies on Comparably

Overall Culture at QASymphony is rated a B by 4 employees.

Perks And Benefits

Top 30%Top 30% of Similar Size Companies on Comparably

Perks And Benefits Score at QASymphony is rated a B by 4 employees.

CEO Rating

Top 5%Top 5% of Similar Size Companies on Comparably

A+

CEO Rating at QASymphony is rated an A+ by 3 employees.

Environment

Top 35%Top 35% of Similar Size Companies on Comparably

Environment Score at QASymphony is rated a B by 3 employees.

QASymphony's Competitors

Recently Asked Questions

Recent QASymphony Employee Reviews

it's very generous. no health insurance premiums.

Rate your company

QASymphony FAQs

Frequently Asked Questions About QASymphony

Automation Host 2.3.3 Release Notes - February 17, 2020

qTest Jenkins Plugin Release Notes

Launch 1.5.3 Single Server Upgrade Guide for Docker

qTest Sessions OnDemand Release Notes

Parameters 2.2.8 OnDemand Feb 03, 2020 Release Notes

qTest Controller - Setting up qTest Insights with Postgres Read Replica 9.6.1 OnPremise

Parameters2.2.4 Single Server Upgrade Guide for Docker

Parameters 2.2.4 OnPremise Single Server Install Guide for Docker

Create Unified Functional Testing (UFT) Agent from Automation Host v 1.3.8 or Later

Create Unified Functional Testing (UFT) Agent from Launch

Using the API's to Link Test Cases and Requirements

qTest Manager 9.9.2+ OnDemand Release Notes

qTest Scenario with OAuth Configuration Guide

Parameters 2.2.8 On Premise February 2020 Release Notes

Introduction to qTest Objects

Manager 9.9.1 OnDemand Release Notes

Silent Install Desktop Explorer with MSI package

Upgrade Insights Logi License for OnPremise before 9.9.1 (Insights version prior to 1.21.14)

Manager 9.7.1+ Release Notes

Insights 1.21.1+ OnDemand Release Notes

Getting Started with qTest 9.7.1 OnPremise: July 2019

Getting Started with qTest 9.6.1 OnPremise

Getting Started with qTest 9.5.3 OnPremise

Getting Started with qTest OnPremise Summer 2018

Getting Started with qTest OnPremise Fall 2018

Getting Started with qTest OnPremise Spring 2018

Getting Started with Q4 2019 qTest OnPremise

OnPremise Upgrade Guides

OnPremise Install Guides

qTest Manager 9.8.3 Q4 2019 OnPremise Release Notes

Insights 1.21.12 Q4 OnPremise Release Notes

Integrate JUnit for Java with Universal Agent

Configure Scenario for Versions 2.1.0 and Beyond

qTest Controller - Applying 9.8.3-2 application patch for qTest Manager

9.8.3-2 OnPremise Patch Release Notes

Sessions 4.3.2 OnPremise February 2020 Release Notes

Launch 1.5.6 OnDemand Release Notes - December 26, 2019

Parameters 2.2.7 OnDemand December 26, 2019 Release Notes

Linking Test Cases and Requirements

Launch 1.5.3 OnPremise Release Notes: July 2019

Batch Actions

Importing Requirements Using Excel Import

Importing Test Cases Using Excel Import

Launch 1.5.5 OnDemand Release Notes - December 19, 2019

OnPremise Product and Integrating App Compatibility

Scenario 3.3.0 OD Release Notes

Parameters 2.2.6 OnDemand Release Notes

Integration with VersionOne

Develop Custom Test Result Parser for Universal Agent

Scenario 3.2.0 Q4 2019 OnPremise Release Notes

Anonymously Ask QASymphony Any Question

Working at QASymphony

QASymphony's Competitors

Recently Asked Questions

Recent QASymphony Employee Reviews