1bf35ac737
* First pass at Playwright test migration * Set working directory * Remove exec * Configure the environment before testing * Remove filter * Update paths for tests * Try explicitly stating working-directory * Change tests directory * Try running all tests * Uncommented project * Update commands to run tests * Comment out env config * Uncomment * Changelog * Set up multiple test configurations * Update failing test * Update paths for artifacts * Update path to artifacts * Path to results * remove unnecessary file * Skip translation E2E tests Skipping translation tests until we fix the missing translations issues after we changed the domain to "woocommerce" * Update the artifacts path * Fix lint errors --------- Co-authored-by: Jon Lane <jon.lane@automattic.com> Co-authored-by: Luigi Teschio <gigitux@gmail.com> Co-authored-by: Saad Tarhi <saad.trh@gmail.com> |
||
|---|---|---|
| .. | ||
| bin | ||
| mocks/custom-plugins | ||
| playwright-utils | ||
| test-data/data | ||
| tests | ||
| types | ||
| utils | ||
| wc-blocks-eslint-rules | ||
| .eslintrc.js | ||
| README.md | ||
| block-theme.setup.ts | ||
| classic-theme.setup.ts | ||
| global-setup.ts | ||
| global-teardown.ts | ||
| playwright.classic-theme.config.ts | ||
| playwright.config.ts | ||
| playwright.side-effects.config.ts | ||
| tsconfig.json | ||
README.md
WooCommerce Blocks Playwright End to End Tests
This is the documentation for the new E2E testing setup based on Playwright and wp-env. Over time, these playwright E2E tests should replace the current Puppeteer E2E tests.
Table of contents
Pre-requisites
- Node.js (Installation instructions)
- NVM (Installation instructions)
- Docker and Docker Compose (Installation instructions)
Note, that if you are on Mac and you install docker through other methods such as homebrew, for example, your steps to set it up might be different. The commands listed in steps below may also vary.
If you are using Windows, we recommend using Windows Subsystem for Linux (WSL) for running E2E tests. Follow the WSL Setup Instructions first before proceeding with the steps below.
Introduction
End-to-end tests are powered by Playwright. The test site is spun up using wp-env (recommended), but we will continue to support e2e-environment in the meantime.
Running tests for the first time
nvm use
npm install
npm run env:start
npm run test:e2e
To run the test again, re-create the environment to start with a fresh state
npm run env:restart
npm run test:e2e
Tests with side effects
We call tests that affect other tests (ones that modify the site settings, using custom plugins) are tests with side effects and we split those tests to a separate test suite:
npm run test:e2e:side-effects
Note: All commands parameters of test:e2e can be used for
test:e2e:side-effects.
Other ways of running tests
Headless mode:
npm run test:e2e
Interactive UI mode:
npm run test:e2e -- --ui
Headed mode:
npm run test:e2e -- --headed
Debug mode:
npm run test:e2e -- --debug
Running a single test:
npm run test:e2e ./tests/e2e/tests/example.spec.ts
To see all options, run the following command:
npx playwright test --help