Menu

1 / 2

We recorded a 14-chapter video series. It turned out to be our best end-to-end test.

DEV Community: java·Miguel Pérez Colom·about 13 hours ago
#13BOfSNS
#devtojava#devto#dev#screen#guest
Reading 0:00
15s threshold

We set one rule for the EventConductor video series — nothing on screen may be drawn by hand — and that rule turned every chapter into a test of the real product. Recording 14 short chapters surfaced more than a dozen real defects, including one that wasn't a bug in the code at all, but in the story our examples told.

The rule: nothing drawn by hand

EventConductor is an open-source engine for business processes in Java/Spring: you declare the steps in YAML, and it handles retries, compensation, waiting for people, timers and operations. It does a lot, and a single promo video can't show it. So we made EventConductor in N minutes : 14 chapters of 2–4 minutes, one aspect each.

The series had three production rules:

Every screen is the product running. The admin console is recorded with Playwright; terminals show real commands with their real output; the IDE is real VS Code with the published extension.

Every snippet on screen compiles and is the code that produces the screen next to it.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.