G2

Ken O.

QA Automation Engineer

Small-Business (50 or fewer emp.)

9/30/2026

"Clear CI Run History in Qase Makes Failures Easy to Spot"

5/5

What do you like best about Qase?

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.

What do you dislike about Qase?

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.

What problems is Qase solving and how is that benefiting you?

Before Qase, a failed CI job was a GitHub log. I had to scroll the log to see whether Business, Admin, or Mobile had failed, and I could not hand someone a single place to look. Each job now opens its own run, so I open the dashboard, see the pass and fail count, and open the failed case. When the same Business portal suite failed in the morning and passed on the next run, the two runs side by side showed a login flake rather than a product break. I paste the run id into Slack or Jira, and the person reading it opens the same result instead of asking me for a log. Review collected by and hosted on G2.com.