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.

Honestly, what won me over early on was how little explaining I had to do. I rolled it out to the team and people just.. figured it out. No two-hour onboarding call, no thick documentation. For a team lead juggling sprints and reviews, that alone was worth a lot.

The structure around suites, shared steps, and test runs is sensible. Nothing flashy, but it stays out of your way. I also appreciate that the roadmap actually moves - I have seen real improvements ship over the months, which isn't something I can say about every tool I have used. Review collected by and hosted on G2.com.

Once you scale past a certain point, the cracks start showing. Search feels sluggish with a heavy test suite, bulk operations are more limited than they should be, and the reporting layer is where I personally hit the wall - gettinh a clean view to share with stakeholders often meant exporting and reworking it elsewhere. The Jira sync also has its moods.

None of these are dealbreakers, but together they add friction in a role where you are already context-switching constantly. Review collected by and hosted on G2.com.

I really liked the UI of Qase. It's not too compact and heavy. The platform is easy to understand and use, especially for me as someone who hasn't used test management tools before. It fulfills our needs in terms of QA management. I also like the no-code automation, even though I haven't explored it that much yet. It really helps, especially for our team that doesn't have a coding background and handles multiple tasks. The low to no-code automation generation of Qase can really help us. The support team at Qase is very swift in replying to our concerns, and the initial setup was very easy because of its UI and tutorials. It only took us weeks to adapt. Review collected by and hosted on G2.com.

The thing that needed to improve that I really noticed is the test report. I wish that they will improve the test report. I noticed that there are so many whitespaces in the test report when extracted to PDF. Though the details are complete, it generates many pages and whitespace. Review collected by and hosted on G2.com.

1. Visibility of both manual and automated tests

2. Easy access to historical data

3. Fast customer support.

4. Rare issues with performance or timing.

5. Out-of-the-box integrations with the most popular frameworks and ability to customize reporters.

6. Reasonable price! Review collected by and hosted on G2.com.

1. Dashboards and queries - not possible to customize to our needs (e.g. filtering and sorting by custom field value is absent)

2. No shared Gherkin steps Review collected by and hosted on G2.com.

One word: organized.

The way QASE keeps everything structured for all the projects, test cases, test runs, and results making it a wonderful, easy-to-use tool. We started testing very early in a startup, when we didn’t yet have clearly defined requirements, and having that level of organization from QASE made it much easier to stay on track.

Also the customer support is top notch. Review collected by and hosted on G2.com.

The integration worked well for linking defects and test cases, but I found synchronization limitations when updates were made after the initial creation. Ideally, I'd prefer tighter bidirectional synchronization to reduce duplicate work Review collected by and hosted on G2.com.