Ecosyste.ms: OpenCollective

An open API service for software projects hosted on Open Collective.

github.com/wp-graphql/wp-graphql-e2e-tests-example

An example plugin showing how to add End to End tests to a WordPress plugin
https://github.com/wp-graphql/wp-graphql-e2e-tests-example

- move the workflow to the proper directory location

ad77958e9be6b69f7a8f42dd4ee34a6c0bcc2e64 authored almost 3 years ago by Jason Bahl <[email protected]>
- Add e2e-tests.yml to run tests in Github when Pull Requests are opened, or when code is pushed to the master branch.

b811b18e49c2dab028217a30d76661ef6b53086e authored almost 3 years ago by Jason Bahl <[email protected]>
- add the assertion to check that the plugin is active

8cb45e2a2e0c88a6c974d5eaae95b67dd13f59f6 authored almost 3 years ago by Jason Bahl <[email protected]>
- adding a `.vscode/launch.json` config so vscode can run the tests properly in debug mode

eb723669a0d510b059fc5d90d548a7e33b2f935c authored almost 3 years ago by Jason Bahl <[email protected]>
Merge branch 'master' of github.com:wp-graphql/wp-graphql-e2e-tests-example

# Conflicts:
# tests/e2e/example.spec.js

368de47fdec25c1eb75e2f00b457d2453d9fba7e authored almost 3 years ago by Jason Bahl <[email protected]>
- adds missing `await` before the visitAdminPage call

14c05cfacdcb53a6aea725cbeba3c83baa00ae1d authored almost 3 years ago by Jason Bahl <[email protected]>
- Adding initial test functionality to login the admin user and visit the admin page

4503232a578d5c20ad541ae06fc8ea9392346ab1 authored almost 3 years ago by Jason Bahl <[email protected]>
- add test scripts to package.json

- add basic e2e test file

4c82b3988dd9dbef0e9e7b9423fa3058d1ae3265 authored almost 3 years ago by Jason Bahl <[email protected]>
- add a .wp-env.json file to configure the current plugin to be active in the WordPress environment

05c1abda32e9e71ef9424494e72004f64280d6dc authored almost 3 years ago by Jason Bahl <[email protected]>
- Fix description in the main plugin file to be "Description" instead of "Plugin Description"

82042b1d80923acea7dcf726e245245b66b7c406 authored almost 3 years ago by Jason Bahl <[email protected]>
- adding "wp-env" script

ffb0d85f0ef6e46a499bc339b8a2af8664fccead authored almost 3 years ago by Jason Bahl <[email protected]>
- add .gitignore file

- add package.json with devDependencies
- run npm install, which generates the package-lock.json

430e95d4987f24a8f82a63b5f56329b165a3bd6d authored almost 3 years ago by Jason Bahl <[email protected]>
Add README for the plugin

36240d38ada1968e8e5998b7821d51592b86e241 authored almost 3 years ago by Jason Bahl <[email protected]>
Scaffold the plugin with the plugin file. This is all that is needed to be a valid WordPress plugin. Of course, there's no functionality, but WordPress does recognize this as a plugin that can be activated.

bd2890398a83a25aaaaa15812602a60c09df8f9d authored almost 3 years ago by Jason Bahl <[email protected]>