You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UI for the context menu can be improved in a few key areas. We already have a design ready that we can implement.
For reference, this is the current UI:
Here are the designs we want to implement instead (as of 2024-11-18):
The core differences from an implementation perspective is:
The current design has a split between "Story statuses" (top) and "any menu item content" (bottom), but the new design puts all content into a single "slot". So addon-test has a slot, and Visual Tests have a slot.
All (sub)test types (Component tests, a11y, coverage, etc.) must always be shown, even when they haven't run yet. This conflicts directly with the Story Status API where stories only have statuses when something has happened (failed/success/running). in combination with 1, we can't use Story Statuses for content here, addon-test has to internally figure out what content and statuses to show instead. So we'll only use the Story Status API for the dots in the sidebar, not the content in the menu.
The new designs have an "edit mode" that essentially functions the same as the Testing Module UI, allowing you to disable/enable any sub test types.
For that reason, we've identified the following tasks:
The content you are editing has changed. Please copy your edits and refresh the page.
The UI for the context menu can be improved in a few key areas. We already have a design ready that we can implement.
For reference, this is the current UI:
Here are the designs we want to implement instead (as of 2024-11-18):
The core differences from an implementation perspective is:
For that reason, we've identified the following tasks:
Tasks
The text was updated successfully, but these errors were encountered: