CucumberStudio, from SmartBear vs. TestRail

HipTest is good and helpful to create and run functional regressions but it is more complicated to use this tool to create and run API testing scenarios (it does not mean it can not be done). This tool is definitively not appropriate for running performance testing scenarios.

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

• Good integration with Jira
• Includes integration with different tools for different porpuses
• You can build your own framework to automate scenarios and make it work with Hiptest

Incentivized

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

Incentivized

• UX is not too obvious and easy (like generating a data table in a scenario or including a scenario in a test run) but you can get used to it relatively easy by playing around with the options, also the documentation is helpful.
• To get extra functionalities you have to pay for them separately.

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

The tool includes a basic but complete documentation that can be very helpful to get started using the tool. The UX sometimes does not feel very easy to understand but after some use you can get familiar without reading the documentation. The webinars are not very useful for using the tool, I have seen a couple of them and they are actually focused on promoting their HipTest product to new users instead of being useful and educational for current users.

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

• It helps to have organization in our scenarios.
• It helps to get regressions done faster than doing it manually
• It helps to graphically see the progress and results of executions.

Incentivized

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

Incentivized