Tech with Jatin
Join 10,000+ Learners

Playwright TypeScript Last-Minute Notes

The night before your interview: all 48 Playwright TypeScript answers in short form, in one sitting.

The 48 Playwright TypeScript interview answers in short form, with every diagram. For the night before your interview.

  • 30 pages
  • 12 parts
  • 48 questions
  1. Buy
  2. Instant download
  3. Prepare part by part

The night before, a full playbook is too much

What you need on the last evening:

  • The key points only, not paragraphs.
  • The questions asked most often, marked so they come first.
  • A picture per topic they can redraw from memory in the interview.

With these notes you can

  • Revise all 12 parts of the Playwright TypeScript Interview Playbook in one evening.
  • Remember one line per answer when you are nervous.
  • Redraw a diagram per part to explain architecture, locators, fixtures or CI.
  • Start with the questions marked Asked often.

Look inside

The first 3 pages of 30, exactly as you get them. Swipe, then tap a page to enlarge it.

  • Preview page 4 of 30, locked
  • Preview page 5 of 30, locked
  • Preview page 6 of 30, locked

Buy to unlock all 30 pages

Full table of contents

All 12 parts and 48 questions, exactly as they appear in the PDF. Tap a part to see its questions.

Part 1. Playwright Basics and Architecture4 questions
  1. Your company runs Selenium. Why are teams like yours moving to Playwright?
  2. One test must show an admin and a customer working at the same time. How do Browser, BrowserContext and Page make that possible?
  3. Which browsers does Playwright support, and what is the difference between bundled Chromium and the Chrome channel?
  4. How do you set up a Playwright TypeScript project from scratch?
Part 2. TypeScript for Testers5 questions
  1. Why use TypeScript instead of JavaScript for Playwright tests?
  2. What are interfaces and types, and where do you use them in a test framework?
  3. A test sometimes fails with "Target closed" and sometimes passes. You suspect a missing await. Explain what is going on.
  4. What are generics, and how do they help in a test framework?
  5. How do you manage environment config and secrets in a Playwright TypeScript framework?
Part 3. Locators5 questions
  1. Your element handle throws errors after the page re-renders. Why do Playwright locators not have this problem?
  2. Which locator strategy do you recommend, and in what order?
  3. How do you work with lists and tables using filter, nth and chaining?
  4. A card payment form sits inside an iframe and a cookie banner lives in shadow DOM. How do you automate both?
  5. How do you generate and debug locators quickly?
Part 4. Auto-waiting and Assertions5 questions
  1. What is auto-waiting, and what does Playwright check before it performs an action?
  2. What are web-first assertions, and why are they better than reading a value and checking it?
  3. Explain soft assertions, expect.poll and toPass.
  4. What are the different timeouts in Playwright, and what are their defaults?
  5. How do you do visual testing with toHaveScreenshot?
Part 5. Test Runner, Config and Projects4 questions
  1. Walk me through the important settings in playwright.config.ts.
  2. You must run one suite on Chrome, Safari and a phone viewport, after a login step. How do projects handle this?
  3. How do you organise and filter tests with describe, tags and annotations?
  4. How do you run tests in order when a flow truly needs it?
Part 6. Fixtures and Hooks3 questions
  1. Every spec file starts with the same 20 lines of setup. How do Playwright fixtures fix this?
  2. What is the difference between test-scoped and worker-scoped fixtures? What is an auto fixture?
  3. When do you use beforeAll and beforeEach hooks instead of fixtures?
Part 7. Page Object Model and Framework Design3 questions
  1. The same login locators are copied into 30 test files. How would you refactor this with the Page Object Model?
  2. How would you design a scalable Playwright framework? Walk me through the folder structure.
  3. Two parallel tests keep editing the same student account and fail at random. How should test data be managed?
Part 8. Network Mocking and API Testing5 questions
  1. How do you mock or change network responses with page.route?
  2. After clicking Place order, you need the order id from the API response. How do you capture it reliably?
  3. Can Playwright test a REST API without opening a browser? Show how.
  4. You want to create an order quickly through the API, then check it on screen. How do you mix API and UI in one test?
  5. What is HAR recording and replay, and when would you use it?
Part 9. Authentication and Sessions3 questions
  1. Every test spends 6 seconds on the login screen. How do you remove that cost?
  2. How do you test an app with several user roles?
  3. How do you handle OTP, 2FA and captcha in automated tests?
Part 10. Debugging and Flaky Tests4 questions
  1. A test failed in last night's run. Which tools do you open, and in what order?
  2. What is the Trace Viewer, and what does it show?
  3. Your checkout test is green on your laptop and red in CI every third run. Walk me through your investigation.
  4. Your suite has 15 tests that fail at random. Which causes do you look for, and how do you fix each one?
Part 11. Parallel Runs, CI/CD and Docker4 questions
  1. You set workers to 4. What actually runs in parallel, and what must your tests do to stay safe?
  2. Your suite takes 40 minutes on one machine. How do you split it across 4 CI machines and still get one report?
  3. Your team wants every pull request tested automatically. What does a Playwright pipeline look like?
  4. Screenshots differ between your laptop and CI because fonts render differently. How does running Playwright in Docker fix this?
Part 12. Playwright with AI3 questions
  1. Your manager asks how an AI assistant could explore the app and draft tests. Explain Playwright MCP.
  2. How would you use AI in your testing work without lowering quality?
  3. What are Playwright test agents (planner, generator, healer)?

A real page from the notes

Your element handle throws errors after the page re-renders. Why do Playwright locators not have this problem?

  • A Locator is a recipe for finding an element, not the element itself.
  • It is lazy: it searches the page every time you use it.
  • So it survives re-renders and works with auto-waiting.
  • It is strict: an action fails if the locator matches more than one element.

Remember: Locators are lazy and strict.

Who it is for

This is for you if

  • You have an interview in the next day or two and need to revise, not learn.
  • You already went through the full Interview Playbook and want the short version.
  • You learn better from diagrams and one-line summaries.

It is not for you if

  • You are new to Playwright. Start with the full Interview Playbook, which teaches each answer with code.

What is inside

  1. 48 answers in short formThe key points to say and the one line to remember, for every question in the Playwright TypeScript Interview Playbook.
  2. One diagram per part12 parts, from architecture to Playwright with AI. Redraw each from memory.
  3. Asked oftenThe questions to revise first are marked.

PDF, 30 pages. Works on phone and laptop.

From Jatin

Jatin Shharma

12+ years in test automation at Infosys, HERE Maps (originally Nokia Maps) and B2X. Client work for BMW and Audi, including self-parking car automation.

More about Jatin

Questions

How is it different from the Interview Playbook?

The playbook is for learning, with full answers and code. These notes are the short version for revising.

What format is it?

A PDF you can read on your phone or laptop and print if you like. The download link comes to your email and stays in My purchases.

Do I get updates?

Yes. Everyone who has it gets every update, and fresh links always download the newest version.

Do I need the full playbook too?

The notes are the short version of the free Playwright TypeScript Interview Playbook. Use the playbook to learn and these notes to revise.

Revise in one evening, not one week

48 answers, 12 diagrams, 30 pages.

Price: ₹199
$4 if you pay by card from outside India

Also in a bundle

Cover of Playwright TypeScript Interview Bundle
Playwright TypeScript, 2 PDFs, Bundle

Playwright TypeScript Interview Bundle

The Coding Round Playbook and the Last-Minute Notes together. Rs 698 if bought separately.

Price: ₹549
$11 outside India
Get now
Cover of SDET Interview Complete Bundle
Playwright and Selenium, 5 PDFs, Bundle

SDET Interview Complete Bundle

All five paid playbooks and notes: Playwright TypeScript, Playwright JavaScript and Selenium Python. Rs 1,895 if bought separately.

Price: ₹999
$19 outside India
Get now