test: optimize basic-usage test

[kagol]

PR

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 deployment workflow to exclude test files from triggering auto-deployment, improving efficiency.

• Tests

  • Enhanced test case for the Fluent Editor demo to verify toolbar functionality and editor content, increasing test coverage and robustness.

[coderabbitai]

Walkthrough

The changes involve modifications to a GitHub Actions workflow file and enhancements to a test case for the Fluent Editor demo. The workflow now excludes specific test files from triggering deployments, refining the conditions for auto-deployment. In the test case, improvements include syntax corrections and expanded content verification for the editor, ensuring it initializes with the expected HTML structure.

Changes

File(s)	Change Summary
.github/workflows/auto-deploy.yml	Added exclusion pattern packages/docs/**/*.spec.ts to prevent triggering on test file changes.
packages/docs/fluent-editor/demos/basic-usage.spec.ts	Enhanced test case with syntax corrections and added verification for editor's inner HTML content.

Poem

In the meadow where bunnies play,
Changes hop in a lively way.
With tests refined and workflows neat,
Our code is now a joyful treat!
Hooray for updates, let’s celebrate,
With happy hearts, we’ll innovate! 🐇✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 42d8ee3 and c087404.

Files selected for processing (2)

• .github/workflows/auto-deploy.yml (1 hunks)
• packages/docs/fluent-editor/demos/basic-usage.spec.ts (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/auto-deploy.yml

Additional comments not posted (3)

packages/docs/fluent-editor/demos/basic-usage.spec.ts (3)

4-4: LGTM!

The addition of the semicolon aligns with standard JavaScript syntax practices.

The code changes are approved.

---

7-8: LGTM!

The addition of the editor locator expands the scope of the test to include verification of the editor's inner HTML content.

The code changes are approved.

---

11-19: LGTM!

The assertion enhances the robustness of the test by not only checking the visibility of the toolbar but also validating the content of the editor.

The code changes are approved.