Add an e2e test for an expanded set of entity form fields

Created on 21 March 2025, 25 days ago

Overview

After πŸ“Œ Media Library dialogs triggered from page data do not have buttons yet Active we have tighter integration between entity forms and entity form fields.
We should expand our test coverage to include more field types and cardinalities

Proposed resolution

Do so

User interface changes

πŸ“Œ Task
Status

Active

Version

0.0

Component

Redux-integrated field widgets

Created by

πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

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

Comments & Activities

  • Issue created by @larowlan
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    We should expand our test coverage to include more field types and cardinalities

    Cardinalities: πŸ“Œ Multiple fields widget should fully work in the contexual form Active .

  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Linked 3 issues @bnjmnm created for widgets.

    Can you and @bnjmnm decide how to approach breaking up this work? πŸ™

  • First commit to issue fork.
  • πŸ‡ΊπŸ‡ΈUnited States bnjmnm Ann Arbor, MI

    I expected way more of the fields added in xb_test_article_fields to either "just work", or not work in a manner that didn't adversely impact the form if they weren't fields that had value changes.

    In the case of language, options-as-buttons (radios), and possibly others, it's clear this isn't the case - they are enough to deserve their own issues IMO. In particular, if the problems impact the ability to test any fields in the form, a separate issue might be good. This issue could then be specific to adding tests for fields that either work already, or are broken in a way that doesn't contaminate the entire form.

    It looks like the branch here and the MR in πŸ“Œ Get Options as buttons in Page Data form working Active are tackling the options-as-buttons issue in different places and I suspect they might be more complementary than conflicting. My preference is to see the work on option buttons here brought over to that issue. BTW I describe a wall I hit in comment 4 β†’ but perhaps the approach here gets around that.

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    I'll hoist my work into your branch πŸ‘οΈ

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    Merged forces with πŸ“Œ Get Options as buttons in Page Data form working Active

Production build 0.71.5 2024