Interactive Testing with Flare and Halogen
summary
A bridge between Flare and Halogen uses a higher-order component that forces a redraw by bumping a slot ID, letting a Flare-generated UI drive a Halogen child and intentionally blow away that child state. It wires Flare, Halogen, halogen-storybook and Sparkle, and demonstrates interactive testing against live server-backed components. A snag appears: reliance on Data.Generic breaks in 0.12 (workarounds needed). The proof of concept works and enables quick playground-driven QA.
AI-written summary · about
chapters (9)
- 0:00Interactive testing with Flare
- 1:18Flare's interactive UI
- 2:47Flare with Halogen
- 3:51Higher-order testing component
- 5:41Flare for UI states
- 7:52Forcing redraws with Flare
- 8:53Sparkle for generic UI
- 10:23Future plans with generics
- 11:27Q&A
related talks
19mBridging the Gap with Gleam & Lustre
31mReinforcing your blocks: A practical guide to UI component testing
17mBeyond Components: Designing Generative UI for MCP Apps
08mLightning Talk
27mREPL/Playground, Let's do it Live!
29mBuilding Live HTML and Omniscient Debuggers in Brackets
34mFantastic Bugs and Where to Find Them
50mThe Babel Fish Data: A Case Study