test(SelectPanel): update tests to account for more of API

[joshblack]

As we're working more on the v1 of SelectPanel, I wanted to add some additional tests to the test suite.

This is not complete coverage but figured I'd add what I could this week and revisit another time for what was missed

Changelog

New

Changed

• Update tests for Select Panel

Removed

Rollout strategy

• None; if selected, include a brief description as to why

This is a change that adds tests to Select Panel

[changeset-bot]

⚠️ No Changeset found

Latest commit: 79e8cc5

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]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	90.97 KB (0%)
packages/react/dist/browser.umd.js	91.25 KB (0%)

[joshblack]

bump @siddharthkp when you get a sec 👀

[broccolinisoup]

Thanks so much for adding these tests 🙏🏻

Question: I assume these are the current behaviours since all tests pass. Is there any behaviour that we know for sure that it will change after we implement the accessibility remediations? If there are some, we might want to add comments on them to help us refactor the tests later.

Let me know if I am not making sense!

[joshblack]

@broccolinisoup my understanding since we're keeping the combobox-related functionality is that it should mostly be the same behavior, if I remember right 👀

[broccolinisoup]

@broccolinisoup my understanding since we're keeping the combobox-related functionality is that it should mostly be the same behavior, if I remember right 👀

Oh this is great! Thanks for sharing that.