End of Support Announcements for qTest

This page contains announcements for the end of support for various features used within qTest products.

GET Projects API Improvement November 19, 2020

The GET Project API is improved to allow users to define pagination. Additionally, a paging link in the Header of the responses is included when pagination (page and pageSize) are defined.

Parameter Required

Description

pageSize N

To define how many projects each page returns.

By default, if pagination is not specified in the request, the response only includes the first 100 objects.

You can specify custom number (up to 999) for this parameter

page N

To define which page will be returned.

By default, the first page returns but you can specify any page number to retrieve objects.

Deprecation and API Change Announcements September 3rd, 2020

API affected

GET /api/v3/projects/{projectId}/histories

Current Behavior

Customers reported when querying for objects' history there is only the ability to define pagination for the list of histories, but no ability to add paging for a list of objects. This produces slow query time

New Behavior

Users can define pagination for"

  • list of objects
  • list of histories of each object

Example: User defines:

  • ObjectPageSize = 100
  • ObjectPage = 1
  • History PageSize = 100
  • History Page = 1

Deprecations

There are 2 deprecation announcements. Read the changes carefully.

Bugzilla & Fogbuz

As part of routine maintenance, qTest monitors usage numbers of our existing integrations. When minimal use is observed, we take the opportunity to reduce the complexity of our application by removing those integrations. Bugzilla and Fogbuz were identified for deprecation through this process.

How this impacts qTest:

  • Customers not currently using the integrations:

    No impact. The connection will simply be removed.

  • Customers currently using the integration:

    No impact. The connection will simply be removed.

    The connection will still be available for customers whom currently using Bugzilla and Fogzilla.

    NOTICE: Bugzilla/Fogbugz is no longer supported from qTest Manager 10.2. Users will manage the defect life cycle outside of qTest as a result.

    Submit all defects directly to your OnDemand/Local integrated application.

    The Defect menu and some reports are disabled, as a result of this deprecation. Once the integration is deactivated, the connection to Fogbugz and Bugzilla is permanently removed from the Integration Settings page.

Deprecation and API Change Announcements May 1, 2020

There are 4 API change announcements for qTest 10.1, Q3 release. Review the changes carefully.

APIs affected

  1. API to trigger/retrieving data for connection

    Current Behavior

    Customers reported incorrect amount of defects being retrieved when using this endpoint. The API is actually returning incorrectly and only shows the first job ID of internal defects.

    New Behavior

    API returns an array of objects with jobs that are to be retrieved from Jira, along with their JobID.

    Sample of new response:

  2. API to update Test Run and API to update Test Suite

    Current Behavior

    We will release a feature to allow users to merge Jira releases in Q3, Therefore, a validation needs to be added for these two API endpoints.

    New Behavior

    When using this API, if plannedStartDate is being defined, then :

    • Project startDate <= Release Start Date <= test run plannedStartDate <= test run plannedEndDate <= Release End Date <= Project end date (optional)

    • Project startDate <= Release Start Date <= testSuite plannedStartDate <= testSuite plannedEndDate <= Release End Date <= Project end date (optional

  3. API to create a Test Run and API to create a Test Suite

    Current Behavior

    We will release a feature to allow users to merge Jira releases in Q3. While working on this feature, we encountered that the validation rule for the planned start date field were being handled incorrectly for these two API endpoints.

    New Behavior

    When using this API, if plannedStartDate is being defined, then -

    • Project startDate <= Release Start Date <= test run plannedStartDate <= test run plannedEndDate <= Release End Date <= Project end date (optional)

    • Project startDate <= Release Start Date <= testSuite plannedStartDate <= test suite plannedEndDate <= Release End Date <= Project end date (optional)

  4. Enable or disable Release Integration feature of a Jira connection

    Current Behavior

    Previously users were unable to map multiple Jira projects with the same fix version to a single qTest project.

    New Behavior

    In order to support the ability to map multiple Jira projects with the same fix version to a single qTest project we are adding a check box in the Release Integration section so that user can choose to merge duplicated fix versions. As a result of this enhancement, we need to make a change to the appropriate endpoint.

    • Added a new optional parameter to this endpoint: 'mergeDuplicatedFixVersions'

    • User can set this parameter to true (check box) or false (uncheck box). If unset, it will always default to False.

Atlassian change announcements

Atlassian Jira has posted the following announcements that impact Jira integration features:

Enhanced Validation of OAuthClientIds: Atlassian Connect is enhancing the security of impersonation token requests to ensure older OAuthClientId are no longer accepted. An app making a token request using an expired OAuthClientId will receive a response with a 400 status code. qTest uses the oauthClientId to get the Jira JWT access token, which specifically impacts using Jira with proxy. For additional information, read the Atlassian change notice here.

Deprecation of some Connect App install payload fields:The following fields in the Connect app install payload are deprecated and will be removed on, or after September, 2020. qTest does not use these fields for the integration.

  • pluginsVersion

  • serverVersion

For additional information, read the Atlassian change notice here.

Deprecations

There are 3 deprecation announcements. Read the changes carefully.

  1. Elasticsearch/ PostgreSQL

    As a part of routine maintenance, qTest monitors opensource updates to ensure compatibility with the latest versions. Elastic Search and PostgreSQL were identified as services that needed an upgrade.

    How this impacts qTest:

    • On-Demand: No impact

    • On-Premise: The Q3 2020 OnPremsie release of qTest 10.1 is planned to be compatible with PostgreSQL 10.x versions and Elastic Search 7.x versions.

      • As a result of this work, qTest 10.1 will not be compatible with Elastic Search 6.x versions

      • Customers using Elastic Search 6.x will need to install Elastic Search 7.x if they plan to take the 10.1 upgrade in Q3 2020.

      • Additionally, Elastic Search 6.x End of Life Support will take place in November 2020 - See info here https://www.elastic.co/support/eol

  2. Docker Deprecation Message

    The following deprecation notice, received from Docker, can affect qTest On-Premise versions in the future.

    Summary:

    • Docker will display a deprecate message if client is using Docker engine v19.03.0 to Docker engine v20.02.0.
    • Docker will not allow user to use Docker images that built with v2 schema 1 from Docker v20.03.0.
    • Current latest Docker release: v19.03.x

    How this impacts qTest:

    • On-Demand: No impact

    • On-Premise: Impact Docker deployment if following cases happen
      • Currently: Our docker images are built with v2 schema 1 methodology and we’re asking our clients to use Docker v17.03 to v18.0.3 for Q1 OP and Q2 OP (see this link) but if client installs the newest version then they will receive the following message when installing qTest by Docker installer. This is just a warning and does not affect the deployment, as client can still install qTest using Docker deployment and run qTest apps.

      • Future: Docker will release v20.03 soon and if client does not follow our recommendation and install v20.03 then Docker deployment will fail, qTest apps cannot be run.

    • In Q3 2020 OnPremise 10.1:

  3. GitHub will no longer support username/password integrations. Instead, they will require the use of a token for integration.

    Our plug-in has been updated to support both, but Github will officially deprecate this in November. Our Message for this change, in intercom, needs to go out 60 days before the beginning of November 2020. Likewise, this info needs to be updated in all documentation. - Cloud & OP

    Github has begun sending communication of username/password integration failures which continues through October (see sample failure messages below).

    In November 2020, the change will be official - https://developer.github.com/changes/2020-02-14-deprecating-password-auth/

    Hi @chris,

    On March 26th, 2020 at 16:52 (UTC) you used a password to access an endpoint through the GitHub API using octokit.js/15.17.0 Node.js/10.14.1 (Linux 4.14; x64):https://api.github.com/repositories/195080433. Basic authentication using a password to the API is deprecated and will soon no longer work. Visit https://developer.github.com/changes/2020-02-14-deprecating-password-auth/ for more information around suggested workarounds and removal dates.

    Thanks,

    The GitHub Team

Deprecation & API Change Announcement March 10, 2020

As our APIs evolve, Tricentis will notify you of any changes and provide you with sufficient time to adapt to these changes. Please review this message carefully to understand how to ensure that your application can adapt.

API affected

  • Get-Test-Runs API

  • Java SDK 1.4.9 (Located under Resources page in qTest, not to be confused with our Swagger SDK)

Current Behavior

  • Get-Test-Runs-API: This API returns all test runs. This may affect qTest performance in occasions when the list of test runs is extensively long.

  • Java SDK 1.4.9: Legacy SDK.

New Behavior

  • Get-Test-Runs-API: This API will only return the first 100 test runs if pagination information is not defined.

  • Java SDK 1.4.9: None. This will be removed from the resources download page within the next couple of weeks, and entirely deprecated by June 8th, 2020.

How am I impacted and What do I need to change?

  • Get-Test-Runs-API: As a result of this change, customers who use this API without pagination will only see the first 100 test runs. You should paginate your results by adding the page & pageSize parameter to your API requests.

  • Java SDK 1.4.9: As a result, customers using this SDK will have to rebuild their code using our swagger documentation.

When do I need to make the changes by?

You do NOT need to wait for our next release to make a pagination change. Do it now! We already support to include pagination in the API requests.

If you are using Java SDK 1.4.9, we advise you start NOW. Our New API behavior and SDK deprecation will become effective on June 8th, 2020. Please contact support@tricentis.com for more help.

Katalon Studio Deprecation

Tricentis has deprecated the integration with Katalon Studio and we are removing the integration information from the Download qTest Resources page in the coming weeks.

Supported Compatibility with External Tools

  • Tricentis cannot guarantee compatibility with versions of external tools that have reached End of Life.

  • To view a list of supported versions of Atlassian products, like Jira, please see: Atlassian Support End of Life Policy

Integration Browser Plug-ins

  • Safari plug-ins have been temporarily removed from the Resources page.

  • In the meantime, we recommend that you use Chrome or IE when using qTest with external integrations Jira, Rally, and VersionOne

API Access using http

  • Beginning with Manager v8.9, qTest APIs will no longer be accessible using http.

  • Please make sure to change your target URLs to use https instead or accept a 301 response as a successful response.

UFT V1 Integration

  • After this was released in July 2016, we released UFT V2 (with even more capabilities) in August 2017.

  • UFT V1 integration was deprecated in January 2018.

  • To integrate with UFT, we recommend using the new UFT V2 agent.

TestNG V1 Integration

  • After this was released in April 2015, the legacy plug-in was replaced by the TestNG V2 agent (with even more capabilities) in July 2015. The legacy TestNG V1 was removed from the Resources page starting with Manager v8.6.2.

  • To integrate with TestNG, we recommend using the TestNG V2 agent

HipChat Plug-in

  • This integration was released to the Atlassian Marketplace in March 2016. Due to the low usage of the HipChat plug-in, and the Atlassian announcement of Stride (HipChat's successor), this plug-in was removed from the Atlassian Marketplace in October 2017.

Mobile Explorer

  • Deprecated in August 2017 and removed from Resources page starting with Manager v8.6.2.