Running playwright tests on CI

[shivaahir158]

Motivate of the pull request

• To address an existing issue. If so, please provide a link to the issue:
• Breaking new feature. If so, please describe details in the description part.

Describe the technical details -

Draft PR to test the e2e runs on the CI, the tests run fine on the local env, shall investigate the CI issue first and will raise the final PR.

What is currently done? (Provide issue link if applicable)

What does this pull request change?

Which part of the code base require a change

• Frontend:
• Backend:
• Library: <Specify the library name, e.g. npm packages>
• Plug-in: <Specify the plugin name, e.g. Webpack, jtest>
• Documentation
• Regression tests: tests/e2e
• Continuous Integration (CI) scripts

Impact of the pull request

• Require a change on Quality of Results (QoR)
• Break backward-compatibility. If so, please list who may be influenced.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.83%. Comparing base (f5dd78a) to head (446c1e3).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #265   +/-   ##
=======================================
  Coverage   68.83%   68.83%           
=======================================
  Files         110      110           
  Lines        9022     9022           
  Branches      402      402           
=======================================
  Hits         6210     6210           
  Misses       2812     2812           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[shivaahir158]

@NadeemYaseen , the e2e tests run in local env all the time, not sure why they have time limit exceeded error on the CI, just FYI.

On local there is currently no way to test e2e tests from latest pull because of no device availability, I am using old fetches where device.xml existed. Selectors are working fine so no issues there.

[ravikiranchollangi]

@NadeemYaseen , the e2e tests run in local env all the time, not sure why they have time limit exceeded error on the CI, just FYI.

On local there is currently no way to test e2e tests from latest pull because of no device availability, I am using old fetches where device.xml existed. Selectors are working fine so no issues there.

@shivaahir158 didn't we agree on manually copying the devices folder ? Why can't we do that to run local e2e tests ?