Qase Reviews & Product Details

It just makes testing less of a headache. I am an IOS developer, so my days are packed with builds, fixes, and release checks, and Qase never feels like extra work. I can write test cases, organize them, and kick off a run in a few minutes. It works nicely with Jira and our CI/CD pipeline, the support team actually replies and helps, and the AI features take care of a lot of the boring, repetitive test writing. Review collected by and hosted on G2.com.

Not much, to be honest. If I had to pick something, I would love a bit more flexibility in custom reports and dashboards, and a few extras for mobile-focused testing. But these are small wishes, not real problems, and the team keeps shipping updates. Review collected by and hosted on G2.com.

Qase is simple to start with and pleasant to use. Our software team at Pravesh Doors was able to move our test cases out of scattered spreadsheets and into one structured place within days. Test suites, test cases, and test runs are easy to organize, and the interface is clean, so new team members pick it up without long training. The Jira and Github integrations let us link test results to issues and track defects without switching tools. Reporting is clear, which helps us see pass or fail status and release readiness at a glance. Review collected by and hosted on G2.com.

Some advanced reporting and customization options could be more flexible, and very large test suites can feel harder to navigate. A few higher level features sit behind the more expensive plans. Review collected by and hosted on G2.com.

I like that it gives a clear overview of test result and progress at a glance. This way, it helps me and my team collaborate better by having all test information in one spot. Review collected by and hosted on G2.com.

So far I haven't faced any major issues and it meets all my requirements. Review collected by and hosted on G2.com.

Qase makes it easy to execute test cycles quickly and share reports publicly—two capabilities that matter most to me. Its Robot Framework integration sends automated test results directly to the dashboard, helping me investigate failures faster and reduce debugging time. The support experience also stands out. When I encountered an issue, I was connected directly to a support agent, who resolved it within two minutes. That combination of practical automation features and responsive human support makes Qase especially valuable in my day-to-day work. Review collected by and hosted on G2.com.

Defect tracking integrations are the main area where I would like to see improvement. The Jira integration workflow is not as smooth as I would like. In particular, having to create a defect in Qase before linking it to an existing Jira ticket adds an unnecessary step. Being able to link and track external defects directly would make the process simpler and more efficient. Review collected by and hosted on G2.com.

The run history is what I use most. Our Playwright CI jobs report into Qase, so each Business, Admin, and Mobile suite gets its own run instead of living only in a GitHub log. I open the dashboard, see which suite passed or failed, and open the failed case. Last week that was a Business portal login timeout on one run and a Mobile profile-activity check on another. A later Business portal run the same morning was green, and having both runs side by side made it obvious the first one was a session flake, not a product break. I also keep the run id when I write the Slack update or a Jira comment, so someone else can open the same result without me pasting a log. Review collected by and hosted on G2.com.

A cancelled CI job leaves the run empty. The reporter opens the Qase run when the job starts, and if GitHub cancels the job before it publishes results, the run stays In Progress with no cases and a 0 duration. Our weekly Admin portal jobs did this, so the dashboard showed runs that looked active when nothing had been executed. Closing or marking the run aborted when the job is cancelled would keep the history honest.

The results API is the other gap. I can list runs with the same token, but fetching results for the project returned 403. I then had to open each run in the UI, or go back to the GitHub log, to see which case failed. The token that can list runs should be able to read the results on those runs. Review collected by and hosted on G2.com.

I found the UI very clean and intuitive. The custom fields support is excellent, with plenty of options and configuration flexibility. The integration with Jira and testing frameworks is also a strong point, as well as the MCP support, which makes today’s AI-oriented programming and workflows feel smooth and easy.

The Starter Tier is priced really well for the features it offers, and it stands out compared with other tools that provide fewer features for more expensive subscriptions. The demo project also helped me understand how Qase works and how it fits into the different workflows across the testing process.

Coming from using spreadsheets with Gherkin-formatted test cases, being able to import them via a CSV file makes migration from our old system to this tool incredibly fast and straightforward, improving greatly the speed and pace of the testing process from start to finish. Review collected by and hosted on G2.com.

So far, I haven’t found anything to dislike, as it is a great improvement over our team's old processes. Review collected by and hosted on G2.com.

I use Qase to write test plans, manage test cases, and update results through different test cycle runs. Its interface and UI are simple to use and adapt, which makes it easy for me to manage and update test cases, track results, and monitor the time taken, especially when working with a larger number of test cases. Another aspect I appreciate is how Qase connects everything, allowing for seamless integration with JIRA. This feature is great because if a test case fails, I can raise a defect and link it directly to a JIRA ticket, keeping development, quality engineering, and management well-connected. I also found the setup process easy, making it simple to get started with. Review collected by and hosted on G2.com.

Maybe I should get notifications to run test cases which I am assigned with when a new test cycle is at the end or the deadline is reaching. More graphical analytics can be present in test cycle runs. Review collected by and hosted on G2.com.

Qase strikes the right balance between powerful test management and a clean, intuitive UI. Organizing suites, creating clear step-by-step test cases, and mapping them directly to product specifications is simple. Tracking test run progress in real time gives us immediate visibility into release readiness without clutter or unnecessary complexity. Review collected by and hosted on G2.com.

The pricing tiers can feel a bit rigid as a team scales. Some advanced reporting features and higher-tier API rate limits are locked behind higher enterprise plans, which can make scaling up cost-prohibitive for smaller teams that only need one or two specific advanced features. Review collected by and hosted on G2.com.

I like the test run part because I can perform the planned tests and send a report to people who do not have access to the platform. I also use a saved test plan whenever we release a new build version. With it, I can observe all possible areas of the project without forgetting scenarios that have already caused problems, and the team finds errors that previously went unnoticed. Review collected by and hosted on G2.com.

I think the bug registration could be improved. I can't implement the template we use in the company in Qase or categorize the custom fields. The AI also crashes when we ask it to generate a test or perform it automatically, even when it was working minutes before. I also can't customize the sending of bugs from Qase to ClickUp, so I need to change the fields there. This is laborious and can make us forget something, so I prefer to register the bugs directly in ClickUp. Review collected by and hosted on G2.com.

I like having one portal where my team can work together and keep our test cases organized. The review feature keeps our repo clean by making edited test cases go through a review process before they’re merged. Shared steps let me create a test-step skeleton in advance, reuse it, or edit it, which helps me speed up creating test cases. Qase is easier to maintain than online sheets, and we don’t get the unsynced updates we had there. Once we uploaded everything and started using the new flow, working with test cases became much easier. I also find it helpful that our automation scripts can update test-run results, and that the Qase API lets us use AI for parts of our workflow, like putting test cases into a template and uploading them to the desired topic. Review collected by and hosted on G2.com.

I’d like a way to reference test data in my test cases and maintain it centrally. Our test data changes often, and I’d like to reference values like usernames, passwords, or product IDs. Moving everything into the Qase template also took time. Review collected by and hosted on G2.com.