We just raised a $30M Series A: Read our story

PractiTest OverviewUNIXBusinessApplication

PractiTest is #11 ranked solution in top Quality Management Tools and #14 ranked solution in top Application Lifecycle Management Suites. IT Central Station users give PractiTest an average rating of 8 out of 10. PractiTest is most commonly compared to TestRail by Gurock:PractiTest vs TestRail by Gurock. The top industry researching this solution are professionals from a computer software company, accounting for 28% of all views.
What is PractiTest?

Manage your QA and Testing process, controlling your testing tasks while getting complete visibility into your results, and most importantly releasing your products in a professional way

Professional end to end QA management for your manual and automation testing. 
  • Create your manual tests and organize them based on cycles, sprints, etc.
  • Seamlessly integrate your manual testing with your automation and CI processes.
  • Reuse tests and correlate results across different releases and products.
  • Release your products with confidence and control.


Buyer's Guide

Download the Application Lifecycle Management (ALM) Suites Buyer's Guide including reviews and more. Updated: October 2021

PractiTest Customers

Canonical, SAS, Amobee, Play Buzz, Abbott, Aternity, Zerto, Freeman

PractiTest Video

Pricing Advice

What users are saying about PractiTest pricing:
  • "Pricing is probably in the middle, it's not the cheapest but it's not the most expensive."

PractiTest Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
DC
Test Team Lead at a computer software company with 501-1,000 employees
Real User
Top 10
Flexible and intuitive with easy reporting, and good support that is instantly available through chat

Pros and Cons

  • "The most valuable feature is the way the libraries are structured so that they were not folder driven."
  • "It doesn't allow you to connect to multiple different tracking tools."

What is our primary use case?

We are using this solution to create a library of our manual test cases, to record any bugs, and report the status of the testing to the stakeholders. 

How has it helped my organization?

Helped organise the manual test cases so they were documented correctly. This was invaluable as it allowed for reviewing/improving of test scripts so they could be followed by a number of different people which helped with resourcing. The reporting was useful to as i could concentrate on the testing knowing the reporting sorted itself out which was a massive step up from using excel where the reporting took a lot of effort simply to keep track of progress.

What is most valuable?

The most valuable feature is the way the libraries are structured so that they were not folder driven. They are structured by tags. We had tagged test cases.

It's a nice feature that allows you to be quite flexible in the way that you structure them.

Also, the fact that you can review the test cases as well as approve them or put them through repair is a very useful feature.

The reporting is quite simple. 

The interface is quite intuitive. It's pretty straightforward.

What needs improvement?

It doesn't allow you to connect to multiple different bug tracking tools at the same time. This is not an issue if you only have one bug tracker but we can potentially use different tools for different projects. As an example, if you connect PractiTest to Jira for one project, that's the one you have to use for all projects. 

We had a requirement to connect with Jira for one project, and a different tool for another, project but it was unable to accommodate that unfortunately. 

I would therefore like to see it easier to integrate with bug tracking tools at project level which would give each project the opportunity to use a different bug tracker if required. 

For how long have I used the solution?

I have been using PractiTest for approximately two years.

We were using the latest version. It's a SaaS solution, so it's always the latest one.

The last time I used this solution was May of this year.

What do I think about the stability of the solution?

PractiTest is a stable solution.

What do I think about the scalability of the solution?

We haven't tried to scale it yet.

There were only a few of us in our company who are using it. Approximately four or five.

How are customer service and technical support?

We contacted technical support briefly, and it was pretty good.

The support is pretty much instantly available through an online chat, which is quite rare really. 

You didn't have to raise a ticket and wait for a response, you just do an instant chat for them, which is quite nice.

Which solution did I use previously and why did I switch?

Prior to PractiTest we just used excel which meant we often simply recorded what we wanted to test but never documented how to test it.

How was the initial setup?

The initial setup was very simple. It only took minutes to deploy.

As long as you can put in your card details, you can be up and running.

What about the implementation team?

We implemented ourselves. If we wanted help it was there. They have very good online chat support that is pretty much available instantly. Which is quite nice.

It's a straightforward system, so we didn't need too much. We were only using it for testing, so we weren't really doing much with automated testing.

It was quite straightforward.

What's my experience with pricing, setup cost, and licensing?

Pricing is probably in the middle, it's not the cheapest but it's not the most expensive.

There were no additional fees, everything was included in the license and the online support was great.

Which other solutions did I evaluate?

I looked at a few but preferred PractiTest for its pricing flexibility.

What other advice do I have?

I would recommend this solution to others who are interested in using it.

I would rate PractiTest an eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.