[Bug]: Interactions - When step function is not awaited, it gets lost in debugger

Description

play: async ({ canvasElement, step }) => {
    const canvas = within(canvasElement);
    const loginButton = await canvas.getByRole('button', {
      name: /Log in/i,
    });
    await userEvent.click(loginButton);
    // This should be awaited. If it's not, the panel bugs out.
    step('click', async () => {
      await userEvent.click(loginButton);
    })
}

Contributor guide

Tech stack

typescriptreact

Domain

frontendtesting

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

async/awaitStorybook interactions addon

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60

Research direction

The issue is reproducible via the provided StackBlitz link (src/stories/Page.stories.ts). Investigate how the 'step' function is processed in the interactions addon; specifically, why an unawaited step causes the debugger panel to malfunction. Look into the addon's step implementation and the async execution flow. The fix likely involves either enforcing awaited steps or handling the unawaited case gracefully.