Create an E2E test that starts with an empty canvas

Created on 13 September 2024, 6 days ago

Updated 16 September 2024, 3 days ago

Overview

In 📌 Update default config to make a fresh install result in an XB UI with an empty canvas Fixed we made it so that anybody you creates an article an then uses XB at xb/node/1 will start with an empty canvas

To limit the scope of the issue we used the same defaults that we had before 3472299 in XBTestSetup to create the node that E2E tests use. Therefore the E2E tests all start with a pre-filled canvas

Since we already found and solved a problem in #3472299-20: Update default config to make a fresh install result in an XB UI with an empty canvas → (linked to explanation) that only happened on when the canvas was empty, is possible we could introduce new problems that only show up canvas is empty and we have no test coverage for this situation

Proposed resolution

Create at least 1 E2E test that starts with an empty canvas and then places 1 component on the canvas.

User interface changes

📌 Task

Status

Active

Component

Page builder

Created by

🇺🇸United States tedbow Ithaca, NY, USA

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @tedbow
Comment 6 days ago →
🇺🇸United States tedbow Ithaca, NY, USA
Will the front end folks determine the priority. Though the problem with an empty canvas discovered in #3472299-20: Update default config to make a fresh install result in an XB UI with an empty canvas → was actually a backend issue.
Comment 3 days ago →
🇧🇪Belgium Wim Leers Ghent 🇧🇪🇪🇺
Comment 3 days ago →
🇧🇪Belgium Wim Leers Ghent 🇧🇪🇪🇺
Bumping to because without it, our E2E tests do not cover the full spectrum of typical use.

Plus, it already slowed velocity down once before — even though the root cause was a simple back-end fix.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024