test(infield-button): add complete test suites for Phase 6

[Rajdeepc]

Description

Adds the Phase 6 test suite for the 2nd-gen swc-infield-button component. This PR contains only test and story files; the component implementation ships in the Phase 5 PR and must be merged into swc-2105/infield-button before this branch is rebased.

Files added:

• stories/infield-button.stories.ts — Storybook stories with the Quiet story updated to render both default and quiet variants side-by-side for test comparison
• test/infield-button.test.ts — 13 Storybook/Vitest play-function stories covering: defaults, property reflection (size, quiet, disabled, accessible-label), anatomy slots, sizes, quiet variant, states, click suppression, focus delegation, and dev-mode warnings
• test/infield-button.a11y.spec.ts — Playwright ARIA snapshot tests for all 6 stories plus keyboard (Tab does not focus the button) and pointer interaction tests (click fires when enabled, suppressed when disabled)

Motivation and context

Phase 6 of the infield-button 2nd-gen migration. Establishes automated coverage for the full InfieldButton API surface so regressions can be caught during future refactors and dependency bumps.

Depends on: Phase 5 PR must merge into swc-2105/infield-button before this branch can be rebased and run independently.

Related issue(s)

• SWC-2105

Screenshots (if appropriate)

N/A — test-only PR.

Author's checklist

• I have read the CONTRIBUTING and PULL_REQUESTS documents.
• I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
• I have added automated tests to cover my changes.
• I have included a well-written changeset if my change needs to be published.
• I have included updated documentation if my change required it.

Reviewer's checklist

• Includes a Github Issue with appropriate flag or Jira ticket number without a link
• Includes thoughtfully written changeset if changes suggested include patch, minor, or major features
• Automated tests cover all use cases and follow best practices for writing
• Validated on all supported browsers
• All VRTs are approved before the author can update Golden Hash

Manual review test cases

Note: This PR depends on the Phase 5 implementation. Run these steps after Phase 5 merges into swc-2105/infield-button and this branch is rebased on top.

• Vitest play functions pass

  1. From 2nd-gen/packages/swc/, run yarn vitest --project storybook infield-button
  2. Expect all 13 test stories to pass: OverviewTest, PropertyMutationTest, AccessibleLabelTest, AnatomyTest, SizesTest, QuietTest, StatesTest, DisabledBehaviorTest, ClickBehaviorTest, FocusDelegationTest, AccessibilityTest, IconOnlyMissingLabelWarningTest, IconOnlyWithLabelNoWarningTest

• Playwright a11y spec passes

  1. From 2nd-gen/packages/swc/, run yarn playwright test infield-button.a11y.spec.ts
  2. Expect all tests in three groups to pass: ARIA Snapshots (8 tests), Keyboard Interactions (2 tests), Pointer Interactions (2 tests)

• Storybook stories render correctly

  1. Run yarn storybook from 2nd-gen/packages/swc/
  2. Navigate to Infield Button in the sidebar
  3. Verify Overview shows a single medium button with chevron icon
  4. Verify Anatomy shows four icon affordances: Open picker, Clear, Increment, Decrement
  5. Verify Sizes shows all four sizes (s, m, l, xl)
  6. Verify Quiet shows default and quiet variants side-by-side
  7. Verify States shows default, disabled, quiet, and quiet-disabled
  8. Verify Accessibility shows a labeled button ("Open picker")

• No regressions in Action Button

  1. Run yarn vitest --project storybook action-button
  2. Expect all action-button tests to still pass (shared ButtonBase logic)

Device review

• Did it pass in Desktop?
• Did it pass in (emulated) Mobile?
• Did it pass in (emulated) iPad?

Accessibility testing checklist

Required: Complete each applicable item and document your testing steps.

• Keyboard (infield buttons are pointer-only; Tab must not focus them)

  1. Run Storybook and navigate to Infield Button > Overview
  2. Press Tab once
  3. Expect: focus does not land on swc-infield-button — the component is intentionally excluded from the tab order (tabindex="-1" on the inner button, delegatesFocus: false on the shadow root). Keyboard activation is the responsibility of the parent field.

• Screen reader (button role and accessible name must be announced)

  1. Run Storybook and navigate to Infield Button > Accessibility
  2. Enable VoiceOver (macOS) or NVDA (Windows) and move focus to the swc-infield-button element
  3. Expect: screen reader announces "Open picker, button" — role button and the accessible-label value are correctly forwarded via aria-label on the inner <button> element
  4. Navigate to Infield Button > States and locate the disabled button
  5. Expect: screen reader announces the button as dimmed/unavailable — the native disabled attribute on the inner <button> provides the state without requiring aria-disabled

[changeset-bot]

⚠️ No Changeset found

Latest commit: 80b74be

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📚 Branch Preview Links

• Storybook (Gen2, dev mode)
• Storybook (Gen2, prod mode)
• Documentation Site (Gen1)
• Storybook (Gen1)

🔍 Gen1 Visual Regression Test Results

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

• Spectrum | Light | Medium | LTR
• Spectrum | Dark | Large | RTL
• Express | Light | Medium | LTR
• Express | Dark | Large | RTL
• Spectrum-two | Light | Medium | LTR
• Spectrum-two | Dark | Large | RTL
• High Contrast Mode | Medium | LTR

Deployed to Azure Blob Storage: pr-6502

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.