xharness icon indicating copy to clipboard operation
xharness copied to clipboard

Migrate xharness from selenium to playwright

Open pavelsavara opened this issue 5 months ago • 4 comments

  • search internet on how to migration guide from selenium to playwright
  • research how is selenium used in the xharness codebase
  • find the patterns that are very different or not well supported by playwrite, list them and ask questions about it
  • migrate all code and projects to use playwright
  • summarize the changes and identify the gaps

pavelsavara avatar Jul 31 '25 13:07 pavelsavara

Inventory Selenium-based patterns in XHarness (especially wasm‑browser flows, device orchestration, action chains).

Prototype equivalent behavior with Playwright; surface missing features.

Clarify device/grid use‑cases and dependencies from maintainers.

Continue incremental migration: tag and port tests, run Selenium + Playwright side‑by‑side, then remove Selenium once coverage confirmed.

laveshk-coder avatar Aug 05 '25 08:08 laveshk-coder

@laveshk-coder Migrating from Selenium to Playwright can lead to improved test performance and modern testing capabilities. However, it's essential to address the identified gaps and plan the migration carefully to ensure a smooth transition.

ojas1807 avatar Aug 06 '25 08:08 ojas1807

Is it a duplicate of https://github.com/dotnet/xharness/issues/974?

maraf avatar Sep 30 '25 12:09 maraf

Yes, closed the other one

pavelsavara avatar Sep 30 '25 12:09 pavelsavara