PractiTest Reviews

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. 

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.

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.

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. 

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.

PractiTest is a stable 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.

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.

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.

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.

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.

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.

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

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

I would rate PractiTest an eight out of ten.

Our company was looking for a test management tool that could be integrated with Pivotal Tracker and Selenium. We selected PractiTest out of other tools due to its great integration solutions. 

Therefore, we work with PractiTest, Selenium, and Pivotal Tracker and all the systems are synced. That is exactly the tool which we were looking for. 

In addition, we found PractiTest very user-friendly and customizable.

Needs to improve adding the ability to run tests multiple times and setting different parameters.

One year.

Recently, we had minor issues but they were resolved fast.

They provide a high-level of customer support.

Zephyr, qTest, and TestRail.

Integration with other platforms, Test Set schedule, custom filters, requirements linking with the test case, and the Dashboard are the most valuable features of this product.

Just one click on the Dashboard and we get all reports in graphical format. Dashboards and reports are very customizable and the ability to share metrics with other colleagues is a great feature.

Custom filters are really a big advantage of PractiTest. We have hundreds of tests and test sets that we can arrange properly and easily thanks to this tool.

In addition, PractiTest offers a good reporting module and integration with other platforms such as JIRA, which we use daily.

Advanced customization allows us to customize the tool's settings in accordance with all our needs.

We integrated PractiTest with Pivotal Tracker and it allowed us to have everything synced on two systems and to make our testing process more professional.

Since we started using this product, our organization's testing functionality has really improved. We easily trace requirements and maintain the bug lifecycle. We can also easily trace how many test cases have been completed in a predefined schedule test, and we easily maintain the test case library.

It does not offer server installation, only software as a service. Also, the JIRA integration setup took some time. We worked with their support. Initially, it was hard to understand. I would recommend that PractiTest add more
options for execution via API, as sometimes we feel the lack of them.

The last year.

No.

No.

10 out of 10.

We used HPE Quality Center. We switched because:

• Customization was too rigid.
• User-defined fields can be created, but you are limited to a predefined set of field types: user list, lookup list, string, date, and number. This covers most needs, but does have some limits. For instance, there is no checkbox option (which actually used to exist in older versions of TestDirector).

PractiTest is a cloud-based tool and that was a big advantage for us, as we did not want any installation on our side.

Starts at $15.00/month.

Pricing model: Subscription/free trial (no credit card required).

Before choosing this product, we evaluated Test Complete.

It is a SaaS product, so there are no special requirements for implementing it. Choose the subscription plan according to your developer and testing team size and requirements.

• Test Library
• Test sets
• Runs
• Reports

Because I am always working on running a test set or getting a report from a client.

It provides a good way to share knowledge by sharing the link to specific test sets. This way, some other PractiTest user can take a look at some test cases and reuse them, if needed.

Maybe adding a feature that allows user to export reports to an Excel format.

For two and a half years, the time that I have been working for the Accdeo company.

Yes, there are times when server is very slow in response.

No.

Intermediate to advanced.

I did use another solution for previous jobs. I changed because Accedo.tv, the company I work for now, is using this solution.

I received my account already set up.

This is a good solution for a global transnational company. Not sure about pricing.

No.

This is a good solution for a global transnational company. Not sure about pricing.

Its integration with JIRA is good which saves time in creating bugs separately on the JIRA board.

When we first started using this product for manual testing it was not integrated with JIRA, but now that it is things are easier.

Spooling of data needs to be more standardized, especially when we are taking data dumps.

Six months.

No, I didn't.

No, I didn't.

Technical support of PractiTest is awesome. They are always ready to help in any time zone, which makes them stand out from others.

No, this was the first test management tool we have used.

That was done by my USA team, so I am not the right person to answer this question.

That was done by my USA team, so I am not the right person to answer this question.

That was done by my USA team, so I am not the right person to answer this question.

This is a very good and easy to understand test management tool. Anyone with even limited knowledge of testing can use this tool.

The two-way integration with Pivotal Tracker is what appealed to me in the first place. I absolutely loved the ability to file a bug within PractiTest, have it automatically assigned to the proper developer stakeholder, and include the full steps of the test case including where it fell short.

• It helped the testing process in two major ways along with a handful of smaller benefits.

• I can't quantify how much better it is than "Excel Hell" for record keeping.

• It was easy to see historic results of pass/fail status of certain tests on a given platform, version, and date.

• The reporting makes sprint planning, review, and retro sessions seamless and very well-liked by PMs and developers.

• If PractiTest were used over the course of a year or two, it'd be very easy to see which specific feature or area of the product was weakest and strongest.

• This type of reporting is greatly beneficial in risk assessment and whistle-blowing of areas that may potentially benefit from code refactoring or intense bug fixes.

• It reduced the time taken to file a bug by a large margin. The interface and overall UX, ability to write out tests, customization of workflows/process, and ability to integrate with a variety of platforms were all bonuses.

PractiTest practically requires a lot of sandboxing, demos with their team, and online tutorials.

Although this information is very readily available and PractiTest provides all of these services for free as part of their wanting your business, it's still an intimidating process.

If you're looking for something you can just set up and run with ASAP, it's doable. However, there are some processes that may not seem intuitive that requires some research.

For me, it was a stumbling block on how to set up tests on different mobile devices and platforms. How do I execute an Android version of the same test plan as what I have written for iOS? (Bearing in mind that the interfaces are slightly different and Android offers multiple ways to do the same thing in iOS or vice versa.)

This was a whole side topic on how best to write test plans around these caveats. It was something I couldn't figure out on my own anyway.

It had a short lifespan due to the nature of the business rather than test case management birthrights. The documentation was sadly frowned upon at the business where I performed testing. PractiTest died a natural death after I voluntarily resigned from this particular company as I was its only advocate.

No stability issues. It is as solid as a rock on steroids.

We never scaled large enough to test these waters.

Technical support is highly responsive and always available. I was never let down or walked away disappointed with their support. They are A+ resources.

When I started at this particular company, they had scatterbrained, outdated, and chaotic spreadsheets for test plans where almost 90% of the tests didn't even make sense or make it clear what the expected results were. Converting a couple of these test plans into PractiTest was amazing and made a world of difference.

The initial setup was straightforward. Signing up for the trial and getting started was amazing. The complex aspect is in regards to the process/workflow aspects of multiple versions.

The pricing and licensing is competitive with other solutions, but it is steep. If you are a small business, don't be surprised if you're spending anywhere from $50-200/month. If you're an enterprise level with a large team of testers, you're looking well into the four-digits.

I did you evaluate other options. Sadly, however, I forgot them.

I'm a consultant, so I am biased in saying, "I charge $80/hour for advice." LOL.

Traceability between requirements, tests and issues

Customizable reports and dashboards

Various custom filters that help to organize data

PractiTest gives us the opportunity to control the testing process efficiently and saves us a lot of time that we had to spent while using other tools.

There are some features that I would like added: an option to export a part of tests with steps.

Two years

Always get a swift reply.

No technical knowledge required in order to start using PractiTest.