A pragmatic approach to QA and OPS


Playwright Logo

If you’re a QA and have been working on Automation and do research about the latest tools and technologies, chances are you already know what Playwright is.

In case you’re not, let me tell something about Playwright. It is a shiny new toy in the JS e2e testing space. And it is maintained by Microsoft. Yeah the same Microsoft, whose CEO Steve Ballmer once criticised Linux and Open source in general as cancer. However, times have changed and now Microsoft is going big on open source, including purchase of the open source version control system Github.

Well, that’s another story, but we’ll divert our focus towards Playwright, a new shinning armour that lets to run e2e test cases, play around with Chrome Devtools, supports mocking and network intercepting and even has a new shot in arm where it supports component testing. And most important of them all, it is in no way dependent on Selenium and Webdriver bindings.

Playwright utilises the Websocket connections and relies heavily on the CDP protocol. And there are a lot of other great features that makes it stand apart among the plethora of e2e testing tools.

Since Playwright is comparatively new in the market, there is no repository of questions that can be asked in the interviews. There are lot of good tutorials and videos , like one from Naveen Automation Labs and one from Kaushik Chatterjee, but there is no question repo, which can be used for a quick look on the questions that may be asked.

I’ve been working with Playwright for the last ~1.5 years and so I thought I should create a repo of questions that can be used by anyone. So I have created a series of Playwright questions and will keep on updating the links as the questions series keeps going live.

  1. PLaywright Questions Set 1 -> Link
%d bloggers like this: