Tricentis qTest Reviews

Pros

Perfectly fit for agile projects, story board, customization of the product, reporting, bug management, reporting and analysis, user management, project milestones, color coding, flexible to upload/link attachments, shortcut keys for accessing items, integration with other market tools like blueprint, microsoft azure, caliber, etc.,

Cons

I liked all the features, least item is managing API code with postman tool and other coding features.

Pros

Its easy integration with different tools such as JIRA and the way it allows to manage test cases, requirements, bugs and everything related to SDLC

Cons

It becomes slow to run Insights queries when you have many projects selected

Pros

The software was integrated with qTest to bring over requirements and create test cases and execute them in qTest. We were able to run queries to find specific modules and run specific test cases. We were also able to effectively track which test cases had been executed and the result of those test cases. Then, qTest created helpful infographics to help us further track how far along in the test execution process we were.

Cons

Sometimes, the requirements between qTest and JIRA did not sync well. There were many times where the number of requirements in each software was not the same. Along with this, some of the qTest add-ons such as Insights are very difficult to work with and not intuitive as normal data analysis tools.

Pros

Its integration with JIRA and the capabilities it provides to execute test cases

Cons

Slowness to run queries using Insight module

Pros

The ease of use.Be able to copy/paste images to test cases steps.Version control.Execution process.

Cons

Application updates for patching existing issues and new features takes way too long to wait.

Alternatives Considered

Reasons for Choosing Tricentis qTest

Reasons for Switching to Tricentis qTest

Pros

Its easy integration with SDLC tools such as JIRA to gather needed information

Cons

It becomes slow to query many projects through Insights

Pros

Its easy to use and its feature to record and create tests

Cons

The copying of folders across modules. Also its not good for requirement management and hence creating test traceability

Pros

We are using qTest for tracking and creating our Test cases and User Stories and also for keeping a track of bugs

Cons

The thing that I don't like about this software is that sometimes it works really slow

Pros

I like how easy it is to save work, the intuitive UI and the color scheme for quick status checks. The layout is straightforward like Rally's and it can be a requirements repository. Integration seems to be easy and possible with requirements and Jira.

Cons

I didn't like how many steps it seems to take to set up the test plan folders. Our testing is pretty rigorous and used for FDA - approved medical devices so that some of the default workflows and fields are not robust enough. I don't like that the Actual Results field can be left blank as long as you select a test status.

Pros

-Easy to use
-Integration with Jira is the main reason we use this
-Test Script creation

Cons

-Minor bugs when saving a test script could be fixed
-If you copy from word or any other source, the text is not always displayed correctly

Pros

Easy to use.Copy, paste & moving is simple

Cons

Not much features for automation testing

Pros

This software integrates with The Atlassian Jira software pretty well. I can select the Story or Bug that is imported from Jira to a test script and then the text execution data will be displayed in Jira. The catch is that unless you have a qTest license you can't see the actual details of the test when you click on it. You can also click the little create bug button while running a test case in qTest and it will automatically create the Bug in Jira and populate as much data as it can from the current test case.

Cons

I'm not sure if it is our implementation - but it seems to hiccup often, I randomly get errors or steps don't display. My problem is that I sometimes forget to click the Save button and I walk away and if the session times out - then all your work is lost.

Pros

qTest is very useful when creating and executing large batches of test cases, especially when running the same test cases in different environments. This saves time and effort, great feature!

Cons

Could use graphics to show test coverage and progress, rather than just a percentage report.

Pros

Intuitive UI,COLOR CODING, INTEGRATION WITH tools like JIRA, creates a clear link between the test case and the JIRA story assigned.
Provides multiple ways to create or upload test cases.Test design is satisfactory when created using qTest .

Cons

Requirement mapping,for same items belonging to a particular story you still have to manually tag every item with the story.Frustrating.
Also unit level management seems quite old and time consuming.

Pros

QA Symphony did a pretty good job by packaging most of the test management capabilities into it. Starting with its capability to import test cases from Excel spreadsheets or other tools is great.
Other notable feature includes complete control over requirement management and traceability and easy to use UI etc.

Cons

It is highly priced compared to other competitors.

Features: lacks a Rich Text Editor option in requirement management module.

Pros

I like the integration with JIRA, so we can import requirements into qTest just by tagging them on our JIRA board. From there we can have them organized by team and by sprint. Being able to search by requirement is the most useful feature for me.

Cons

The UI is a little counterintuitive. To add test cases to a test suite you have to click the 'Statistics' tab then you have the option to add tests. Still don't understand why they named it that.

Pros

I love the Jira integration. We run all our requirements through Jira and import them into qTest when we can link all our test cases to them.

Cons

The out of box reporting is lacking some basic features that you would think come standard.

Pros

Absolutely love the integration with Jira so that we can track all test cases for each requirement

Cons

Would like for it to be more user friendly for those that are not in the QA role

Pros

I have been using qtest for a while and I really like it the way it has built up. The integration with jira allows to link JIRA issues against the Qtest which is helpful in overall visibility.

Cons

The recent removal of precondition/Prerequisite field I didn't like it. In recent version the test pre requisite you cannot add.

Pros

I am using it daily and love the fact that you can integrate it with Jira. So you can connect the requirements with the test cases. It is easy to use, has a lot of great features. You can export/import test cases in excel/word.

Cons

Maybe the fact that the refresh is taking some time.

Pros

The software has a good workflow allowing traceability of requirements right through to individual test runs. It is easy to separate releases and produce reports on test summary once finished.

Cons

The UI looks unappealing and third party automation tools are generally not supported, as Tricentis want you to use Tosca for automation with qTest integration. We use Ranorex in our team and unfortunately this cannot hook up into qTest.

Pros

Ease of operation. Uploading TC, Execution, Releases, Jira Integration

Cons

Some times the slow response, nice to have automated test execution reports on email

Pros

Easy to use and understand
Good Support and Training sessions

Cons

qTest Insights didn't have the best options for displaying data/test cases.

Pros

Documenting all the test scenarios and regression test results with bug attached

Cons

The jira integration sometimes not working

Pros

It's quick and concise, easy to use and is very intuitive for what you may need to do with it.

Cons

There are some minor hassles like dragging to reorder things being finicky but that's more of a minor nitpick.