test: add playwright

[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

• New Features

  • Introduced a GitHub Actions workflow for automated Playwright testing.
  • Added testing and reporting scripts to the project for enhanced functionality.
  • Implemented a new Playwright test to verify the toolbar in the Fluent Editor documentation.

• Bug Fixes

  • Updated dependencies in the documentation package to improve testing capabilities.

• Chores

  • Enhanced the .gitignore file to exclude unnecessary Playwright-generated files.
  • Established a new Playwright configuration for streamlined test execution.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces a GitHub Actions workflow for running Playwright tests, enhances the .gitignore file to exclude unnecessary files, and adds new scripts to package.json for testing and reporting. It also includes a new Playwright test file for the Fluent Editor documentation and a configuration file for Playwright settings. The changes aim to streamline testing processes and improve project organization.

Changes

File(s)	Change Summary
.github/workflows/playwright.yml	New GitHub Actions workflow for running Playwright tests, triggered on pushes and pull requests.
.gitignore	Added entries to ignore playwright-report, blob-report, and playwright/.cache directories.
package.json, packages/docs/package.json	Added scripts for testing and reporting; updated dependencies and fixed JSON syntax.
packages/docs/fluent-editor/demos/basic-usage.spec.ts	New Playwright test file for verifying the toolbar in documentation.
packages/docs/playwright.config.ts	New configuration file for Playwright, specifying test settings and options.

Poem

In the garden of code, we hop and play,
With tests and reports brightening our day.
A workflow to guide us, like stars in the night,
With each little change, our future looks bright!
So gather 'round, friends, let’s dance and delight,
For our project now shines, oh what a sight! 🐇✨

---

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.