-
Notifications
You must be signed in to change notification settings - Fork 87
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
Implement e2e (end to end) tests for EE core. #833
Comments
On thing I like about using the GB e2e tests as a model is that they are incorporating tests for catching accessibility related things as well. I think it's important we incorporate some accessibility specific tests in things we do as well. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has been stale for a significant period of time without any activity. |
closed in favour of eventespresso/barista#689 |
The GB project has an end to tests that are maturing which could be used as a template (somewhat) for incorporating our own e2e tests for GB related things (and really we can expand for implementing e2e tests for all our things).
While we do have codeception tests, they haven't really gotten any momentum from our team in writing tests and part of that is probably due to the difficulty in getting it setup :(. I've found them valuable in catching some bugs that otherwise would have gotten released but they only retain that value when there's actual coverage.
As we move towards a more javascript heavy interface, and with the more rapid changes in the WP development world, I think it's becoming more crucial that we have some end to end tests in our automated set of tools.
The text was updated successfully, but these errors were encountered: