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

Testing: Fix and re-enable editor UI tests #11897

Closed
rachelmcr opened this issue May 12, 2020 · 1 comment · Fixed by #12111
Closed

Testing: Fix and re-enable editor UI tests #11897

rachelmcr opened this issue May 12, 2020 · 1 comment · Fixed by #12111
Assignees

Comments

@rachelmcr
Copy link
Member

The Editor UI tests were disabled in #11530 due to failures discussed here:

the problem seems to be that the tests expect Aztec (not Gutenberg) but for some reason sometimes Gutenberg is getting enabled.

We should fix those tests and enable both those Aztec editor tests and the Block editor tests.

@mkevins
Copy link
Contributor

mkevins commented Jun 5, 2020

I've drafted a PR to allow setting the editor explicitly in the different editor UI tests. It is currently only in draft since the startup time issue for Gutenberg has not been solved yet, but we should have the option now to temporarily enable Aztec only if that becomes a blocker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants