🎨 removing jupyterlab flaky part of the e2e test

[matusdrobuliak66]

What do these changes do?

• 🎨 I have removed the flaky part of the jupyterlab test connected to jupyter math service while I manage to create a more stable test. (This change is already used in the e2e tests from my personal branch and I can confirm that the not stable part of the test was removed.)

Related issue/s

How to test

Dev Checklist

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

DevOps Checklist

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.0%. Comparing base (a735871) to head (6e63c63).

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #5371      +/-   ##
=========================================
- Coverage    87.5%   65.0%   -22.5%     
=========================================
  Files        1317     539     -778     
  Lines       54175   27178   -26997     
  Branches     1176     203     -973     
=========================================
- Hits        47407   17690   -29717     
- Misses       6518    9437    +2919     
+ Partials      250      51     -199     

Flag	Coverage Δ
integrationtests	65.0% <ø> (-0.1%)	⬇️
unittests	?

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

see 1110 files with indirect coverage changes

[GitHK]

OK I guess

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

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

See analysis details on SonarCloud

[elisabettai]

Thanks.

I'm curious to see why jupyter-math specifically is flaky (doesn't the jupyterlab UI show up correctly?). I'll check if I can spot some meaningful playwrite tests.

[matusdrobuliak66]

Thanks.

I'm curious to see why jupyter-math specifically is flaky (doesn't the jupyterlab UI show up correctly?). I'll check if I can spot some meaningful playwrite tests.

no no the UI shows correctly. The test is written not in a stable way meaning that sometimes when he is looking for the jupyter math button he doesn't see it

page.frame_locator(".qx-main-dark").get_by_text("python (maths)").first.click()

this line of code needs to be written differently, but I do not know yet how.