Playwright interview questions that you are going to love
Playwright interview questions for Mid and Senior level quality assurance automation engineers
Latest
Playwright Interview Questions that you are going to hate
Everybody hates it when they go to an interview and they are given live coding challenge that is written intentionally to make you fail, so the interviewer can prove his "superiority". Here are 12 playwright interview questions and answers, so you can have the advantage this time.
Playwright with Allure Reporter published on AWS S3 Bucket - full parallelization
What is the journey we are going to embark on to today?
* We will setup a Playwright framework with focusing on settings about full parallelization
* Install Allure-playwright as reporter and configure to preserve history and trends using AWS S3 buckets
* Configure AWS User to perform CLI commands in our github
Playwright tips and tricks #3
It's time to have a look under the hood of Playwright and understand a few details that will enhance our skills to be more creative.
1. Get more details about your test during test run
There is a way that you can access some particular values related to your test
Full parallelization in Playwright
How many workers should we setup in our config ?
How many shards should we use in our CI ?
Do we need fullyParallel true in Playwright config ? What does it even mean?
If you ever asked any of these questions, then you are in luck. Here is a way you can
Debugging with Playwright
Of course you know how to do debug your tests. Everybody knows how to do it. But not everybody does it in the same way. Here are a few ways to debug your tests using playwright
Debug using Playwright trace viewer
One of the most commonly used method is to
Playwright tips and tricks #2
I've written a post about tips and tricks and it got a lot of love. So, I've decided to do another one.
1. How to handle an element that appears after full page load in playwright
One of those rare cases where an element will appear in DOM only after
Playwright tips and tricks #1
As you work with a framework you start to encounter various situations from which you can learn. Things that you find out are really important and are not that easy to discover just by reading the docs or following tutorials. Things that come with experience. I would like to share
Publish your playwright reports to github pages
What I am looking to achieve here is a free solution to have my reports published into separate sub-directories, accessible at an unique link that I can easily put in my Jira ticket, github issue or other test management tool, so I can show my client/manager/team what is
Which one is better? Selenium with POM or Cypress without POM
One of the best things about trying various frameworks and designs is that you have the possibility to directly see how it "feels" and have a better understanding of what suits best for your present or future projects.
I have done the Different Angle Challenge and I have created the
![How can I learn [more efficient] a new testing framework ?](https://images.unsplash.com/photo-1603468620905-8de7d86b781e?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3wxMTc3M3wwfDF8c2VhcmNofDE4M3x8Y29kaW5nfGVufDB8fHx8MTY4NTkxMjQxMXww&ixlib=rb-4.0.3&q=80&w=720)
How can I learn [more efficient] a new testing framework ?
There are so many languages and software testing frameworks out there that sometimes it feels overwhelming. You have Selenium, Cypress, Playwright, TestCafe, Protractor, Robot Framework, TestComplete, Karate, Nightwatch.js, Webdriver.io and many more. You may find yourself in a situation where a new project will require you to learn
Organize your Selectors in Automation Frameworks with Cypress
When it comes to software testing frameworks, selectors play a crucial role in making the code reusable, modular, and efficient.
In the past, I used Object-Oriented Programming (OOP) and Page Object Model (POM) with Python and Selenium. Back then it made sense to keep selectors as part of each page
Cypress cross-origin testing
How to handle multiple origins/domains in a single test.
One of the things that are not that easy to understand is how cy.origin works. How to test with Cypress a flow that implies multiple domains. I have a small Romanian QA Community in discord where we debate various