action #91884

[spike][timeboxed:18h] Demonstrate how Playwright helps with tricky UI tests

Added by cdywan 3 months ago. Updated 3 months ago.

Concrete Bugs
Target version:
Start date:
Due date:
% Done:


Estimated time:


With #91659 we'll be in a position where we could use Playwright in place of Selenium. Ideally we find some cases where it's clearly better in terms of time spent on writing new tests, fixing unreliable tests or debugging problems.


  • Port t/ui/25-developer_mode.t - see #91232#note-5
  • Consider other tricky tests

Open questions to answer

  • What do we gain from switching to Playwright
  • What do we lose (if anything)
  • Do we see a benefit with tricky tests
  • Do we see a benefit with tests which are stable that are stable already
  • How does debugging compare to Selenium-based tests

Related issues

Related to openQA Project - action #91659: Add Playwright to devel:languages:perlResolved2021-04-232021-05-08

Copied from openQA Project - action #91232: Test t/ui/25-developer_mode.t failed in CIRejected2021-04-152021-04-30


#1 Updated by cdywan 3 months ago

  • Copied from action #91232: Test t/ui/25-developer_mode.t failed in CI added

#2 Updated by cdywan 3 months ago

  • Due date deleted (2021-04-30)
  • Start date deleted (2021-04-15)

#3 Updated by cdywan 3 months ago

  • Related to action #91659: Add Playwright to devel:languages:perl added

#4 Updated by mkittler 3 months ago

Considering that t/ui/25-developer_mode.t is mainly focusing on testing JavaScript code and most of the backend is mocked it would be indeed a good candidate to try out Playwright.

Maybe there's also something to gain in terms of performance so it would also be interesting to compare the execution time of the tests afterwards. Note that our current tests are already taking effort to disable animations of bootstrap and jQuery. Even if Playwright can handle them better we might still want to turn them off for performance reasons.

Also available in: Atom PDF