Add component tests for create/edit custom elements
Categories
(Calendar :: Calendar Frontend, task)
Tracking
(Not tracked)
People
(Reporter: arschmitz, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [calendar-ui-create-edit])
Summary:
Add shared create/edit custom-element test fixtures and cross-element contract coverage.
Links:
-
Zeplin main create/edit: https://app.zeplin.io/project/66dd0f2b2fe8f1b63cda36f1/screen/6a0f2f285393a283202254bc
-
Zeplin repeat subview: https://app.zeplin.io/project/66dd0f2b2fe8f1b63cda36f1/screen/6a10620cf1139fa048b0868f
-
Zeplin guests subview: https://app.zeplin.io/project/66dd0f2b2fe8f1b63cda36f1/screen/6a106fea17e89a34ddffd33f
-
SOW: Testing plan: https://docs.google.com/document/d/1ZVLX8VjxaYsSBuywLyFsXf27Q-Pf55g8QxT8G9z0eZ4/edit?tab=t.0#heading=h.vj4d1m6tkwpz
-
Planning: Redux - Pure state tests
Acceptance criteria: -
Shared fixtures instantiate fresh dialog sessions in create mode and attribute-driven edit mode without production launch routing.
-
Fixture helpers provide isolated Redux state, serializable source snapshots, source-loader adapter stubs, draft initialization, subview entry, and axe execution for field-owned focused tests.
-
Source-loader stubs exercise the real attribute-to-session contract, including plain snapshot mapping, request IDs, route replacement, stale-result rejection, and show readiness. They do not place raw
calIEventor calendar objects in fixture Redux state. -
Fixtures exercise
storeObserver-driven initial render and updates, including reuse across dialog close/open without disposing an element that remains in use. -
Cross-element contract coverage is limited to element registration, attribute-to-loader handoff, session/draft initialization, generic row/subview navigation, Back-focus contract, and readiness-before-show.
-
Helpers provide deterministic cleanup of fixture stores, source caches, DOM elements, and async work so one test cannot affect another session.
-
Field controls, semantic mapping, field validation, persistence, visual variants, and integrated user journeys remain tested by their owning stories.
-
Add fixture and contract tests for create/edit setup, isolated state, loader handoff, stale-route handling, observer-driven rendering, generic navigation, cleanup, and axe coverage where supported.
Out of scope:
- Production launch-routing tests, field-specific behavior, persistence or calendar transactions, exhaustive visual validation, and end-to-end create/edit journeys.
Description
•