Insights on test automation, quality engineering, and software development best practices.
Part 2 of 'How To Succeed as an SQA Engineer' offers practical tips for SQA professionals to boost team performance. It covers creating mind maps to understand product architecture, analyzing upstream/downstream systems, assessing the tech stack, and evaluating testing infrastructure.
This blog post outlines five essential strategies for Software Quality Assurance (SQA) engineers to succeed with their teams: implementing the Pareto Principle, breaking work into manageable chunks, maintaining transparency, dedicating time to continuous learning, and recognizing that quality is a shared team responsibility rather than an individual burden.
How to automate APIs using the Microsoft Playwright framework with TypeScript and build a custom framework.
Discover why Playwright isn't waiting for elements as expected in your automation tests. Learn practical solutions to handle timing issues, including strategies for web tables and text lists.
Learn Playwright automation efficiently with this strategic approach for QA engineers. Discover how to build a strong foundation, layer your skills, and master Playwright step-by-step. Perfect for both experienced testers and beginners looking to enhance their test automation capabilities.
Discover best practices for Playwright locators to build robust test automation frameworks. Learn to prioritize user-facing attributes, leverage advanced techniques, and use the Locator Picker tool effectively. Gain insights on creating stable, maintainable tests for complex web applications.
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.
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() assertions 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 major danger lies behind it.
Let's take a deeper dive into the subject to determine which of the two frameworks is a better fit for your project or organization. Let's go!
Cucumber is one of the most well-known tools in test automation. What is less well known is how widely this tool is misused. 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.