Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add E2E and acceptance tests for settings #9

Open
justlevine opened this issue Nov 27, 2022 · 0 comments
Open

Add E2E and acceptance tests for settings #9

justlevine opened this issue Nov 27, 2022 · 0 comments
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

Comments

@justlevine
Copy link
Member

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

@justlevine justlevine added 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. labels Nov 27, 2022
@justlevine justlevine added this to the v0.1.0 milestone Nov 27, 2022
@justlevine justlevine changed the title Add E2E and acceptance tests Add E2E and acceptance tests for settings Feb 5, 2023
@justlevine justlevine modified the milestones: v0.1.0, v0.2.0 Apr 27, 2023
@justlevine justlevine modified the milestones: v0.2.0, 0.3.0 Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

1 participant