Compare PractiTest and TestRail 
- Users report that PractiTest excels in Quality of Support with a score of 9.1, while TestRail's support is rated lower at 8.4. Reviewers mention that PractiTest's support team is responsive and helpful, making it easier to resolve issues quickly.
- Reviewers mention that both products have a strong Test Repository feature, scoring equally at 8.9. However, users on G2 highlight PractiTest's ability to manage complex test cases more effectively, which can be crucial for larger projects.
- Users say that PractiTest shines in Requirements Listing with a perfect score of 9.1, while TestRail does not have this feature as robustly integrated. Reviewers mention that PractiTest's requirements management allows for better traceability and alignment with testing efforts.
- G2 users report that PractiTest offers superior Internal Communication Enablement with a score of 9.0, compared to TestRail's performance in this area. Users say that PractiTest's communication tools facilitate better collaboration among team members.
- Users report that both products are on par in terms of Scaling, with scores of 8.4. However, reviewers mention that PractiTest's flexibility in scaling to accommodate larger teams and projects is a significant advantage.
- Reviewers mention that PractiTest's Automated Creation & Testing feature scores impressively at 9.2, while TestRail does not offer the same level of automation. Users say that this feature in PractiTest significantly reduces manual effort and increases testing efficiency.
- 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.
