fix: make StoryWright steps work in storybook 7

[Hotell]

Previous Behavior

New Behavior

• removes invalid testWrapper selector for stories that don'd render this wrapper via decorator or programmatically
• this fix adds VR tests that were non-existent for 6+ months so the change is big

action for story owners 👋:

1. Please adjust your VR stories accordingly with appropriate wrappers that can be found here: https://github.com/microsoft/fluentui/blob/master/apps/vr-tests-react-components/src/utilities/TestWrapperDecorator.tsx

• Example of usage: https://github.com/microsoft/fluentui/blob/master/apps/vr-tests-react-components/src/stories/Textarea/Textarea.stories.tsx#L13

2. Fix invalid Steps using executeScripts

• Example:
  . -
  . - see more details within pipeline logs https://uifabric.visualstudio.com/fabricpublic/_build/results?buildId=370237&view=logs&j=d896371a-1583-5fe7-db02-473133ed56b2&t=e160194d-9f9f-5756-8519-377c2b9059d6

• disables storybook storyStoreV7 temporarily for vr apps ( which shouldn't be possible but it works)
  • this makes StoryWright Steps processing work again
  • this will be rolled back once new StoryWright will be released feat: support storybook storyStoreV7 storywright#69

Related Issue(s)

• Fixes [Bug]: No VR interactive test steps are being executed #33759

[github-actions]

📊 Bundle size report

✅ No changes found

[github-actions]

Pull request demo site: URL

[dmytrokirpa]

Hey @Hotell, great findings! I have a suggestion - rather than adjusting steps to remove the .testWrapper selector, why not add the TestWrapper decorator to the stories that don't have it? This will make future TestWrapper unification easier #31994.

What do you think?

[Hotell]

Hey @Hotell, great findings! I have a suggestion - rather than adjusting steps to remove the .testWrapper selector, why not add the TestWrapper decorator to the stories that don't have it? This will make future TestWrapper unification easier #31994.

What do you think?

yeah that was my original intent, but I don't have context to do that with expected outcome -> thus the call to action to test authors within PR description

to add on this, this appears to be bigger issues in general right

• no generators to create VR test/no docs = inconsistency everywhere
• the tool wont fail if invalid cropTo to is provided = needs feature work on StoryWright or we can build lint rules
• high probability to migrate away from storywright = big effort

[Hotell]

@chrisdholt can we get approval from your crew please ?

[marchbox]

approving for vr-tests-web-components