Tricentis qTest

Formerly QASymphony

We currently have partial integration and are not fully integrated with Tricentis. We update the test case manually or copy the same from previous projects, which is a good functionality that makes life easy for the testing team and saves time.

Very basic Jira integration, though it is finicky.

The JIRA plugin versions are not updated due to which it gets hectic with the integration, It doesn't supports the JIRA advance roadmap fields. Initializations and upon test runs, handling test you may face performance issues and mentioned by several users. Other, can be easily integrated with the automations scripts of selenium, Atlassian.

Integration with Jira is quite deep, offering bidirectional synchronization native support makes the setup relatively straightforward. Integrating with Jenkins enables automated test results to funnel back to qTest, ensuring a consolidated view of testing. The complexity rises when integrating with Selenium. Even though Selenium scripts can be executed and reported in qTest, however often the results need to be reformatted to be compatible with qTest

I think Integration was not that difficult this tool also has have the feature to connect with such tool

The depth of integration between Tricentis qTest and other tools can range from basic data synchronization to complex, bi-directional, and workflow-driven integrations. The difficulty of achieving these integrations depends on various factors, including the complexity of the integration, the tools involved, and the expertise of the team

We did not face much challenges since we had our own sme's and competencies who would help us.

The integration with MS Azure DevOps was complicated but once done it was easy to use. Integration with MF ALM was also a bit complicated.

It is very easy and user friendly to integrate Third Party tools with q_test

Thankfully he had some help from our the other team involved on the feature development, which made everything smoother.

Jira integration was easy , for .net c# api integration have to write code

All the integrations were really simple.

Simple for some tools but more challenging for some others.

The configuration was straight forward.

We are still exploring Jenkins. Jira was straightforward.

Jira Stories are imported as Requirements in qTest. Defects are also created and track in Jira but linked to qTest test cases. The integration setup was not difficult at all.

We have not tried integrating our other test tools with Tricentis qTest Explorer, nor have we seen a need to.

We did Tricentis qTest requirements integration with Jira. Initially, things looked like they were going to be simple to set up, but there were numerous problems throughout that led to it taking 3 months (including lackluster support from Tricentis qTest) to get things working semi-reliably. The defects integration with Jira was far simpler and that was set up in hardly any time at all.

Jira configuration is fairly straightforward. We did have an ongoing Webhook issue (which I got ZERO support on) when attempting to connect to a unique Jira instance. This never got solved and we eventually gave up on the integration. Selenium is integrated via the command line and our automation lead got zero support on this integration. In order to finalize the integration, she worked with a support community outside of Tricentis. Browser Stack integration went smoothly.

qTest is primarily integrated with our JIRA cloud instance. While we have experienced integration issues sporadically in the past the token connection has been fairly reliable. Setup and maintenance is not difficult to achieve, however, when issues do arise a re-sync or reconnection might be necessary which can also sometimes create unnecessary duplicate data entries within qTest as a result.

We are finding that the Azure DevOps integration isn't as seamless

Jira integration has been a constant issue and still does not work today completely. We have made several support calls and finally given up and do part of it manually.