Using the end to end tests as the flow is a neat idea. They already list the steps in order and they break when the UI changes, so a script built from them is less likely to drift from the real labels. Fixtures for screen content makes sense too, since nobody wants a demo full of "test user 3". How do you handle flows that only exist behind a feature flag?
Good question. I treat the flag as part of the fixture. The demo seed turns the flag on explicitly, so the end to end test for that flow and the demo read the same state, and nothing depends on whatever the flag service says that day. Two rules I'd add. If the feature isn't released to everyone yet, the video either says so on screen or waits. And the script never pulls steps from a test that only runs with the flag off. Otherwise you end up demoing a screen most users can't see yet.
StackShortlist
Proof Over Promises.
Using the end to end tests as the flow is a neat idea. They already list the steps in order and they break when the UI changes, so a script built from them is less likely to drift from the real labels. Fixtures for screen content makes sense too, since nobody wants a demo full of "test user 3". How do you handle flows that only exist behind a feature flag?