PractiTest

What differentiates PractiTest from other similar products?

The depth of features e.g. filtering logic can generate nearly any view required and it works in the same way across all included ALM modules PractiTest has thought hard about what is required to provide a test management solution that can be molded to test the way your organisation needs to test. An example of this is the implementation of Test Sets and Test Instances. There are a number of products out there that appear to do the same thing but actually, they don't due to the implementation of parameters that PractiTest has included. This vastly reduces the number of test scripts that need to be written

What is your favorite aspect of this product?

Parameter-driven scripting. If used correctly, it ensures your business thinking is aligned with a uniform approach and not hit and miss. This becomes teased out very early in the testing process. This is getting better and better as time goes on

What do you dislike most about this product?

Reporting could be more flexible (and in some cases just more simplistic) so you can slice and dice information more readily. Requirements - at the moment it's quite basic but PractiTest is working on it. In point of fact, we have written an application that, using PractiTest's API creates a more usable requirement which can then be updated directly to PractiTest for traceability against related tests, issues, etc. Step Parameters - already very good - can't wait for the enhancements that allow you to make global changes throughout a set of parameters and or tests.

What recommendations would you give to someone considering this product?

Understand your requirements and talk to PractiTest. They know their business and understand their product very well (I would say their customer support is second to none in terms of efficiency and effectiveness). If they can't fulfill your requirement they will explain why. Often it is in a forthcoming release (and believe me they do release new changes often incorporating ideas from users - I can attest to that) which may not be far away. The best recommendation I can give is that I came to know PractiTest through use on a client site and, due to that experience of both the company and the tool, we have purchased the tool for our own use,

What differentiates PractiTest from other similar products?

The seamless integration with Jira, and the ability to create a Test and requirements right from the Jira Card is a tremendous time saver. It also assures consistency with the test cases.

What is your favorite aspect of this product?

It is intuitive to use and, therefore, simple to create test cases and test cases and test sets.

What do you dislike most about this product?

The ability to re-use steps from previous test cases is clunky. You need to know your test number and the steps to re-use them. A drag-and-drop interface would save a lot of time. Because of this, I don't import steps from previous test cases too often. I find keeping a One Note notebook with my test case content quicker for simple copy-n-paste vs. recalling steps.

What recommendations would you give to someone considering this product?

If you use Atlassian/Jira, get the integration set up. That made the decision simple for us to go with PractiTest.

What differentiates PractiTest from other similar products?

Filters are a game changer. Being able to infinitely nest filters allows for very powerful reporting and management.

What is your favorite aspect of this product?

The API is rich and full featured.

What do you dislike most about this product?

I'd like for dashboard items to be able to organize data based on values in text type custom fields.

What recommendations would you give to someone considering this product?

If you're looking for a QA test management platform look no further. Practitest is great! Give it a try.