67 Tricentis qTest Reviews
Overall Review Sentiment for Tricentis qTest
Log in to view review sentiment.
We can maintain a suite of step-by-step test designs, one test to cover each feature of the product, or one aspect of a feature. Those tests can easily be rolled forward to the next baseline, or the next delivery of the current baseline. Additional tests can be added to any baseline's suite of tests at any time, so we can add a test that covers a particular defect coming back from fielded software or a new test of a newly added feature. We can also designate a onetime group of tests as part of a particular milestone, e.g. a set of regression tests to make sure that a product change did not leak into related areas. Review collected by and hosted on G2.com.
QTest has a lot of features and can be overwhelming in that regard. We use it primarily to manage manual tests though we are looking into tracking automated tests as well. It can be difficult to reorganize a large product, or to manage a suite of inter-related but not hierarchical products. In one instance we ended up exporting our tests to a spreadsheet and then re-importing them, but at least that was possible. Review collected by and hosted on G2.com.
Qtest report section, I like how qtest report appears Review collected by and hosted on G2.com.
slowness, sometime while we go from one tab to anther it takes time Review collected by and hosted on G2.com.
Able to see all the tests no matter what type they are(unit, automation, performance etc.) Review collected by and hosted on G2.com.
LTPulse is the one area I would say needs more improvement as it's not user friendly now. Review collected by and hosted on G2.com.
The ease of creating individual test-cases.
The ease of creating test cycles and test suites.
The ease of managing requirements.
The ease of managing test execution.
The usefulness of the reporting tool in graphing project progress. Review collected by and hosted on G2.com.
Modifying test steps on many test cases since the find/replace function does not include test steps and step expected results.
The program response is 'clunky' and sometimes takes extra time or even extra selections to access desired functional areas. Review collected by and hosted on G2.com.
It works okay with TFS 2012. Once installed it does seem to be mostly set it and forget it. As long as you use Java 7. Support is pretty good. Review collected by and hosted on G2.com.
It is very difficult to set up all the technologies. We can't update to TFS 2015 until they support it. A real issue with our team. It should be able to use whatever Java or TFS version. It would be great if they had an installer that installed all the underlying technology. Instead we had to setup redis, elasticsearch and java before we could install qTest. Review collected by and hosted on G2.com.
qTest does an excellent job of making managing Releases, Requirements, Test Cases, and Test Results very easy. You can create requirements and quickly create test cases linked to that requirement in order to track test coverage. By utilizing Test Suites and Test Cycles it's easy to organize your tests for a release. The interface used for running tests is great, and geared toward making it easy to execute and maintain tests at the same time. Additionally, the support team is awesome. They always reply quickly, even when you simply ping them with a question. More than once, I have seen requests I have made to the support team addressed in the next release. Review collected by and hosted on G2.com.
My only wish is that the reports be a little more configurable, but they provide more than enough canned reports and query functionality that you can get the info you need. Review collected by and hosted on G2.com.
Best parts are:
1) Connecting all test cases with user story.
2) Connecting all JIRA's with TC's
3) It's easy for PO's and other team members to review.
Review collected by and hosted on G2.com.
Things QA-Symphony can improve
1) Copy and paste between the projects didn't works very well sometimes.
2) Sometimes loading issues.
3) It remember user name and passwords Review collected by and hosted on G2.com.
Qtest has all the features for testcase management I need. This includes the flow of data as well as tracking that data. Having a integration with Jira has been a huge plus. I also like the ability to create custom fields. This lets me adjust to my QA work flow. I am looking forward to using the new api set for qtest7, hopefully I'll ahve the update soon. I have enjoyed the export and import functionality. Review collected by and hosted on G2.com.
To execute a testcase you have to create a test suite that has test runs. Testcases and testruns are 2 different objects. From the UI I cannot see historical results of a testcase, I have to use a database query. A testexecution should be created from an instance of the testcase object and linked somehow. Having to manage 2 different object types is inefficient. I don't like having to pay more to have the ability to share testcases between projects. Review collected by and hosted on G2.com.
The ability to get going quickly w/o having to learn the user interface. I am leading up a new test team with staff that isn't your typical testing community. qTest is straight forward in it's design. Implementing this tool was simple. Review collected by and hosted on G2.com.
The native requirements and defect modules could use some more build out. I understand that most customers use Jira for those modules, but it would be nice to see those modules become more robust. Review collected by and hosted on G2.com.
* eXplorer tool
* integration with JIRA
* reporting capability
* very configurable
* separate access to projects (can share with customers)
* test artefact organisation/ tree view presentation
* ability to share test cases
* assignment of test cases
* version control Review collected by and hosted on G2.com.
* reporting needs further improvement (I know this is in the pipeline)
* more bugs than I expected in the software Review collected by and hosted on G2.com.
