CI: new `cypress E2E debug` job

Created on 17 December 2024, 5 days ago

Overview

…
Then I remembered something @jessebaker said on Slack: maybe it's a dev vs. production build issue. That's it! 💫

I was able to confirm that testing the app after npm run build (and reverting my fix) doesn't present the issue! This is because there are no subsequent re-renders occurring for the InputBehaviors component in the production build. They happen in development mode thanks to our use of <StrictMode>, which helps us catch bugs by double rendering in development. That's exactly what happened here. The fix is still valid and necessary.

…

AFAICT we could've caught this automatically.

Proposed resolution

Add new cypress E2E debug CI job that's identical to the cypress E2E job, with two exceptions:

it uses the debug build (npm run drupaldev, not npm run build)
it does not run always, only when the UI is changed (and of course for the 0.x branch + manually)

User interface changes

None.

📌 Task

Status

Active

Version

0.0

Component

Page builder

Created by

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.

DX (Developer Experience)
Enhances developer experience.

Merge Requests

!484CI: new `cypress E2E debug` job
Open
🇧🇪Belgium wim leers
updated 5 days ago

Comments & Activities

Issue created by @wim leers
Merge request !484Introduce `UI debug` and `cypress E2E debug` CI jobs. → (Open) created by wim leers
Comment 5 days ago →
🇳🇱Netherlands balintbrews Amsterdam, NL
wim leers → credited balintbrews → .
Comment 5 days ago →
🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Comment 5 days ago →

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

$ npm run drupaldev
> vite-template-redux@0.0.0 drupaldev
> VITE_DRUPAL=true vite
  VITE v5.4.11  ready in 289 ms
  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose

… oops, npm run drupaldev is long-running 😅

I'll let @balintbrews adjust that! 🤓

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024