🐛e2e testing: replacement of sleepers using Playwright (preparation for upscaling of ext clusters)

[sanderegg]

What do these changes do?

This PR leverages Playwright and replaces the puppeteer-based sleepers e2e test by:

• not relying on any template, but by creating a new project from a service
• creating 12 sleepers
• running them both in billable and non-billable products works

Bonuses:

• refactored some fixtures (auto-stop started pipeline on exit, auto-delete created project on exit)
• uses the GUI to logout
• some fail fast with error added (wrong password or others that do not need to wait 30 seconds to fail)
• make use of socket.io messages to wait for events
• can auto-register on deploys that allow it
• uses pydantic 2.x

NOTE: The video was generated using Playwright --video=on flag!

8e7e530c20a3bf0e8bc7d91e73f4a0a6.webm

Related issue/s

How to test

against any deployment

make devenv
source .venv/bin/activate
cd tests/e2e-playwright
make install-dev
# if non billable with existing user
pytest test/sleepers.py --product-url=https://osparc.io --user-name=USERNAME --password=PASSWORD
# if billable with existing user
pytest test/sleepers.py --product-url=https://osparc.io --user-name=USERNAME --password=PASSWORD --product-billable
# autoregister works, non-billable
pytest test/sleepers.py --product-url=http://127.0.0.1:9081 --autoregister
# autoregister works, billable
pytest test/sleepers.py --product-url=http://127.0.0.1:9081 --autoregister --product-billable

against local deployment only

make devenv
source .venv/bin/activate
make build up-prod
cd tests/e2e-playwright
make install-dev
make test-sleepers
# or headed
make test-sleepers-dev

Dev Checklist

• No ENV changes or I properly updated ENV (read the instruction)

DevOps Checklist

[codecov]

Codecov Report

Merging #5167 (6f9aa3c) into master (bda5bc6) will increase coverage by 0.1%.
Report is 1 commits behind head on master.
The diff coverage is n/a.

❗ Current head 6f9aa3c differs from pull request most recent head f1e5fcc. Consider uploading reports for the commit f1e5fcc to get more accurate results

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #5167     +/-   ##
========================================
+ Coverage    87.2%   87.4%   +0.1%     
========================================
  Files        1282    1282             
  Lines       52651   52651             
  Branches     1141    1141             
========================================
+ Hits        45946   46022     +76     
+ Misses       6460    6384     -76     
  Partials      245     245             

Flag	Coverage Δ
integrationtests	64.9% <ø> (+1.3%)	⬆️
unittests	85.2% <ø> (+<0.1%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 10 files with indirect coverage changes

[bisgaard-itis]

Super cool!
Looks good to me. I added a few suggestions and questions for my own understanding.
Thanks!

[GitHK]

Looking very nice. Thanks for the effort!

[GitHK]

@sanderegg An additional question
I see in the above video that not all the sleepers show any outputs. Is that intended?

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud