PractiTest is presented as a cloud-based test management tool that provides its customers with an end-to-end system to meet testing and QA needs. It is described by the vendor as flexible but methodological, enabling organizations to ensure visibility and communication at all levels. The solution aims to help users and project development teams streamline and manage their testing processes, while providing management with a clear and simple view of their project status at all times.
$39
user
TestRail
Score 6.9 out of 10
N/A
TestRail by Gurock, an IDERA company, is presented as a complete web-based test case management solution to manage, track, and organize your software testing efforts.
$35
per month billed annually per user
Pricing
PractiTest
TestRail
Editions & Modules
Professional
$39.00
user
Enterprise
$49.00
user
Professional Cloud
$35
per month billed annually per user
Professional Cloud
$38
per month per user
Enterprise Cloud
$71
per month billed annually per user
Offerings
Pricing Offerings
PractiTest
TestRail
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
PractiTest
TestRail
Features
PractiTest
TestRail
Test Management
Comparison of Test Management features of Product A and Product B
For most of the test case scenarios, PractiTest works fine. If we talk about one specific feature then it would be the automation side. I like this feature a lot just because it made all testing so easy and effortless but on the other hand automation in this platform comes with so many limitations and that's where I am not fully satisfied.
Well suited - where you have a set of cases defined say for regression and then you can mark them as Pass/Fail/Skipped, etc. If you wish to present the impact of certain set of new features, bug fixes,etc, you can use this tool Not well suited- where the user is naive and don’t have much understanding of test reporting tools as this tool is slightly difficult to learn at a glance
As I am a tester, for me I found this tool to be new in terms of everything like the management of tests, plans, releases, reporting,etc. It is overall a good tool for test reporting and can be used for reference in the future. I liked several features of on the go placement of screenshots. Also I feel like the UI , the font, the color combination can be improved
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.
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.
TestRail definitely saves times. I work in a company that consists of several development teams, all of which have different processes. Some of the teams leverage test cases, some do not. I've noticed that the turn around time it takes for me to pick up a ticket, QA it, and then pass/fail/send feedback is much faster when there is a test case created as I'm not reading through ticket description/comments to figure out what needs to be QA'd.