For some time now I've been playing with github actions to see if I can easily reproduce behaviors I apply in my current CI tool. I wanted to parallelize tasks

E2E enables extensive testing as soon as the changes are available. It has a chance of catching potential issues before merging changes to the main branch.

Sometimes, when working in a team or open source organization, you may misspell a message or make errors in your repository's commits

In this post I will go through all the info you need to integrate Playwright in your CI without any problem.

Today I'll speak about a beta feature in Playwright: Components.

Today I want to speak about Fixtures, a vital friend if you're going to work with Playwright and you want to share data between your tests.

Today you will learn how to generate the code for your tests.

Playwright Test for VSCode allows you to install Playwright in your projects or add new browsers configuration, but today the goal is the debug.

In this post, you will learn how to write tests with Playwright, using assertions, locators and more.

Playwright is a testing framework to handle e2e testing. With Playwright we can write e2e tests and run them in different browsers, like Chrome, Firefox and Web

As are most questions worth asking, the answer is nuanced and could be boiled down to it depends.

In this article, I will demonstrate the testing approach I’ve been using successfully in a project I’ve been working on for the past 8 years.

Flaky tests are tests that fail even though they should pass. Because of the complexity of an E2E, it’s unlikely to have them as stable as unit tests.

Maintaining the same E2E coverage will require more and more tests—and their execution time will add up.