EasyQA vs. TestRail

The complexity of the product is too high, so even changes to a single feature impact many other functionalities. Using EasyQA has helped us create multiple test cases where the feature may have its effects and test and track the progress on as many related functionalities as possible.

Incentivized

The integration with other tools, and their user friendly layout and design. It's very comfortable to use and is way better than other tools with the Automation Testing tools, thanks to the great API that is included. Sometimes the integration with Jira is a little faulty, but the links to that tool usually work well. It could be cool if it had a better following for the bug items that were registered on other tools.

Incentivized

• Creation of test cases for new features
• Management of created bugs
• Bug tracking and analysis

Incentivized

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

Incentivized

• In my experience, they provide poor support
• The application is still a bit buggy

Incentivized

• Integration with Jira seems [a] little faulty.
• Increase the API call limit for different editions.
• Better way to trigger automation suites from TestRail.

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

• Improved test management process and collaboration inside team.
• Increased transparency of QA work.
• Team became more satisfied.

Incentivized