#1 India's Top IT Training Institute
×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
Mentors

Mentors

Meet the industry experts who train and guide you through your course.

Read More →
Free Resources

Free Resources

Free tutorials, interview questions, tools and calculators to help you learn.

Explore →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
Playwright Interview Q&A · #37

What are the limitations of Playwright?

By Uncodemy Editorial Team · Updated 16 Nov 2026

Playwright is a strong browser automation tool, but it is not a universal testing tool. A good interview answer names the real limits, explains why each one exists, and gives the usual workaround. Here they are, grouped by the question a tester would actually ask.

"Can I test on real Safari and real phones?"

A typical config still covers a lot of ground, as long as everyone knows the last project is an emulation:

// playwright.config.ts
import { defineConfig, devices } from '@playwright/test';

export default defineConfig({
  projects: [
    { name: 'chromium', use: { ...devices['Desktop Chrome'] } },
    { name: 'firefox',  use: { ...devices['Desktop Firefox'] } },
    { name: 'webkit',   use: { ...devices['Desktop Safari'] } },   // WebKit build, not Safari
    { name: 'mobile',   use: { ...devices['Pixel 7'] } },          // emulated phone
  ],
});

See which browsers Playwright supports and how mobile emulation works.

"Can it test things outside the browser?"

"Can it get past security checks?"

No, and it should not. CAPTCHAs, bot detection and SMS one-time passwords are designed to stop automation. The correct fix is in the test environment: use the CAPTCHA provider's test keys, a fixed OTP for test accounts, or an API-based login that skips the UI step. Ask the developers for a test hook rather than trying to beat the check.

"Does every language get the same features?"

The browser API is available in TypeScript/JavaScript, Python, Java and .NET. The test runner (fixtures, projects, retries, sharding, the HTML reporter, toHaveScreenshot) is the Node.js package @playwright/test. Python teams use the pytest plugin, and Java or .NET teams use JUnit, TestNG, NUnit or MSTest, so some runner features differ or need extra set-up. See using Python with Playwright.

Practical costs

How to phrase it in an interview

Say that Playwright covers modern web apps across three engines very well, then list two or three limits with workarounds: WebKit is not real Safari, mobile is emulation, and CAPTCHAs need test keys. That shows you have used the tool rather than memorised a feature list. For the other side of the picture, read the main features of Playwright.

Want to master Playwright hands-on?

Join Uncodemy's Playwright Automation Testing Course in Noida — Dedicated Placement Support.

Explore the Course →