Kualitee vs. TestRail

From a business standpoint, features such as test scenarios, test cases, bug logging, and then graphical representations of every minute detail related to task and projects are very satisfying and productive. We can keep track of literally everything with Kualitee, and our quality is improving. One downside is that we cannot change the visualisations of some graphs. I believe that by giving the user more customisation options, such as filtering out on the basis of days and months, the experience could be greatly improved.

Incentivized

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

Incentivized

• Import and Export
• Integration with other tools
• Regression and Blackbox testing

Incentivized

• Beautiful and productive UI.
• Nice filtering system allowing me to find what I need quickly.

Incentivized

• Support response time
• Should have dark mode
• Response time for API call

Incentivized

• UI has a lot scope of improvement
• Uploading of test screenshots and managing them can be more effective
• User experience can be improved
• Tracking of tests can be more simplified

Incentivized

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

Incentivized

TestRail is very costly and complex compared to Kualitee

Incentivized

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.

Incentivized

• If the terminology ( Test Scenarios, modules, components ) is not used in your workflow, it may take some time to set up properly because you must figure out how these are defined by your own terminology to get the hierarchy correct

Incentivized

• We are able to easily pull reports any time management would like to see them
• Jira integration makes it easy to attach to stories/defects and save time
• A quick overview at the system's health as a whole is easy to see from TestRail

Incentivized