ci(e2e): [tree,pager] optimize e2e precise matching logic

[zzcr]

PR

优化流水线e2e测试用例精确匹配逻辑，比如tree只会匹配tree组件，不会匹配chart/tree

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow configuration for E2E testing
  • Modified component parsing logic in test workflow

[coderabbitai]

Walkthrough

The pull request modifies the GitHub workflow configuration for E2E testing, specifically changing the component parsing logic in the .github/workflows/test-e2e-pr.yml file. The key change involves updating the component formatting from .map((c) => "\/${c}\/") to .map((c) => "\/app\/${c}\/"), which now prefixes components with /app/. This adjustment affects how test components are processed during the E2E test workflow, without altering the overall workflow structure or error handling.

Changes

File	Change Summary
.github/workflows/test-e2e-pr.yml	Modified component parsing logic to prefix components with /app/

Suggested labels

e2e-test, enhancement

Suggested reviewers

• kagol

Possibly related PRs

• test(e2e): [dialog-box,bulletin-board,cascader-panel,company,config-provider,country,fullscreen] update e2e test #2329: Updates in E2E tests for various components with similar parsing logic
• ci(e2e): remove the limit on the number of E2E test case components in git-action #2725: Workflow configuration modifications for E2E test component parsing
• test(e2e): [calendar-view]fix calendar-view error e2e test #2737: Calendar view test modifications potentially involving similar component referencing

Poem

🐰 In workflows where tests dance and twirl,
A prefix change makes components unfurl
/app/ now leads the testing parade
With precision that CodeRabbit has made
E2E magic, one small change at a time! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a76d9d1 and 4e8785d.

📒 Files selected for processing (1)

• .github/workflows/test-e2e-pr.yml (1 hunks)

🔇 Additional comments (1)

.github/workflows/test-e2e-pr.yml (1)

32-32: Confirm the new “/app/” prefix will not disrupt existing references.

By switching from "/${c}/" to "/app/${c}/", potential backward compatibility issues might arise if older references depend on the original path. Confirm that any tests, scripts, or code referencing the old path have been updated accordingly.

Below is a script to locate references to these components across the repository to ensure consistency:

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[petercat-assistant]

Walkthrough

This pull request focuses on optimizing the end-to-end (e2e) precise matching logic within the continuous integration (CI) process for the tree component. The changes aim to enhance the accuracy and efficiency of the e2e tests.

Changes

File	Summary
.github/workflows/test-e2e-pr.yml	Adjusted the e2e test configuration to improve precise matching logic, with 1 addition and 1 deletion.