Observability Dashboard Interaction Test Suite Generator

Role: Principal UX Engineer specialising in developer tooling and observability interfaces.

Context

• Target dashboard component: {{dashboard_module}}
• Live telemetry stream type: {{telemetry_data_type}}
• Core investigative user flow: {{critical_user_path}}
• Edge and failure states to assert: {{error_state_scenarios}}
• Target testing framework: {{target_framework}}
• Maximum acceptable UI response latency: {{latency_threshold_ms}}

Task

Write a fully executable end-to-end UI interaction testing script in {{target_framework}} that validates developer interactions across {{dashboard_module}}, verifying data density handling, interactive chart filtering, and asynchronous loading states without flakiness.

Method

1. Map the visual hierarchy and DOM selectors for the controls in {{dashboard_module}} handling {{telemetry_data_type}}.
2. Initialize fixture data mocks to simulate high-frequency streaming updates alongside {{error_state_scenarios}}.
3. Implement viewport setup and authenticated state initialization for the target investigative workspace.
4. Script the user interaction step-by-step for {{critical_user_path}}, including zoom, brush filters, and facet toggles.
5. Embed explicit DOM assertions measuring paint cycles against the {{latency_threshold_ms}} boundary.
6. Add visual regression snapshot hooks at each major view state transition.
7. Inject deliberate fault scenarios to confirm resilient error boundary rendering and fallback UI behaviour.
8. Add teardown routines that purge local storage, abort open web sockets, and reset network interceptors.

Constraints

• The script MUST be syntactically valid code ready for direct inclusion in CI pipelines.
• You MUST NOT use arbitrary sleep timers; use deterministic element state and network intercept promises.
• Selectors must rely on accessible roles (getByRole) or data-testid attributes rather than fragile CSS classes.
• Include inline comments explaining the UX rationale behind each assertion.

Output format

1. Test Setup & Configuration block (dependencies, mocks, environment setup).
2. Main Test Suite script (sequential automated test cases with descriptive naming).
3. Assertion & Helper Utilities block (reusable assertions and performance timing wrappers).

Self-review

• Confirm all 6 variables ({{dashboard_module}}, {{telemetry_data_type}}, {{critical_user_path}}, {{error_state_scenarios}}, {{target_framework}}, {{latency_threshold_ms}}) are exercised.
• Verify zero hardcoded time sleeps exist in the code.
• Ensure script covers both nominal paths and {{error_state_scenarios}}.