qTest for Test Management
Overall Satisfaction with Tricentis qTest
We use Tricentis qTest to help clients standardize and optimize test planning and repositories. We also use it with clients for manual and exploratory testing since not everything can be automated. As with anything, there's a learning curve. But leveraging qTest to store test scenarios in a clean way, also linking everything back to requirements provides traceability from start to finish. It also doesn't depend what automation platform we're using, qTest integrates well through qTest Pulse via API and webhooks. This is one of the elite commercial/enterprise grade test management platforms to exist.
Pros
- Cleanly organized repository structure for team to standardize to
- Gives me real time, historical, and future visibility as to the state of testing (results, in progress, planned - then all linked to requirements)
- Deep integration with a variety of automation tools and requirements management tooling
Cons
- Modular features create a feeling of overload and unnecessary complexity for newer users
- Reporting directly in qTest is lacking compared to BI tools (but it integrates directly to circumvent this)
- Not a strong defect manager
- Less tool sprawl, faster back and forth between teams - less duplication
- Faster release cycles
- Faster test creation with reusability
- Slow onboarding without expert help
- Without defined process and full adoption, qTest partial-use can occur, leading to rework and slow releases
- Tosca
- Selenium
- Cypress
- Appium
- Katalon
- Jenkins
- ADO
- TeamCity
- CircleCI
- Bamboo
- PowerBI
- GitHub Actions
- BrowserStack
- Perfecto
For visibility, an organization moving from spreadsheets or confluence for example, now has one place to look for all manual and automated test reporting directly linked to epics/stories. PMs can also see test statuses and launch readiness very easily. No more instinctual guessing.
For risk coverage, qTest allows for building a formal matrix of traceability, which you can then tag things based on risk, making test execution more effective by focusing on highest priority activities, as well as post-mortem or audit workflows moving much more swiftly.
As for process improvement, you can't manage what you don't measure. With qTest you can more easily trace repeated failures to identify root causes and adjust. You also no longer have to rely on tribal knowledge, you have a central record of history to bring new team members up to speed faster, as well as to mitigate errors or inefficiencies moving forward.
For risk coverage, qTest allows for building a formal matrix of traceability, which you can then tag things based on risk, making test execution more effective by focusing on highest priority activities, as well as post-mortem or audit workflows moving much more swiftly.
As for process improvement, you can't manage what you don't measure. With qTest you can more easily trace repeated failures to identify root causes and adjust. You also no longer have to rely on tribal knowledge, you have a central record of history to bring new team members up to speed faster, as well as to mitigate errors or inefficiencies moving forward.
Tricentis qTest ranks well among all test management platforms. For smaller teams with less activity or reporting requirements, qTest can be overkill. However, as organizations evolve and become more scrutinized or chaotic, qTest is one of, if not, the best option to ensure all your bases are covered. The biggest thing with qTest is ensuring best practices are maintained, and that all team members lean into the toolset rather than working around it.
Do you think Tricentis qTest delivers good value for the price?
Yes
Are you happy with Tricentis qTest's feature set?
Yes
Did Tricentis qTest live up to sales and marketing promises?
Yes
Did implementation of Tricentis qTest go as expected?
Yes
Would you buy Tricentis qTest again?
Yes

Comments
Please log in to join the conversation