control-ui-e2e

End-to-end testing for a GUI uses Vitest and Playwright to simulate user interactions while mocking Gateway WebSocket flows and dashboard runs. This approach ensures deterministic testing by isolating the UI from unpredictable backend data.

The best way to capture visual proof of GUI test results is using Playwright during end-to-end test execution. It automatically records screenshots and videos of the simulated user interactions, providing clear evidence of UI behavior.

Yes, you need to mock WebSocket flows for deterministic GUI testing. Mocking Gateway WebSocket flows and dashboard runs isolates the UI from backend variability, ensuring that test outcomes remain consistent and reliable across runs.

To run end-to-end tests for a Control UI project, execute the command `pnpm test:ui:e2e` in your terminal. This initiates the Vitest and Playwright test suite to simulate user interactions and verify UI behavior.

Yes, this testing approach works with Vitest and Playwright together. Vitest manages the test execution while Playwright handles browser automation and user interaction simulation, capturing screenshots and videos for visual evidence.

End-to-end GUI tests fail due to backend data changes because live data introduces variability. By mocking Gateway WebSocket flows and dashboard runs, you isolate the UI to ensure deterministic testing and prevent test flakiness.