Create Cypress E2E test to ensure component variants work

Created on 14 August 2024, 4 months ago
Updated 9 September 2024, 3 months ago

Overview

This is to ensure that the

As a creator, I want to select a variation of a component. For example, I want to select a dark or light variation of a card component.

(user story (#6) for 🌱 Milestone 0.1.0: Experience Builder Demo Active )

actually works.

Even though Introduce component variants to SDC Active is not yet in core, the assumption is that the variant prop name will be reserved and given special meaning (and that it will have a {type: string, enum: […]} prop shape). Since 📌 Introduce an example set of representative SDC components; transition from "component list" to "component tree" Fixed , 2 SDCs exist in the XB codebase that have such a prop already.

Proposed resolution

Write E2E Cypress test.

User interface changes

None.

📌 Task
Status

Active

Component

Page builder

Created by

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • Novice

    It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.

Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024