A big variety of articles and resources

Playwright and Cypress, two leading UI automation frameworks in 2024. I break down their key features, limitations, and coding experiences, providing practical examples to illustrate their differences. Whether you're building a small project or scaling up your testing infrastructure, this guide will help you make an informed decision between these powerful tools.

Blog Templates

This article explains the "playwright timeout 30000ms exceeded" error, a common issue in Playwright testing. It covers five types of Playwright timeouts, explores three main causes of this error, and provides practical solutions, including adjusting timeout durations, optimizing locators, and mocking slow endpoints. The article also offers best practices for handling timeouts and creating more robust Playwright tests.

Master Playwright assertions with our comprehensive guide. Learn the key differences between generic and locator assertions, best practices, common pitfalls, and expert tips for writing stable, efficient automated tests.

The most popular git commands for every test automation engineer. All typical use cases. Grouped by the subject for easy navigation

What is the difference between the toBe() and toEqual() assertion in Playwright?

Using {force: true} often can be a quick solution for non-clickable web elements in Playwright or Cypress. At first, it may seem like a great solution but a big danger is hidden behind it.

Let's deeper dive into the subject to understand, which of the two frameworks will be a better fit for your project or your organization. Let's go!

Cucumber - is one of the most well-known tools in the world of test automation. What is not so well-known - is how misused this tool is. Let me try to explain and demonstrate why in 99% of the cases, test automation projects do not need Cucumber. There is a better way.