chore(dev): Add data-test props for integration tests

[domphan-wandb]

Description

WB-23722

This PR adds data-test props that'll be used for integration tests

Testing

How was this PR tested?

Summary by CodeRabbit

• Tests
  • Improved automated testing support by adding unique identifiers to key interface elements, ensuring easier element selection during quality assurance without affecting the end-user experience.

[circle-job-mirror]

Preview this PR with FeatureBee: https://beta.wandb.ai/?betaVersion=98c12890afad80971c3aafe066a76162f0bfcd84

[coderabbitai]

Walkthrough

This pull request adds testing attributes to two components. The ControlFilter.tsx file now includes a data-test attribute on a <div> element, and the PanelTable.tsx file has been updated with a similar attribute on a <span> element for pagination. These changes introduce identifiers that can be used for automated testing without modifying any core logic or functionality.

Changes

Files	Change Summary
weave-js/src/components/Panel2/ControlFilter.tsx weave-js/src/components/Panel2/PanelTable/PanelTable.tsx	Added a data-test attribute to target elements: "filter-expr" on a <div> in ControlFilter and "pagination-info" on a <span> in PanelTable.

Suggested reviewers

• jtulk
• jamie-rasmussen

Poem

I’m a little rabbit on a coding spree,
Adding test tags for all to see.
"filter-expr" hops in with style,
"pagination-info" joins the mile.
Together we test with bunny delight,
Skipping bugs from morning to night!

---

📜 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 5b6883e and 7cccba0.

📒 Files selected for processing (2)

• weave-js/src/components/Panel2/ControlFilter.tsx (1 hunks)
• weave-js/src/components/Panel2/PanelTable/PanelTable.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• weave-js/src/components/Panel2/ControlFilter.tsx
• weave-js/src/components/Panel2/PanelTable/PanelTable.tsx

⏰ Context from checks skipped due to timeout of 90000ms (90)

• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)
• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)
• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)
• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)
• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)
• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)
• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)
• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)
• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)
• GitHub Check: WeaveJS Lint and Compile
• GitHub Check: Trace nox tests (3, 13, trace)
• GitHub Check: Trace nox tests (3, 12, scorers)
• GitHub Check: Trace nox tests (3, 12, trace)
• GitHub Check: Trace nox tests (3, 11, scorers)
• GitHub Check: Trace nox tests (3, 11, trace)
• GitHub Check: Trace nox tests (3, 10, scorers)
• GitHub Check: Trace nox tests (3, 10, trace)
• GitHub Check: Trace nox tests (3, 9, scorers)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
• @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.