TestRail Reviews

Regression testing

Comments: TestRail was implemented to do the record taking for manual regression testing and planning.

Pros:

Great product allowing us to keep history of our testing and specifically regression testing of our software development team

Cons:

Find some reporting can be difficult, but in general it is a great tool for managing our regression testing test cases, and ensuring that they have all been run.

Testcase Management

Comments: We enjoy using this tool because it takes little time to train new members and easy of using. SImple and faster.

Pros:

Ease of use. Simple and intuitive flow for the workflows that can be customized based on your work.

Cons:

Traceability is based on how you configure. Little confusing if you try to explain to users not familiar with the tool.

Alternatives Considered: Zephyr

Reasons for Choosing TestRail: Ease of use and less maintenance work. No need to worry about managing the infrastructure and secure.

Switched From: Rally Platform

Unfortunately, disappointing experience.

Comments: When I started to use it it was a relatively good test management tool, but in the second year it turned into a day-to-day struggle, I was wasting a lot of time writing and editing test cases - one of the key job characteristics of the QA. It's important to mention that I am not using TestRail for almost two years, and I hope the things got better. But honestly, I wouldn't risk to go back again.

Pros:

The test suites and test case structure were good and easy to navigate.

Cons:

The small tiny bugs that appeared every day and bothered our work. Things like the inability to open a screenshot in full-screen with 1 click.. To do that I had to open it on a new browser tab which was very annoying. And plenty of other similar issues that were arising day by day. This was the reason for switching to another test management system.

Great solution to improve testing efficiency

Pros:

Effective test case managment:- TestRail provides a highly customizable test case management system. You can create test suites, parts, and cases to suit the unique needs of your project. Easy to use:-Test cases using TestRail are efficient and simple. The ability to add test results, comments, and attachments directly from the interface simplifies the testing process.

Cons:

There should be option for comments or chat to communicate within TestRail for communication amongst team.

Everything we needed at half the cost

Comments: We are better able to track our software testing and coverage with this tool.

Pros:

I love the way they setup billing, every month you it automatically detects how many active users you have and you pay for that instead of being roped into a set amount of licenses. This has been incredibly helpful as we've gone through hiring, layoffs, and bringing on offshore contracted workers. Great flexibility! Another thing I like a lot are the UI Scripts, where you can customize the instance adding in or removing features and functionality. They are very powerful and super useful for us.

Cons:

It bugs me that every time you close a test run the test case id numbers have a huge spike, a case we created today had the id number of over 11 million even though we have less than 50,000 cases total in our library. I also do not like the way you add and remove tests from a run. It is a bit awkward and hard to see exactly what tests you're adding and removing.

If you are executing manual test cases on a large scale then Test Rail is for you

Comments: Having using various test management suites TestRail does excel in that it was built to run manual test cases and display results in an easy glance for the whole team. Linking to defects is simple, generating a report when the test run is complete. I feel like reusing regression suites could be improved, it does what it is meant to however you have to repeat several steps each time you want to generate a regression suite.
Some areas for improvement would be a test case type for API tests, I am sure everyone needs this but struggles to find a way to record this data.

Pros:

I think report generation is the strong suit of Test rail, the percentage pie chart of passed, failed blocked cases at a glance make daily reporting for scrum stand up meetings ideal. Integration with Jira is excellent, although some room for improvement.

Cons:

Trying to do something simple like import test case steps from a .csv is not so easy. You can import a suite but that is not ideal. Trying to duplicate cases can be tedious, let's say you have a lot of cases, trying to copy paste them in to various projects is a lot of hassle, it is surprising they have not addressed issues like this after so many years.

TestRail: Great for companies willing to pay for it!

Comments: Working on a Global team, TestRail enabled everyone to have a seat at the Test Case management/creation table. Editing existing test cases was very easy to do, and the GUI makes it easy to find any existing Test Case you are looking for.

Pros:

First of all, TestRail is an extremely smarter way to track and maintain test cases than using Excel. I like how easy it is to create new projects, create custom fields, create test runs, and generate good looking reports to submit to your managers. The GUI takes a little bit to get used to, but once you get a hand of all of the key-shortcuts moving around the application is easy!

Cons:

My least favorite part about this software is the JIRA plug in. In order to see the linked test cases from TestRail in JIRA, you need to have a TestRail account. In my company only the testing team had TestRail accounts, while the rest of R&D didn't. While it was helpful for me as a tester to see the linked test cases on a JIRA bug, when we started off with TestRail we had assumed everyone in the R&D department would be able to see this information so we could be more transparent in our testing. My company was not willing to pay for 100 TestRail accounts, so this was a bummer. If yours is then TestRail might be right for you!

Test rail : systematic arrangement for testing resources

Comments: Very very happy to use test rail, transition was. Smooth everything is arranged logically. Move copy delete all the features are available and easy to use.

Pros:

Test rail is very easy to use from creating the test plan to creating test runs.We can easily pull test cases as per our requirements and execute them as a test run.

Cons:

Test results uploads of videos is comparatively slow.Scree capture and voice recording features should also be there

Best test-case management tool.

Comments: TestRail can be a helping hand to the QA engineers. It can now be integrated to JIRA for easier project management and testcase management, User need not to keep track of both of them seperately.

Pros:

-TestRail provides easy management of test-suites, test-cases, test-runs. Easy management for maintaining agile methodology in the project. -Feature to export/import files for test-cases from xml, csv and xls files. -The provision to define milestones can be useful for maintaining release-wise goals. -The User can define the expected duration and priority for a test-case. - The representation and reporting are the best part of this software, the user can see the progress of the test-run in various formats as pie-chart.

Cons:

- Test results should be editable as required in some cases.

TestRail

Pros:

I enjoyed using the free trial (non enterprise) version. I think it one of the best test case management tools out there. Simple in use, intuitive, functional.

Cons:

I didn't encounter any major issues with TestRail.

Stellar Feature Rich Platform

Pros:

The ease of use for maintaining, connecting and sharing test cases are unrivaled. The platform is so feature rich every time I think of a feature I want to request they already have it!

Cons:

Takes a good amount of time to spin up a valuable framework. I think this can be mitigated by some test case best practices or maybe a super-user demo within the platform.

Alternatives Considered: CucumberStudio and Zephyr Enterprise

Switched From: CucumberStudio

Wonderful for testing and analytical reviews

Comments: I have used TestRail for the last five years for user acceptance testing and have used it for creating test cases, adding results viewing the history of results, creating reports, etc. It has been of great help for me and made my work as a QA very easy. I can't imagine working with excel and losing results due to some problem with my workstation or something, plus it becomes very difficult to maintain it in one place. TestRail is a great product and I highly recommend it.
I also thing TestRail can still take some inspiration from zephyr to include their reporting metrics and easier importing of test cases and their mapping.

Pros:

For me the best thing about TestRail is the visual representation of the test results in the form of graphs, This gives me a quick and easy idea about the stability of the tested software, another thing that is very useful is the format of test suites and test runs.

Cons:

I think importing testcases from excel can be made a little easier with better mapping and easy uploads.

TestRail: An Effective QA Suite

Comments: TestRail has been useful in my QA position for tracking the progress of test cases in our weekly regression runs. The framework it gives you for test case management is flexible enough to be used in a variety of ways for our company, whether for bug testing or tracking what tests have been automated over time.

Pros:

- The system of test suites (a master list of all your test cases) and test runs (individual lists of specific test cases) is well-built and allows you to manage your test cases easily. - Product is consistently stable. - Test cases in different parts of the product have synced states, which makes it easy to make changes to a test case when necessary. - Tools for sorting test cases in a run/suite are powerful.

Cons:

- There isn't a good tutorial for the product (or at the very least I never saw anything like a tutorial). As a result, it took me a while to notice some of the more unintuitive features. - Collaboration can be a bit clunky sometimes (multiple users editing a single test case, notifications at email level only).

Qualit Assurance Manager

Comments: I test software builds for a system which is installed into Taxis around the US. Each city has it's own configuration, rules and templates for printing & displaying info. There are several hardware configurations any taxi might have. By creating Projects based on functionality, I can copy/paste each required Project into a master Project then as a Test Run is created, check on/off individual Sections as needed and then test each build accordingly.
Having a report for each test Run allows management to go back & view each build's tes Run results when any "issue" is complained about by fleets/drivers to verify whether it was working or not in that build - as drivers are sometimes worse lairs than Lawyers or Politicians

Pros:

1- versatility to create Projects which allow base line Test Cases to be used in a variety of different test runs for different products. 2- ease of being able to import test cases from existing methods

Cons:

The main issue I have is the Projects are listed as a flat-file. We have several different groups which have created Projects and even though they might be testing a given entity from different sides, they have to name their Projects differently. We prefix each project with a Group Name so the Projects can be "grouped" and easily referenced from the main dashboard. Another less important issue is there isn't really an easy way to make a backup of our entire Dashboard. We can Export each Project but I don't see any way to make backups of anything else outside of offloading each individual entity which really isn't all that hard.

Title of my review

Comments: Overall the solution is one of the best I used in the past 10 years. Powerful test case management capabilities and API for automation so we can aggregate manual testing results as well as results from automation. But missing some collaboration features we are used to from google suite.

Pros:

- managed in cloud - powerfull customization options - easy to use - option of templates for TC

Cons:

- some reports are complicated to get, as who worked on what in the past quarter - to customize some stuff is sometimes quirky - hard to use for exploratory testing - collaboration on preparing test plan is a pain, it does not allow two testers add stuff to test plan simultaneously

Test Case Management tool with good customer support

Comments: We are able to clearly track the health of a build. With creating testplan we are able to track release readiness through milestones. Management can view report on mail or printout

Pros:

Appreciate easy integration with JIRA, this allows us to map test cases to JIRA task & defects. Test plan is another feature which we appreciate. It allows us to track our progress on milestones. Adding additional attributes to test cases also helped us to resolve some requirements like multi level reviews. Configuration is another option which we have used extensively.

Cons:

A direct integration with Confluence could be appreciated. We have always felt that tester needs to navigate to JIRA and to confluence to review any requirement change. As confluence is a widely used documentation tool and direct integration with the same would be widely appreciated.

Must have tool

Comments: We are using TestRail to manage automated tests on a variety of projects, from API tests to application acceptance tests. We've integrated TestRail into various CI platforms with ease.

Pros:

TestRail is powerful yet easy to learn and use. It is extremely flexible and we have not encountered any application of it that was not a perfect fit. It has been widely adopted by our QA and Dev teams.

Cons:

There are some admin features that could be easier such as managing users and grouping them for team access and policy rights.

Nice UI but there are a few features missing that would help track individual work

Comments: It's faster than free product, better interface and easy to use API

Pros:

The Test Cases Organization and flexibility to create tests. The possibility to add custom fields and that after, you can filter by those fields

Cons:

The way the Test plans are managed, there is no easy way to delete tests from a given configuration in a test plan and the reporting is very basic, not allowing Leads or managers to see progress for individuals

Test Rail high level review

Pros:

It is very intuitive. If one used other such tools for test documentation and tracking, it really very use to start with Test Rail.

Cons:

1) Configuration of the tool is a bit too rigid. I would make it more streamlined and have some admin features for configuration made available for regular users 2) Errors. Rather errors explanations. If possible to expand on what the exact issue is when we get an error.

TestRail review - QA perspective

Comments: Ability to quickly put together test plans, and use existing test cases in creating test plans make the overall experience better

Pros:

Easy to create test cases and ability to add test steps with screenshots which enable to describe the expected functionality/results clearly

Cons:

1.Do not have proper rich text fields where you can easily format the test steps without having to use syntax 2. Inability to combine multiple projects in a given test plan/test run 3. Inability to create dash board that shows results of multiple projects 4. Need to easy to use help documentation

Excellent Test Management Software

Comments: Excellent manual test management with the ability to integrate with our automated test software. Overall, we have a feature-rich and fully functional tool for our test management needs.

Pros:

The ease of use for this software has allowed our company to transfer from paper test sheets to logins for our end users. This test software had an answer and feature for every question we had.

Cons:

There's very little to dislike about this software. The report extract is a bit clunky. When a report is emailed to an email address, it's sent as a zip file with an html file. The extra steps required to view a report eliminate the usefulness of this feature.

Test rail : Manages test like a charm.

Comments: It has been a great experience working on this software.

Pros:

the process is very easy for writing test cases about a feature in development and assigning the same to the relevant story. Also, a user can assign and link multiple bugs to the same story which will be mapped with JIRA.

Cons:

Test rail is very comprehensive in nature and has various options to generate reports but the velocity chart and RTM can be improved.

Best Test Case Manager we have found

Pros:

We use it TestRails as a host for our Manual regression suite and report our selenium tests results too using the testrails API. Works very nice.

Cons:

Out company uses TFS and integration with TFS is not very good. The best we can do is link a failed test to a TFS dev task, and it only goes 1 way.

Easy to use

Comments: We liked the product but had a hard time integrating it with other software (Jira cloud version and TestRail cloud). But that was mostly our IT department not wanting us to connect that way. We moved to DevOps with it's Test Plan feature so had no need for TestRail anymore

Pros:

This was very easy software to use. We used the cloud version. We were able to quickly setup Test Plans and cases with reports to watch how we were doing quality wise. The printed versions and online print versions of test cases were very useful.

Cons:

The export wasn't as good as I hoped. It lost all the images we had stored in each of the test cases.

Awesome Life Cycle App

Comments: Organize my work and team members in the team

Pros:

It's pretty easy to learn and very quickly onboarding it

Cons:

No slack integrations very bad no have many integrations with other platforms