[Bug]: No VR interactive test steps are being executed

[ling1726]

Area

build

Environment

System:
    OS: Linux 5.15 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (32) x64 Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
    Memory: 46.38 GB / 62.77 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
    Yarn: 1.23.34 - /mnt/c/Program Files (x86)/Yarn/bin/yarn
    npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm
  npmPackages:
    eslint: 8.57.0 => 8.57.0
    prettier: 2.8.8 => 2.8.8
    storybook: 7.6.20 => 7.6.20
    typescript: 5.3.3 => 5.3.3

Current Behavior

In the repro PR I made an override to make all Button backgrounds red - the output screenshots have no mention of the other steps that are used in the Button tests

This might be happening happening because storywright is using some internal API that does not seem to exist anymore

Storywright in latest version also uses a different mechanism to fetch steps storywright/src/StoryWright/BrowserExecutor.ts at main · microsoft/storywright

If you try to run locally you get these "wonderful" error messages

Expected Behavior

VR tests should run interactive steps

Reproduction

#33758

Steps to reproduce

1. Clone repro PR
2. Navigate to apps/vr-tests-react-components
3. Run yarn build-storybook
4. Run yarn test-vr
5. See error messages

Suggested severity

Urgent - No workaround and Products/sites are affected

Products/sites affected

No response

Are you willing to submit a PR to fix?

no

Validations

• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[Hotell]

thanks for great report !

This was introduced while migrating to SB 7 (v7.20) https://github.com/microsoft/fluentui/pull/32018/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519 ( unfortunately the build log is no longer available https://uifabric.visualstudio.com/fabricpublic/_build/results?buildId=356077&view=logs&jobId=d896371a-1583-5fe7-db02-473133ed56b2 ) cc @dmytrokirpa

The mistery part is storywright version that was supposed to work only with sb 7 - we need input from VRT team on this ( ping @sunilsurana )

Tried to bump to latest storywright 0.0.34, which wont even run the screenshoting phase:

> nx run vr-tests-react-components:test-vr

$ storywright  --browsers chromium --url dist/storybook --destpath dist/screenshots --waitTimeScreenshot 500 --concurrency 4 --headless true
================ StoryWright params =================
Storybook url = file:////Users/martinhochel/Projects/msft/fluentui/apps/vr-tests-react-components/dist/storybook
Screenshot destination path = dist/screenshots
Browsers = chromium
Headless = true
Concurrency = 4
Cores available on system  = 10
SkipSteps = false
WaitTimeScreenshot = 500
Parse DOM = false
Compress DOM = false
================ Starting story right execution =================
StoryWright processor started @  2025-02-04T10:39:04.524Z
Starting browser test for chromium
** ERROR ** Error: page.evaluate: Error: extract called before initialization
    at StoryStore.extract (file:///Users/martinhochel/Projects/msft/fluentui/apps/vr-tests-react-components/dist/storybook/sb-preview/runtime.js:47:11685)
    at StoryStore.raw (file:///Users/martinhochel/Projects/msft/fluentui/apps/vr-tests-react-components/dist/storybook/sb-preview/runtime.js:47:13415)
    at ClientApi.raw (file:///Users/martinhochel/Projects/msft/fluentui/apps/vr-tests-react-components/dist/storybook/sb-preview/runtime.js:79:408)
    at eval (eval at evaluate (:234:30), <anonymous>:1:28)
    at eval (<anonymous>)
    at UtilityScript.evaluate (<anonymous>:234:30)
    at UtilityScript.<anonymous> (<anonymous>:1:44)
Closing process !!
StoryWright took  0 secs to complete.
StoryWright processor completed @  2025-02-04T10:39:05.021Z

NOTE: fluentai is affected as well @micahgodbolt