Add E2E and acceptance tests for settings #9
Labels
good first issue 🐣
Issue that doesn't require previous experience with the plugin
scope: tests 🧪
status: confirmed 📍
The issue has been confirmed and reproduced.
type: chore 🧹
No changes to production code.
Milestone
What problem does this address?
Gutenberg likes to break things, but we need to make sure updates don't break any functionality or extensibility.
What is your proposed solution?
We should implement codecept acceptance tests and playright e2e tests to ensure a stable backend.
What alternatives have you considered?
No response
Additional Context
Inspiration: WordPress/gutenberg#38851
The text was updated successfully, but these errors were encountered: