Browsers need not apply, UI testing with Lustre and Gleam
summary
Luster on Gleam separates model, update and view so tests hit the right thing: unit-test the update function for business logic, run view assertions and a query DSL for presentation, take textual snapshots with birdie for content diffs, and use a Storybook-like Fable + a browser only for design checks. A simulate module folds messages to emulate journeys and avoids spinning real browsers (no more half-hour CI times); Gleun runs tests, RSVP handles HTTP.
AI-written summary · about
chapters (13)
- 0:00UI testing with Lustre and Gleam
- 1:07Hate traditional UI tests
- 3:38Four UI test categories
- 4:41React component limits
- 6:26Lustre/Gleam component separation
- 9:39Unit tests for business logic
- 11:05Presentation logic in Lustre
- 13:36User journeys without browsers
- 14:40Text snapshots for content
- 15:23Design tests with components
- 16:25Tailor test strategies
- 16:47Lustre’s testing ecosystem
- 17:10Q&A
