test(app): Add data-test to ToggleButtonGroup buttons

[ericakdiaz]

Description

Adds a data-test to each individual button to make it easier to click in Playwright tests.

Testing

How was this PR tested?

See https://github.com/wandb/core/pull/27603

Summary by CodeRabbit

• Tests
  • Enhanced testing support for the toggle buttons by adding dynamic identifiers that streamline component validation during test runs.

[coderabbitai]

Walkthrough

A new data-test attribute is added to the Button component within the ToggleButtonGroup component. This attribute is set dynamically to toggle-button-${optionValue} to improve testability. There are no changes to the component's core logic, structure, or public interface.

Changes

File	Change Summary
weave-js/.../ToggleButtonGroup.tsx	Introduced a new data-test attribute with a dynamic value on the Button component for easier test identification.

Poem

I'm a bunny with a keen delight,
Hoping my tests will shine so bright.
Added a tag with a twist so neat,
Making each toggle easy to greet.
Testing paths made light and free—
A joyful leap in code for me!
🐰✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 59744a6 and c412196.

📒 Files selected for processing (1)

• weave-js/src/components/ToggleButtonGroup.tsx (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

`**/*.{js,jsx,ts,tsx}`: Focus on architectural and logical i...

**/*.{js,jsx,ts,tsx}: Focus on architectural and logical issues rather than style (assuming ESLint is in place).
Flag potential memory leaks and performance bottlenecks.
Check for proper error handling and async/await usage.
Avoid strict enforcement of try/catch blocks - accept Promise chains, early returns, and other clear error handling patterns. These are acceptable as long as they maintain clarity and predictability.
Ensure proper type usage in TypeScript files.
Look for security vulnerabilities in data handling.
Don't comment on formatting if prettier is configured.
Verify proper React hooks usage and component lifecycle.
Check for proper state management patterns.

• weave-js/src/components/ToggleButtonGroup.tsx

🔇 Additional comments (1)

weave-js/src/components/ToggleButtonGroup.tsx (1)

73-73: LGTM! Well-structured test attribute.

The added data-test attribute follows a clear, predictable pattern that will make the buttons easily identifiable in Playwright tests. The implementation is clean and has no performance impact.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[circle-job-mirror]

Preview this PR with FeatureBee: https://beta.wandb.ai/?betaVersion=2c7384fa2a726951a0fc3e63ae591ab1df14aac6