mirror of https://github.com/gosticks/wordpress-develop.git synced 2025-10-16 12:05:38 +00:00

History

Tonya Mork 36ecafde11 Build/Test Tools: Add end-to-end (e2e) tests for edit posts page. Adds e2e tests for 'Edit Posts': * No posts found * Shows a single post after publishing * Edit existing post via Edit button * Quick edit existing post via Quick Edit button * Delete post Props isabel_brison, azaozz, hellofromTonya, justinahinon, talldanwp, youknowriad. Fixes #49507. git-svn-id: https://develop.svn.wordpress.org/trunk@51990 602fd350-edb4-49c9-b593-d223f7449a82		2021-11-02 21:25:53 +00:00
..
config	Build/Test Tools: Introduce local visual regression testing.	2021-11-02 21:03:10 +00:00
specs	Build/Test Tools: Add end-to-end (e2e) tests for edit posts page.	2021-11-02 21:25:53 +00:00
jest.config.js	Block Editor: Update the WordPress Packages to the ones used in the Gutenberg 6.5 release	2019-09-19 15:17:39 +00:00
README.md	Build/Test Tools: Add end-to-end (e2e) tests `README.md`.	2021-10-12 18:50:34 +00:00
run-tests.js	Build/Test Tools: Remove explicit puppeteer dependency.	2021-03-29 18:05:47 +00:00

README.md

E2E Tests

End-To-End (E2E) tests for WordPress.

Running the tests

The e2e tests require a production-like environment to run. By default, they will assume an environment is available at http://localhost:8889, with username=admin and password=password.

If you don't already have an environment ready, you can set one up by following these instructions.

Then you can launch the tests by running:

npm run test:e2e

which will run the test suite using a headless browser.

If your environment has a different url, username or password to the default, you can provide the base URL, username and password like this:

npm run test:e2e -- --wordpress-base-url=http://mycustomurl --wordpress-username=username --wordpress-password=password

DO NOT run these tests in an actual production environment, as they will delete all your content.

For debugging purposes, you might want to follow the test visually. You can do so by running the tests in an interactive mode.

npm run test:e2e -- --puppeteer-interactive

You can also run a single test file separately:

npm run test:e2e tests/e2e/specs/hello.test.js

Documentation

Block Editor Handbook end to end testing overview: https://developer.wordpress.org/block-editor/contributors/code/testing-overview/#end-to-end-testing
Gutenberg e2e-test-utils package API docs: https://github.com/WordPress/gutenberg/tree/trunk/packages/e2e-test-utils
Puppeteer API docs: https://github.com/puppeteer/puppeteer#readme (the version we are using is indicated in the @wordpress/scripts package: https://github.com/WordPress/gutenberg/blob/trunk/packages/scripts/package.json)