Choosing a Playwright language can seem like a straightforward engineering preference: use the language your team already knows, install the binding, and start automating. At the browser level, that assumption largely holds. Playwright provides the same fundamental automation capabilities across TypeScript, Python, Java, and .NET, so the core mechanics remain familiar. The more meaningful differences…
Microsoft Dynamics 365 is a powerful and expansive platform. It is an amazing set of tools for businesses that need to build ERP or CRM apps tailored to their needs. From a QA perspective, however, Dynamics 365’s broad range of capabilities, modules, and integration options can be deeply challenging. When there are so many ways…
The cheapest AI-generated Playwright test can become the most expensive test in the suite if an AI agent has to reason through it every time it runs. That is the uncomfortable part of AI-assisted Playwright testing. Enterprise teams often want the speed of AI agents and Playwright MCP, while the organization quite reasonably ask two…
At first glance, migrating tests from Cypress to Playwright might seem fairly straightforward. Both frameworks employ similar concepts, such as test suites, assertions, selectors, fixtures and browser automation. In most cases, there’s no need to redesign test suites from the ground-up. But if you actually dive into the migration process, you’ll likely find that moving…
RSAT support ends after May 15, 2027. Playwright can automate Dynamics 365, but that does not automatically make raw Playwright the right replacement for everything RSAT provided. For some teams, Playwright will be an excellent foundation. For others, replacing hundreds of RSAT tests with code could turn a migration into a software-engineering project. The real…
If you’re a Salesforce Lightning QA engineer, you face a variety of challenges unique to your role. Issues like Shadow DOMs, dynamic IDs, and asynchronous rendering can make it especially challenging to design, write, execute, and manage tests for Lightning apps. Meanwhile, you’re doing this work as teams face pressure to release application updates early…
Note: This is part one of a series about the challenges that come with managing Playwright at scale and solutions for addressing these issues. Every software development and QA team hits meaningful milestones in their work. Sometimes, these milestones celebrate achievements, like pushing a large software release. Other times, they include challenges, such as scaling…
Every organization has growing pains, whether it’s scaling systems, managing budgets, or picking the perfect coffee maker for the new office. Software testing’s chief challenges typically fall into two fundamental categories: technical and organizational. The challenges engineers tend to home in on are the technical ones. Issues like test degradation, environmental mismatches, and time synchronization…
If you ask a roomful of QA engineers how to fix a flaky test, you’ll receive no shortage of answers. “Add retries, improve synchronization and stabilize test data,” some will tell you. “Isolate dependences and update selectors,” others will say. This is valid advice. These practices will indeed help reduce testing flakiness. But the problem…
If you lead a team of developers, SDETs, or QA professionals, you’ve likely had this conversation: should you build test automation yourself, or buy a platform that already does it? Playwright itself is a strong, well-documented framework, and it has become the default choice for browser automation. That reputation is why the do-it-yourself (DIY) route sounds…
