Playwright + Qase: Fast Wins and When to Look Beyond

By Eduard Dubilyer , CTO of Skipper Soft

Introduction: Quick Wins with Playwright + Qase

When you start building a test automation framework, one of the first things you want is fast visibility: run your tests, see the results. The integration between Playwright and Qase provides exactly that. In just two lines of configuration, you can connect your test runs to a reporting portal. For early-stage frameworks, this is an excellent solution.

But as your framework grows and the volume of test activities and results increases, Qase alone won’t cover all your needs. That’s when you need to start thinking about more advanced reporting and management solutions. We’ll get to that in a future discussion. For now, let’s look at the value Qase delivers and its limitations.

Setting Up: Two Lines to Reporting

1. Install the Qase Reporter:

npm install -D playwright-qase-reporter

2. Configure in playwright.config.js:

reporter: [
  ['playwright-qase-reporter', {
    testops: {
      api: { token: '<YOUR_QASE_TOKEN>' },
      project: '<PROJECT_CODE>',
      uploadAttachments: true,
      run: { complete: true },
    },
  }],
]

That’s all it takes to start sending test results directly into Qase’s portal.

Strengths of Qase Integration

1. Perfect for Early Stages

If you just need to run a suite and immediately see a structured report, Qase is ideal. It lowers the barrier to visibility and helps teams get organized quickly.

2. Built-in Bug Logger

Qase isn’t just a reporting tool; it also offers a strong bug logging feature. You can link failed test results to bug tickets, ensuring better traceability between issues and test outcomes.

3. Attachments: Screenshots and Videos

One of the standout features is that, with uploadAttachments: true in your config, you can automatically capture screenshots and video recordings from Playwright. This makes debugging much easier, especially when sharing results across distributed teams.

Example Playwright settings:

use: {

screenshot: 'only-on-failure',

video: 'retain-on-failure',

}

This ensures that whenever a test fails, you get both a screenshot and a video for analysis in Qase.

QASE Test Runs Report Example

The Limitations

1. No Real-Time Step Progress

While Qase provides excellent post-run reports, it doesn’t show the real-time progress of tests at the step level. If you need to watch your test steps execute live, you’ll have to rely on Playwright’s local reporters or other dashboards.

2. Scaling Beyond Basics

As your framework grows—more tests, more projects, more environments—you’ll hit a ceiling. At this stage, you’ll need to think about complementing Qase with additional reporting solutions or building custom dashboards.

QASE Dashboard Example

Final Thought

The Playwright + Qase integration is a fantastic starting point: lightweight, quick, and effective. You can run your tests, get instant reporting, attach logs, screenshots, and videos—all with minimal setup. For the beginning of your automation journey, this is hard to beat.

But don’t stop here. As your automation matures, the demands on reporting and visibility will grow. That’s when it’s time to expand beyond Qase into more advanced solutions. And that’s a topic we’ll explore in the next article.