Compare PractiTest and TestRail 
- Users report that PractiTest excels in its Requirements Listing feature, scoring a remarkable 9.1, which allows teams to effectively manage and track requirements throughout the testing process. In contrast, TestRail does not have a dedicated score for this feature, which may impact its usability for teams focused on requirement management.
- Reviewers mention that PractiTest's Centralized Information feature, rated at 9.4, provides a comprehensive view of all testing activities, making it easier for teams to access and share information. TestRail, while strong in many areas, does not highlight a similar centralized approach, which could lead to fragmented information sharing.
- G2 users highlight PractiTest's superior Quality of Support with a score of 9.1, indicating that users feel well-supported and valued. In comparison, TestRail's support quality is rated at 8.4, suggesting that while it is still good, it may not meet the same level of user satisfaction.
- Users on G2 report that PractiTest's Automated Creation & Testing feature scores an impressive 9.2, allowing for efficient test case generation and execution. TestRail, while offering automation capabilities, does not match this level of user satisfaction, which may affect teams looking for robust automation tools.
- Reviewers mention that both products score similarly in Test Repository and Test Diversity, both rated at 8.9 and 8.7 for PractiTest and 8.9 and 8.6 for TestRail respectively. However, PractiTest's slight edge in these areas suggests a more versatile approach to managing diverse testing scenarios.
- Users say that PractiTest's Integration capabilities, rated at 8.5, are more favorable compared to TestRail's 7.9, indicating that PractiTest may offer a wider range of integrations with other tools, which is crucial for teams looking to streamline their testing processes across different platforms.
- Issues, Requirements, Tests, and Test Sets & Runs
- Unlimited Custom Fields and Filters
- Unlimited Projects
- No IT required, get started in minutes
- Automated updates & optimizations
- Secure hosting on super-fast servers
1. Visibility Visibility Visibility!!! The dashboard is amazing. I can create new tabs for my personal use and use fields and filters for the data. We use also the external dashboards and it really helps us all be aligned (we have it right in-front of the...
Search feature returns are head-scratching--searching for specific test cases rarely return anything useful. Filters and Folders structures are convoluted and archaic--ultimately these become catch-all areas and become useless over time. Mass editing is...
I am experienced in a number of test management tools including HP ALM/Quality Center, IBM's Rational ClearQuest, SmartBear's QA Complete, among others. I am now one of the owners of a small professional services group, and I have management...
I don't like that once you close a ticket in Jira the status of the ticket reads closed in TestRail, yet Testrail still shows that issue as either needing to have a test run on it to pass or fail. If its closed its closed, and no longer needs tests to run.
1. Visibility Visibility Visibility!!! The dashboard is amazing. I can create new tabs for my personal use and use fields and filters for the data. We use also the external dashboards and it really helps us all be aligned (we have it right in-front of the...
I am experienced in a number of test management tools including HP ALM/Quality Center, IBM's Rational ClearQuest, SmartBear's QA Complete, among others. I am now one of the owners of a small professional services group, and I have management...
Search feature returns are head-scratching--searching for specific test cases rarely return anything useful. Filters and Folders structures are convoluted and archaic--ultimately these become catch-all areas and become useless over time. Mass editing is...
I don't like that once you close a ticket in Jira the status of the ticket reads closed in TestRail, yet Testrail still shows that issue as either needing to have a test run on it to pass or fail. If its closed its closed, and no longer needs tests to run.
