Automate Gutenberg block editor testing with Playwright.
npx skills add https://github.com/adityaarsharma/orbit --skill orbit-block-edit-test
Please help me install this Agent Skill. Skill: orbit-block-edit-test Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-block-edit-test Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-block-edit-test
This Skill automates the testing of the editor-time user experience for Gutenberg blocks, ensuring a seamless and bug-free editing process.
Run the orbit-block-edit-test skill to execute editor-time tests for a block in your plugin by running the following command:
PLUGIN_SLUG=my-plugin npx playwright test --project=block-edit
High-intent search queries and answers about installing and using this skill.
Automating Gutenberg block editor experience testing with Playwright involves running targeted tests for block insertion, attribute editing, toolbar functionality, transformations, undo/redo, and inner block rendering. You execute these tests using the Playwright test runner configured for the block edit project.
Automated testing validates block insertion, attribute editing, toolbar functionality, transformations, undo/redo sequences, and inner block rendering. This ensures custom InspectorControls and core editor features work seamlessly without manual verification.
Yes, Playwright is a required dependency to execute automated editor-time tests for Gutenberg blocks. You also need the appropriate plugin configuration set up to run the specific block edit test project.
Run editor-time tests for a specific Gutenberg block plugin by executing the Playwright test command with the block edit project configuration. Set your plugin slug environment variable and run the Playwright test runner targeting the block edit project.
Yes, you can test custom InspectorControls added to Gutenberg blocks. The automated tests validate the editor experience to ensure that custom controls and all block attributes function as expected during the editing process.
The best way to verify undo/redo functionality in Gutenberg blocks is through automated editor-time testing. This approach programmatically triggers undo and redo actions to validate that block states and attributes revert and restore correctly.
adityaarsharmaAudit Gutenberg block plugins for WordPress standards compliance.
ABLER-Digital-ServicesExecute Playwright end-to-end tests and inspect failure artifacts.
gajjalaashok75-UIBuilds Playwright-based end-to-end browser test suites for CI/CD pipelines.
williamzujkowskiAutomate end-to-end web app testing with Playwright or Cypress in CI/CD pipelines.