Conversation
|
Caution: This PR has changes that must be merged to WordPress.com |
| "nock": "10.0.6", | ||
| "node-wp-i18n": "1.2.3", | ||
| "prettier": "https://github.com/Automattic/wp-prettier/releases/download/wp-1.17.0/wp-prettier-1.17.0.tgz", | ||
| "puppeteer": "1.16.0", |
There was a problem hiding this comment.
Will quote @simison's comment from other PR(#12346 (comment)):
Noting that this is a bit heavier dependency (discussed p1554884363738500-slack-jetpack-gutenberg).
$ yarn why puppeteer
...
info Disk size without dependencies: "196.74MB"
info Disk size with unique dependencies: "197.57MB"
info Disk size with transitive dependencies: "199.36MB"
I don't think it's soooo heavy that it's worth the hassle to make pulling it optional (https://docs.npmjs.com/files/package.json#optionaldependencies, https://docs.npmjs.com/files/package.json#peerdependencies) but just wanted to give heads up.
|
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: June 4, 2019. |
7f64e5e to
955f9ce
Compare
|
brbrr, Your synced wpcom patch D28358-code has been updated. |
| "babel-loader": "8.0.6", | ||
| "chai": "4.2.0", | ||
| "commander": "2.20.0", | ||
| "config": "3.1.0", |
There was a problem hiding this comment.
Adding this dependency screws up this import:
This time for real. This PR adds a way to run ngrok powered WP installation in CI. Also includes a dummy test which tries to login into newly created WP site.
I plan to have these tests disabled after this PR will be merged since it does not include any actual tests. In further PR's I'll plan to add some real tests
Few things that I not really sure about, and would like to get some feedback on these:
travis config: stages vs one more parallel build. Former approach doubles build execution time (6min total). The overall e2e build time is 3 minutes, but it will grow as we'll add more tests. UPD: I updated travis config to run e2e job in parallel, and made it optional (e.g. failing job won't fail the build)Switched the job to run in parallel as the other jobsdependencies in rootDecided not to complicate things for now.package.json. E2E tests don't have much in common with root dependencies so it might be a good idea to move them into its own file. Not sure that we really need that.Changes proposed in this Pull Request:
Is this a new feature or does it add/remove features to an existing part of Jetpack?
Testing instructions:
yarn test-e2e. For this, you should have a local WP installation. The test expects that it's running on localhost, and your login creds arewordpress/wordpress. These can be tweaked by passing env vars along with the script eg:WP_BASE_URL="http://wpdev.localhost" WP_USERNAME=admin WP_PASSWORD=admin yarn test-e2e tests/e2e/specs/dummy.test.jsRUN_E2Eenv variable toggles e2e test execution. Head to https://travis-ci.org/Automattic/jetpack/settings and addRUN_E2Evariable set totrue:example build without E2E: https://travis-ci.org/Automattic/jetpack/builds/533758743
example build with E2E: https://travis-ci.org/Automattic/jetpack/builds/533754944
Proposed changelog entry for your changes: