mirror_php/wordpress
1
0
Fork 0
mirror of git://develop.git.wordpress.org/ synced 2025-01-17 12:58:25 +01:00
Code Issues Actions 98 Packages Projects Releases Wiki Activity
wordpress/tests/e2e
History
Timothy Jacobs ec80646878 App Passwords: Don't prevent non-unique App Password names. 
In [50030] we enforced that Application Passwords have unique names. This was done with the assumption that applications would not connect to a user multiple times. However, in practice we've seen applications run into issues with the unique name constraint. Depending on the app, they may not know if they've been authorized before, or they may intentionally allow connecting multiple times. To prevent friction, App developers need to make their App Name unique, and in doing so often include things like the current date & time, which is already included in the App Passwords list table.

This commit removes this requirement to simplify usage of the Authorize Application flow.

Props mark-k, Boniu91, timothyblynjacobs, peterwilsoncc.
Fixes #54213.


git-svn-id: https://develop.svn.wordpress.org/trunk@59084 602fd350-edb4-49c9-b593-d223f7449a82
2024-09-24 16:38:36 +00:00
..
config
Build/Test Tools: Migrate Puppeteer tests to Playwright.
2023-10-13 08:11:41 +00:00
specs
App Passwords: Don't prevent non-unique App Password names.
2024-09-24 16:38:36 +00:00
playwright.config.js
Build/Test Tools: Migrate Puppeteer tests to Playwright.
2023-10-13 08:11:41 +00:00
README.md
Build/Test Tools: Migrate Puppeteer tests to Playwright.
2023-10-13 08:11:41 +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:

WP_BASE_URL=http://mycustomurl WP_USERNAME=username WP_PASSWORD=password npm run test:e2e

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 -- --ui

UI Mode let's you explore, run and debug tests with a time travel experience complete with watch mode. All test files are loaded into the testing sidebar where you can expand each file and describe block to individually run, view, watch and debug each test.

You can also run a single test file separately:

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

Documentation