Test: Add args to mount in react, svelte, and vue renderers

[kasperpeulen]

What I did

This add the ability to mount a specific element in the play function itself, similar as how you do it in testing library.

For React:

storybook/code/renderers/react/template/stories/mount-in-play.stories.tsx

Lines 13 to 20 in 530c0ef

	export const Basic: StoryObj<typeof Button> = {
	args: {
	disabled: true,
	},
	async play({ mount, args }) {
	await mount(<Button {...args} label={'set in play'} />);
	},
	};

For Svelte:

storybook/code/renderers/svelte/template/stories/mount-in-play.stories.ts

Lines 8 to 15 in 530c0ef

	export const Basic: StoryObj = {
	args: {
	disabled: true,
	},
	async play({ mount, args }) {
	await mount(Button, { props: { ...args, label: 'set in play' } });
	},
	};

For Vue3:

storybook/code/renderers/vue3/template/stories_vue3-vite-default-ts/mount-in-play.stories.ts

Lines 13 to 20 in 530c0ef

	export const Basic: StoryObj<typeof Button> = {
	args: {
	disabled: true,
	},
	async play({ mount, args }) {
	await mount(Button, { props: { ...args, label: 'set in play' } });
	},
	};

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This pull request has been released as version 0.0.0-pr-28385-sha-61d0ddf0. Try it out in a new sandbox by running npx storybook@0.0.0-pr-28385-sha-61d0ddf0 sandbox or in an existing project with npx storybook@0.0.0-pr-28385-sha-61d0ddf0 upgrade.

More information

Published version	0.0.0-pr-28385-sha-61d0ddf0
Triggered by	@kasperpeulen
Repository	storybookjs/storybook
Branch	kasper/mount-args
Commit	61d0ddf0
Datetime	Wed Jul 3 07:42:20 UTC 2024 (1719992540)
Workflow run	9773832215

To request a new release of this pull request, mention the @storybookjs/core team.

core team members can create a new canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=28385

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 61d0ddf. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx run-many -t build --parallel=3

---

Sent with 💌 from NxCloud.