qTest Manager organizes tests by projects and then by release. Each release contains test cycles. Each test cycle includes several functional tests.
NeoLoad integrates with qTest Manager to create automatically a test run in qTest containing the information of the performance test result.
Prerequisite: The qTest integration requires you to "activate automation integrations" in your qTest project. Please refer to the qTest documentation for more details.
Prerequisite: The qTest integration requires you to disable the “Unlinked Test Cases” in the “Test Case Settings” of your qTest project. You can also enable this setting and add any integration users to the exception list. Please refer to the qTest documentation of Test Case Settings for more details.
Tip: If you work with an on-premise qTest deployment with self-signed certificate, you may encounter SSL certificate error messages that can be fixed with quite a lot of configuration. To ease the process and be able to work with self-signed on-premise instances, you may set the property stated below to true. In the installation directory of NeoLoad, in <install-dir>/conf/controller.properties [General] qtest.tls.insecure=true
To enable the NeoLoad module for qTest
In the NeoLoad menu bar, click Edit > Preferences > Project settings > qTest.
Select Enable qTestintegration.
Tip: Select the option Automatically create Defects on failed and warning SLAs to have NeoLoad create 1 qTest Defect for each failed and warning SLA at the end of the test and send it to qTest along with the other test result information.
Configure the NeoLoad module for qTest
Once you have enabled the qTest module in NeoLoad GUI, you can proceed with the configuration of the integration with a "default.yaml" as-code file or in NeoLoad GUI.
To configure the NeoLoad module for qTest with as-code
Each preference of the project related to qTest can be overwritten individually thanks to the as-code properties as documented in Github.
Example of an as-code "default.yaml" file containing the rest of the configuration:
qtest.url: https://myCompany.qtestnet.com
qtest.token: clearTokenOrTokenEncryptedByNeoload
qtest.auth_method: TOKEN
qtest.project_id: 101762
qtest.cycle_id: 3761630
To configure the NeoLoad module for qTest in NeoLoad GUI
In the NeoLoad menu bar, click Edit > Preferences > Project settings > qTest.
In the Server URL field, enter the URL of the qTest SaaS or on-premise environment.
Select the type of authentication you want to use.
If you select Authentication with API token, enter the API token you can find in your qTest environment (API & SDK section of the Resources menu). For more information, click the Get token link and/or see the Tricentis documentation here.
If you select Authentication with password, enter the credentials you use to log into qTest.
If you need a proxy to go to qTest, you can configure a proxy in NeoLoad General settings by clicking the Proxy configuration in general settings link. See Use a proxy for more details.
Choose if you want that a new qTest defect be created for each qTest test step with a failed status. The defects created will be tagged as “Performance” category and “Bug” type if possible. These values exist by default in qTest field settings. If you update or remove them, the integration will not select it. For more details, please refer to the qTest documentation of Field Settings.
Click the Test button to verify the connection is well established between NeoLoad and qTest.
In the Context panel, the Project drop-down menu enables you to select the project and node where you want your NeoLoad performance test to be inserted.
You can click and scroll in the menu or directly type and search the name of the project.
Click Apply to save your configuration.
The link to the item created in qTest is available:
in the Results summary in NeoLoad GUI
in the Test Result view in NeoLoad Web
If the transfer to NeoLoad Web is enabled, the link to the NeoLoad Web Test Result is available in qTest in the “Test Log Details”, and in the execution history “Build URL” column. By default this column is hidden, you have to add it to the table by clicking the Gear button: