woocommerce/tests/e2e/env/README.md

161 lines
5.1 KiB
Markdown
Raw Normal View History

# End to End Testing Environment
A reusable and extendable E2E testing environment for WooCommerce extensions.
## Installation
```bash
npm install @woocommerce/e2e-environment --save
npm install jest --global
```
## Configuration
2020-08-05 18:55:28 +00:00
The `@woocommerce/e2e-environment` package exports configuration objects that can be consumed in JavaScript config files in your project. Additionally, it includes a hosting container for running tests and includes instructions for creating your Travis CI setup.
### Babel Config
2020-05-15 09:28:21 +00:00
Make sure you `npm install @babel/preset-env --save` if you have not already done so. Afterwards, extend your project's `babel.config.js` to contain the expected presets for E2E testing.
```js
2020-09-15 17:08:19 +00:00
const { useE2EBabelConfig } = require( '@woocommerce/e2e-environment' );
module.exports = function( api ) {
api.cache( true );
2020-09-15 17:08:19 +00:00
return useE2EBabelConfig( {
presets: [
'@wordpress/babel-preset-default',
],
2020-09-15 17:08:19 +00:00
} );
};
```
### ES Lint Config
The E2E environment uses Puppeteer for headless browser testing, which uses certain globals variables. Avoid ES Lint errors by extending the config.
```js
2020-09-15 17:08:19 +00:00
const { useE2EEsLintConfig } = require( '@woocommerce/e2e-environment' );
2020-09-15 17:08:19 +00:00
module.exports = useE2EEsLintConfig( {
root: true,
env: {
browser: true,
2020-09-15 17:08:19 +00:00
es6: true,
node: true
},
globals: {
wp: true,
wpApiSettings: true,
wcSettings: true,
2020-09-15 17:08:19 +00:00
es6: true
},
2020-09-15 17:08:19 +00:00
} );
```
### Jest Config
The E2E environment uses Jest as a test runner. Extending the base config is needed in order for Jest to run your project's test files.
```js
const path = require( 'path' );
2020-08-05 18:55:28 +00:00
const { useE2EJestConfig } = require( '@woocommerce/e2e-environment' );
2020-08-05 18:55:28 +00:00
const jestConfig = useE2EJestConfig( {
roots: [ path.resolve( __dirname, '../specs' ) ],
2020-08-05 18:55:28 +00:00
} );
module.exports = jestConfig;
```
2020-08-05 18:55:28 +00:00
**NOTE:** Your project's Jest config file is expected to be: `tests/e2e/config/jest.config.js`.
2021-03-08 20:56:47 +00:00
#### Test Screenshots
The test sequencer provides a screenshot function for test failures. To enable screenshots on test failure use
```shell script
WC_E2E_SCREENSHOTS=1 npx wc-e2e test:e2e
```
Screenshots will be saved to `tests/e2e/screenshots`
2020-08-05 18:55:28 +00:00
### Jest Puppeteer Config
2020-08-05 18:55:28 +00:00
The test sequencer uses the following default Puppeteer configuration:
```js
2020-08-05 18:55:28 +00:00
// headless
puppeteerConfig = {
launch: {
// Required for the logged out and logged in tests so they don't share app state/token.
browserContext: 'incognito',
},
2020-08-05 18:55:28 +00:00
};
// dev mode
puppeteerConfig = {
launch: {
...jestPuppeteerConfig.launch, // @automattic/puppeteer-utils
ignoreHTTPSErrors: true,
2020-10-15 17:53:21 +00:00
headless: false,
2020-08-05 18:55:28 +00:00
args: [ '--window-size=1920,1080', '--user-agent=chrome' ],
devtools: true,
defaultViewport: {
width: 1280,
height: 800,
},
},
};
```
2020-08-05 18:55:28 +00:00
You can customize the configuration in `tests/e2e/config/jest-puppeteer.config.js`
2020-08-05 18:55:28 +00:00
```js
const { useE2EJestPuppeteerConfig } = require( '@woocommerce/e2e-environment' );
2020-08-05 18:55:28 +00:00
const puppeteerConfig = useE2EJestPuppeteerConfig( {
launch: {
headless: false,
}
} );
2020-08-05 18:55:28 +00:00
module.exports = puppeteerConfig;
```
2020-08-05 18:55:28 +00:00
### Jest Setup
2020-08-05 18:55:28 +00:00
Jest provides setup and teardown functions similar to PHPUnit. The default setup and teardown is in [`tests/e2e/env/src/setup/jest.setup.js`](src/setup/jest.setup.js). Additional setup and teardown functions can be added to [`tests/e2e/config/jest.setup.js`](../config/jest.setup.js)
2020-08-05 18:55:28 +00:00
### Container Setup
2020-08-05 18:55:28 +00:00
Depending on the project and testing scenario, the built in testing environment container might not be the best solution for testing. This could be local testing where there is already a testing container, a repository that isn't a plugin or theme and there are multiple folders mapped into the container, or similar. The `e2e-environment` container supports using either the built in container or an external container. See the the appropriate readme for details:
2021-02-25 23:51:14 +00:00
- [Built In Container](https://github.com/woocommerce/woocommerce/tree/trunk/tests/e2e/env/builtin.md)
- [External Container](https://github.com/woocommerce/woocommerce/tree/trunk/tests/e2e/env/external.md)
### Slackbot Setup
The test runner has support for posting a message and screenshot to a Slack channel when there is an error in a test. It currently supports both Travis CI and Github actions.
To implement the Slackbot in your CI:
- Create a [Slackbot App](https://slack.com/help/articles/115005265703-Create-a-bot-for-your-workspace)
- Give the app the following permissions:
- `channel:join`
- `chat:write`
- `files:write`
- `incoming-webhook`
- Add the app to your channel
- In your CI environment
- Add the environment variable `WC_E2E_SCREENSHOTS=1`
- Add your app Oauth token to a CI secret `E2E_SLACK_TOKEN`
- Add the Slack channel name (without the #) to a CI secret `E2E_SLACK_CHANNEL`
- Add the secrets to the test run using the same variable names
To test your setup, create a pull request that triggers an error in the E2E tests.
## Additional information
2021-02-25 23:51:14 +00:00
Refer to [`tests/e2e/core-tests`](https://github.com/woocommerce/woocommerce/tree/trunk/tests/e2e/core-tests) for some test examples, and [`tests/e2e`](https://github.com/woocommerce/woocommerce/tree/trunk/tests/e2e) for general information on e2e tests.