Item: PractiTest
Rating: 9
Author: Michael Walkowski

Use Cases and Deployment Scope

We currently use PractiTest as a Test Case repository for the QA department. We link the requirements to our projects, write tests to be executed, track executions, and have our automation results feed in as well to provide a common place for all testing results. PractiTest has a lot of potential to provide tons of different metrics and results from testing. It also integrates with other platforms (Jira for us) so that we can easily work between the two platforms.

Pros and Cons

The ability to create custom fields on your test cases
The custom reporting results due to the custom fields
The ability to work using filters instead of folder trees
Integrations with other platforms
Constant availability of support
Community oriented (host online testing conferences for free, provide insightful blog posts for the testing community, etc.)

Better dashboard display capability (drag and drop to rearrange gadgets)
Creation of global user groups (as opposed to just project groups)

Return on Investment

PractiTest has saved us time in managing our test cases and providing immediate reports through dashboards
The capability to provide a dashboard through and external link allows clients to view our dashboards in real-time (saving time on sending reports).

Alternatives Considered

Tricentis qTest (formerly QASymphony)

I've used many different Test Case Repository tools, and while each of them has its perks, I like the capabilities of PractiTest best.
When creating a test in qTest for example, you can only input information into the fields provided, and you have everything set up in a folder tree structure. With PractiTest, we are able to create custom fields and filter our tests based on those fields to provide more accurate information in a readily available format while quickly searching for the filter instead of through a folder tree.
TestRail did not appear to meet our needs as a company. It just didn't have the potential that we found with PractiTest.
Zephyr for example worked seamlessly with Jira, which is really nice since that is what we use for the most part. However since we cater to many different clients, we needed an external Test Case repository so we could use something that wasn't tied to 1 Jira instance.

Support Rating

The chat button is available to anyone who logs into PractiTest. In my experience, the support has always been very quick, very friendly, and very thorough. They make sure that your question is answered in a way that you understand it. They also provide documentation of best practices so you are never left hanging on what to do next.

Key Insights

Do you think PractiTest delivers good value for the price?

Yes

Are you happy with PractiTest's feature set?

Yes

Did PractiTest live up to sales and marketing promises?

Yes

Did implementation of PractiTest go as expected?

Yes

Would you buy PractiTest again?

Yes

Other Software Used

Jira Software, Postman, PyCharm

Likelihood to Recommend

PractiTest works GREAT as a test case repository. It is very easy to gather metrics, filter, and sort based on custom fields. We were able to work with the API to pull our automation results in as well. The support team is always very quick with their responses and monitors the "in-app chat." They are very open to answering questions, providing best practice materials, and looking for additional feedback.
If you already have a central location for all of your test cases and testing needs, then I guess you probably wouldn't need to add another. However, PractiTest has high capability and potential, so if it's set up properly you can easily save time managing your tests.

PractiTest has not only been great for our company, but for the testing community at large

Overall Satisfaction with PractiTest