End-to-end test that tests both the client (UI) and server

Created on 15 July 2024, about 2 months ago
Updated 2 August 2024, about 1 month ago

Overview

Until 📌 Connect client & server, with zero changes to client (UI): rough working endpoints that mimic the UI's mocks Needs review , the client and server side were independently developed.

Since that, 📌 FieldType: Support storing component *trees* instead of *lists* Fixed changed something on the server side without the necessary corresponding change in SdcController::preview(), which resulted in broken previews. 📌 Add component instance edit form to contextual panel RTBC is fixing that, but is not yet introducing end-to-end tests that actually test the integration of the client side with the server side.

\Drupal\Tests\experience_builder\Functional\EndToEndDemoIntegrationTest was added >1 month ago in e [MR Only] Edit any component prop, powered by a new FieldForComponentSuggester service, which will power the JS UI Fixed but tests only the throwaway TwoTerribleTextAreasWidget, but as of 📌 FieldType: Support storing component *trees* instead of *lists* Fixed we're now getting closer to being able to get rid of TwoTerribleTextAreasWidget 👍 (first step: 📌 Evolve component instance edit form to become simpler: generate a Field Widget directly Fixed ).

Proposed resolution

Update tests/src/Cypress/cypress/e2e/xb-general.cy.js to actually test both the client and server, with the client actually talking to the server. Until now, xb-general.js was talking to the mock server!

User interface changes

Zero.

📌 Task
Status

Fixed

Component

Page builder

Created by

🇧🇪Belgium Wim Leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024