Playwright vs Selenium: comparison and what matters for Dynamics 365 testing (2026)
In short: both are open-source, code-based browser automation. For a new web test project, especially for an app with lots of asynchronous loading such as Dynamics 365, Playwright is more convenient: it auto-waits and comes with a test runner, parallelism and the Trace Viewer. Selenium is strong when you already have a working Selenium suite and Grid infrastructure, when your team writes Ruby or Kotlin, or when you need the W3C WebDriver standard. If business testers maintain the tests, neither is ideal: that is where Tricentis Tosca fits.
What is the difference between Playwright and Selenium?
Selenium describes itself as an umbrella project for a range of browser automation tools and libraries, with the W3C-standard WebDriver at its core. Playwright is a web testing framework that drives Chromium, Firefox and WebKit through a single API and bundles a test runner, assertions, isolation and parallelisation. In a nutshell: Selenium is a building block, Playwright is a complete framework.
| Criterion | Playwright | Selenium |
|---|---|---|
| What it is | a web testing and automation framework with a built-in test runner (Playwright Test) | an umbrella project of browser automation tools and libraries (WebDriver, Grid, IDE) |
| Protocol | its own single API for three browser engines | the W3C WebDriver standard; migrating to the bidirectional WebDriver BiDi |
| Browsers | Chromium, Firefox and WebKit engines; Windows, Linux, macOS | Chrome, Edge, Firefox, Safari (and Internet Explorer) |
| Languages | TypeScript/JavaScript, Python, Java, .NET | Java, Python, C#, Ruby, JavaScript, Kotlin |
| Waiting | automatic: before an action it checks that the element is visible, stable, receives events and is enabled | in the test code: implicit or explicit waits (do not mix the two) |
| Parallel runs | built in: several worker processes, suites can be sharded across machines | Selenium Grid: on remote machines, across browser versions and platforms |
| Debugging | Trace Viewer: step-by-step log, network, console and DOM snapshot | the chosen test framework and your own logging |
| Licence | open source, no licence fee | open source, no licence fee |
Why does auto-waiting matter so much?
Selenium’s documentation names the timing race between the browser and the test as one of the primary causes of flaky tests. In Selenium the test code handles this with implicit or explicit waits, and the documentation explicitly warns against mixing them, because it causes unpredictable wait times (an implicit wait of 10 seconds plus an explicit wait of 15 seconds can time out after 20 seconds).
Playwright checks before every action that the element is visible, stable (not animating), receives events (not obscured by another element) and enabled, and only then clicks. For a UI that loads asynchronously, like a Dynamics 365 model-driven app, this means fewer manual waits and fewer flaky tests.
Which one is better for testing Dynamics 365?
Microsoft’s list of regression testing tools for Dynamics 365 includes both Playwright and Selenium, and Microsoft does not recommend one over the other. In practice a few factors decide:
If the suite is maintained by business testers and key users rather than developers, codeless Tricentis Tosca is usually the better choice. The three tools compared: Tricentis Tosca vs Katalon vs Playwright.
When should you stay with Selenium?
- You already have a large, working, maintained Selenium suite: a rewrite rarely pays off within a year.
- You run your own or a hosted Selenium Grid with several browser versions and platforms, and your CI depends on it.
- Your team works in Ruby or Kotlin; Playwright does not officially support them.
- You need standard W3C WebDriver, for example because of a third-party tool or cloud service.
When is it worth moving to Playwright?
- A new project starts, and developers write the tests alongside the code.
- Your existing Selenium tests suffer from many manual waits and frequent flakiness.
- You want built-in parallelism, the Trace Viewer and unified reporting in CI.
- You want UI and API tests in one tool.
We do not rewrite everything at once: new tests are written in Playwright, the most important old ones are migrated by risk, the rest is phased out. The selection logic is described in regression testing.
How we help
We take over and clean up existing Selenium, Playwright or Robot Framework suites, choose the tool that fits your team, build the test suite and wire it into CI. Details: test automation and testing.
Frequently asked questions
Is Playwright better than Selenium?
Not in general; it depends on the job. For a new web test project Playwright is more convenient (auto-waiting, built-in test runner, parallelism, Trace Viewer). For an existing Selenium suite and Grid infrastructure, or for Ruby and Kotlin, Selenium.
Are Playwright and Selenium free?
Yes, both are open source with no licence fee. The cost lies in writing and maintaining the tests and in the execution infrastructure.
Which languages does Playwright support?
TypeScript/JavaScript, Python, Java and .NET. The built-in Playwright Test runner is for Node.js; for Python the pytest plugin, for .NET base classes for MSTest, NUnit or xUnit, for Java e.g. JUnit or TestNG.
Does Playwright test Safari?
Playwright runs the WebKit engine that Safari is built on, also on Windows and Linux. It is not the installed Safari browser; if you need exactly that, Selenium can drive it via SafariDriver.
Can you test Dynamics 365 with Selenium?
Yes, Microsoft lists it among the tools suitable for Dynamics 365 regression testing. However, Microsoft’s Selenium-based EasyRepro library was archived in October 2026, so for new projects Playwright or Tricentis Tosca is the more future-proof choice.
Let’s talk about your project.
Tell us what you are planning and we will get back to you within a few days.
Get in touch