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.

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.

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.

What I like most about Qase is how straightforward it is. You don’t need a lot of time to get used to it-the UI is clean, and everything is where you expect it to be.

Creating and organizing test cases is easy, and it doesn’t feel heavy like some other test management tools. I use it daily to manage test cases, track runs, and it handles that without any confusion. The ability to link test cases with runs and see results clearly helps a lot during releases.

Integration is also a big plus. It works well with tools we already use, so it fits into the workflow instead of forcing us to change how we work. Review collected by and hosted on G2.com.

There are a few small things. Sometimes the UI can feel a bit limited when you are working on large test suites-filtering and navigation could be a bit smoother.

Also, reporting could be improve. It works, but for more detailed insights or custom reports, you may still need to rely on external tools.

Nothing major, but these improvements would make it even better. Review collected by and hosted on G2.com.

What I like best about Qase is how simple it is to manage test cases and test runs in one place. It keeps everything well organized, so it's easy to track what is tested and what is pending.

I also like its clean interface, which makes it easy to use without much learning. It helps me save time and keeps my testing process clear and structured. Review collected by and hosted on G2.com.

What I dislike about Qase is that a few features are not very clean at first, so it takes a bit of time to get comfortable with them.

But once I understand how things work, it becomes smooth and easy to use. Overall, it's a small learning curve and not a major issue. Review collected by and hosted on G2.com.

Qase makes testing easy to understand and easy to track. Everything is in one place-test cases, test runs, results, and bug links. I can quickly open the dashboard and know what's going on without asking the QA team. It gives a clear view of what is tested, what failed, and what is still pending.

I also like how structured it is. Test cases are written in a clean way, so even if I didn't create them, I can still understand the flow. This helps when reviewing features or checking if edge cases are covered. It also helps during releases because I can quickly confirm if critical flows are tested or not.

Another useful thing is visibility. I don't need to wait for reports or meetings. I can directly check progress anytime. This saves time and helps me stay involved without interrupting the team. Overall, it makes testing more transparent and less dependent on manual updates or communication. Review collected by and hosted on G2.com.

Some parts still feel manual, especially when updating test cases after frequent product changes. If features are evolving fast, maintaining test cases takes extra effort. Also, organizing or searching for specific cases could be a bit smoother. Review collected by and hosted on G2.com.

What I like most about Qase is its simple and clean interface. It makes creating and managing test cases very easy, even when working on big projects. I can quickly organize test suites, reuse steps and keep everything in order without much effort. The integration with tool like Jira and CI/CD is also useful, as it helps keep testing connected with development work. Overall, it saves time and keeps things well organized. Review collected by and hosted on G2.com.

There are a few things that can be improved. Sometime it feels a bit slow when working with large test suites, and the reporting options could be better and more flexible.

Also, for new users, some features are not very easy to understand at first, so better guidance inside the tool would help. Review collected by and hosted on G2.com.

The UI is genuinely clean and doesn't take forever to onboard new team members, which was a big plus coming from older tools. Shared steps and test case suites save a lot of repetitive work, and creating test runs is quick once your cases are set up. The free tier is also surprising usable for smaller teams. Review collected by and hosted on G2.com.

Reporting feels basic once you actually need to dig into trends or generate something for stakeholders. The Jira integration works but isn't always reliable, and search starts to struggle when your test suite grows large. Bulk editing could also use some love. Review collected by and hosted on G2.com.

What I like best about Qase is how it balances simplicity with structure. It makes managing large sets of test cases feel organized without becoming overwhelming.

The test case management is especially strong-creating, grouping, and reusing test cases across different runs is smooth and saves a lot of onboard team members, since the UI is clean and doesn't require much learning curve.

Another highlight is its integration capability. Syncing with tools like Jira and CI pipelines helps keep development and QA aligned, which is critical in fast-moving environments.

Overall, it reduces manual effort while still giving enough control to manage complex QA workflows efficiently. Review collected by and hosted on G2.com.

There is nothing major to dislike about Qase. Some feature like reporting could be more advanced, and performance can slightly slow with very large test suites- but overall, these are minor and don't affect daily workflow much. Review collected by and hosted on G2.com.