-
Notifications
You must be signed in to change notification settings - Fork 384
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
Improve CI configuration #2810
Improve CI configuration #2810
Conversation
Why is the demo plugin needed here? |
@westonruter It basically acts as documentation to show how adding plugins for E2E tests works. Alternatively we can just wait until we actually need some of these plugins when adding the first bunch of tests. |
I'm confused though: these tests are for the AMP plugin. Why would adding plugins need to be tested in this project? |
Unless the intention is to test that AMP validation errors are getting properly attributed? |
@westonruter It's not about testing plugins. This change allows for adding some utility plugins that can be activated during E2E tests. For example, such a plugin could create a custom post type and the accompanying E2E test would verify that block validation errors are shown for this custom post type too. |
Related: #2795.