PB-2064: fix cesium cypress

[sommerfe]

Test link

[cypress]

web-mapviewer    Run #6247

Run Properties:   Failed #6247  •  beb5368e65: PB-2064: fix cypress startup error

Project	web-mapviewer
Branch Review	fix-pb-2064-cesium-cypress
Run status	Failed #6247
Run duration	20m 45s
Commit	beb5368e65: PB-2064: fix cypress startup error
Committer	Felix Sommer
View all properties for this run ↗︎

---

Test results
Failures	65
Flaky	0
Pending	21
Skipped	2
Passing	180
View all changes introduced in this branch ↗︎

---

Tests for review

  3d/layers.cy.ts • 10 failed tests • e2e/chrome/mobile

View Output

Test		Artifacts
Test of layer handling in 3D > add layer from search bar		Test Replay Screenshots
Test of layer handling in 3D > sets the opacity to the value defined in the layers URL param or menu UI		Test Replay Screenshots
Test of layer handling in 3D > sets the timestamp of a layer when specified in the layers URL param		Test Replay Screenshots
Test of layer handling in 3D > reorders visible layers when corresponding buttons are pressed		Test Replay Screenshots
Test of layer handling in 3D > add GeoJson layer with opacity from URL param		Test Replay Screenshots
Test of layer handling in 3D > removes a layer from the visible layers when the "remove" button is pressed		Test Replay Screenshots
Test of layer handling in 3D > uses the 3D configuration of a layer if one exists		Test Replay Screenshots
Test of layer handling in 3D > add KML layer from drawing		Test Replay Screenshots
Test of layer handling in 3D > Verify layer features in 2D and 3D		Test Replay Screenshots
Test of layer handling in 3D > Verify a layer with EPSG:4326(WEBMERCATOR) bounding box in 2D and 3D		Test Replay Screenshots

  drawing.cy.ts • 14 failed tests • e2e/chrome/mobile

View Output

Test		Artifacts
Drawing module tests > Drawing mode/tools > can create marker/icons and edit them		Test Replay Screenshots
Drawing module tests > Drawing mode/tools > can create annotation/text and edit them		Test Replay Screenshots
Drawing module tests > Drawing mode/tools > can create line / measurement, extend it, and delete the last node by right click / button, and make a polygon		Test Replay Screenshots
Drawing module tests > Drawing mode/tools > can create line/polygons and edit them		Test Replay Screenshots
Drawing module tests > KML management > deletes the drawing when confirming the delete modal		Test Replay Screenshots
Drawing module tests > KML management > manages the KML layer in the layer list / URL params correctly		Test Replay Screenshots
Drawing module tests > KML management > keeps the KML after a page reload, and creates a copy if it is then edited		Test Replay Screenshots
Drawing module tests > KML management > manages the KML layer correctly if it comes attached with an adminId at startup		Test Replay Screenshots
Drawing module tests > KML management > manages the KML layer correctly if it comes attached with an adminId at startup from a legacy URL		Test Replay Screenshots
Drawing module tests > KML management > receives an empty KML and can use drawing mode		Test Replay Screenshots
The first 10 failed tests are shown, see all 14 tests in Cypress Cloud.

  importToolMaps.cy.ts • 1 failed test • e2e/chrome/mobile

View Output

Test		Artifacts
The Import Maps Tool > Import external WMTS layers		Test Replay Screenshots

  feedback.cy.ts • 1 failed test • e2e/chrome/mobile

View Output

Test		Artifacts
Testing the feedback form > test the report problem form UI, validations, and it backend interaction		Test Replay Screenshots

  infobox.cy.ts • 2 failed tests • e2e/chrome/mobile

View Output

Test		Artifacts
The infobox > transition from 2D to 3D (and back to 2D) > keeps the selected features when going 3D		Test Replay Screenshots
The infobox > transition from 2D to 3D (and back to 2D) > keeps the selected features when going back to 2D		Test Replay Screenshots

The first 5 failed specs are shown, see all 20 specs in Cypress Cloud.

[sommerfe]

@pakb @ltkum I saw that the 3D tests are failing with an error that the webgl still does not work, this might be a problem that the CI runs the tests with Chrome 142 but 143 is needed. Is this configurable somewhere?