- Issue created by @wim leers
- Assigned to gauravvvv
- Issue was unassigned.
- Assigned to wim leers
- Status changed to Needs work
4 months ago 3:10pm 3 September 2024 - 🇬🇧United Kingdom jessebaker
@Wim Leers Would it be safe to change the title of this ticket to "Create Cypress E2E test to ensure that /enum fields in the components prop form work" or is there some unique aspect of "variants" that specifically needs to be tested here?
- Issue was unassigned.
- Status changed to Active
4 months ago 4:11pm 3 September 2024 - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
No, nothing unique about that … yet.
"component variants" are a high-level concept, that will be prominently present in the XB UX, and therefore merit their own explicit test coverage. For now, there's nothing differentiated about their UX, but that could very well change.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
With 🐛 Prop select lists don't affect the component Fixed in, I'm now 100% confident this works.
So writing a passing tests should be easy.
- 🇳🇱Netherlands balintbrews Amsterdam, NL
Tests were recently written to cover enum fields as part of 📌 Redux Sync all single-value types in the SDC test all props form Fixed . With that covering the basics, let's postpone this issue until we have specific UX created for component variants.