| 1 |
import {defineConfig, devices} from '@playwright/test'; |
| 2 |
import {STORAGE_STATE_PATH, WP_BASE_URL} from './tests/e2e/environment'; |
| 3 |
|
| 4 |
export default defineConfig({ |
| 5 |
testDir: './tests/e2e', |
| 6 |
timeout: 60_000, |
| 7 |
retries: process.env.CI ? 2 : 0, |
| 8 |
/* |
| 9 |
* GiveWP's admin screens share one site's options and database, so parallel workers would see |
| 10 |
* each other's state. Revisit per-worker isolation when the suite grows enough to need it. |
| 11 |
*/ |
| 12 |
workers: 1, |
| 13 |
reporter: process.env.CI ? 'github' : 'list', |
| 14 |
globalSetup: './tests/e2e/global-setup.ts', |
| 15 |
outputDir: './artifacts/test-results', |
| 16 |
use: { |
| 17 |
baseURL: WP_BASE_URL, |
| 18 |
// Local environments that terminate TLS in front of wp-env use a self-signed certificate. |
| 19 |
ignoreHTTPSErrors: true, |
| 20 |
storageState: STORAGE_STATE_PATH, |
| 21 |
/* |
| 22 |
* retain-on-failure still records every test and discards the passing ones, which costs |
| 23 |
* CPU on a runner where WordPress is the bottleneck. on-first-retry records only the rerun |
| 24 |
* of a test that already failed, and CI retries twice, so failures still ship a video and trace. |
| 25 |
*/ |
| 26 |
video: 'on-first-retry', |
| 27 |
screenshot: 'only-on-failure', |
| 28 |
trace: 'on-first-retry', |
| 29 |
}, |
| 30 |
projects: [ |
| 31 |
{ |
| 32 |
name: 'chromium', |
| 33 |
use: {...devices['Desktop Chrome']}, |
| 34 |
}, |
| 35 |
{ |
| 36 |
name: 'headed', |
| 37 |
use: {...devices['Desktop Chrome'], headless: false, launchOptions: {slowMo: 800}}, |
| 38 |
}, |
| 39 |
], |
| 40 |
}); |
| 41 |
|
