Disable interaction autoplay

[liaoyeguo]

Summary

I add a play function to my story for testing, interactions are auto playing when user visit stories or doc. How can I disable this behavior and trigger interaction manually

Additional information

No response

Create a reproduction

No response

[jonniebigodes]

@liaoyeguo, thanks for reaching out to us with your question. Appreciate it 🙏. What you're asking about is a feature that's been asked often here and also here. However, for part of your question (i.e., docs), you could configure it not to run automatically. See here for documentation on configuring it.

Looking forward to hearing from you.

Have a fantastic day.

Stay safe

[KevinGhadyani-Okta]

None of those links solve the problem in my case. I'm not the OP, but I'm someone who's negatively affected by autoplaying interaction tests.

The docs page doesn't matter because interaction tests are disabled by default for that page. What matters are the stories pages.

1. I design a story to be a certain way, and I don't want interaction tests to be changing that.
2. I only want interaction tests to run if I'm on the Interactions tab, not when doing a11y checks.
3. When doing a11y checks, it specifically breaks where something fades-in. The a11y plugin sees the changing colors and assumes the contrast is wrong but doesn't re-run after the transition is complete. This wouldn't be an issue if the interaction test run on page load, but they do.

It only errors sometimes. That's the biggest problem. Interaction tests running cause a race condition. I'd prefer these interaction tests don't run until I tell them to. Even better if I can set one to autoplay while testing in Storybook's UI rather than having it always running; messing up my stories.

Not a solution

A solution was proposed in one of those links to separate stories with interaction tests into another directory, but a11y is running on all stories. It doesn't exclude some just because they have interactions enabled.

This also requires doubling up on stories just to write interaction tests where I could've just used Jest or Playwright directly instead. What advantage are Interaction tests even bringing to Storybook? If you wanna open a Select dropdown on page load, then rename this to "Storybook pre-load" and don't advertise it as an alternative to running unit tests.

[John0x]

Having the same issue.
The autoplay should exist for non docs as well, preferably on a global level. I don't want the interaction tests to automatically run upon opening the story in storybook.
@jonniebigodes

[kerematam]

Autoplay messes snapshot tests. Please support this feature.