github/puppeteer
0
0
Fork 0
mirror of https://github.com/puppeteer/puppeteer synced 2024-06-14 14:02:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
69c38fc2d0
puppeteer/.travis.yml

83 lines
2.1 KiB
YAML
Raw Normal View History

Add travis config (#29) This patch: - adds travis - adds eslint as required in devdeps - cleans up travis yml
2017-06-21 00:04:24 +00:00
language: node_js
chore: tidy up and de-duplicate Travis CI config (#5716)
2020-04-23 08:29:37 +00:00
services: xvfb
Node 6 support (#484) This patch: - introduces a transpiler which substitutes async/await logic with generators. - starts using the transpiler to generate a node6-compatible version of puppeteer - introduces a runtime-check to decide which version of code to use Fixes #316.
2017-08-24 19:20:05 +00:00
jobs:
include:
chore: Add macOS to Travis CI (#5708) Runs TypeScript and the unit tests on an OS X build.
2020-04-22 14:44:24 +00:00
- os: "osx"
chore: split out CI into unit tests + extra checks (#5749) * chore: split out CI into unit tests + extra checks Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-27 10:04:09 +00:00
name: 'Unit tests: macOS/Chromium'
chore: Add macOS to Travis CI (#5708) Runs TypeScript and the unit tests on an OS X build.
2020-04-22 14:44:24 +00:00
node_js: "10.19.0"
env:
- CHROMIUM=true
before_install:
- PUPPETEER_PRODUCT=firefox npm install
script:
- ls .local-chromium .local-firefox
- npm run tsc
chore: turn on Travis retries (#5787) To enable Travis to retry to work around ECONNRESET and similar that pops up.
2020-04-30 11:38:58 +00:00
- travis_retry npm run unit
chore: tidy up and de-duplicate Travis CI config (#5716)
2020-04-23 08:29:37 +00:00
chore(ci): re-enable tests on Windows (#5637) * chore: Add Windows to Travis This commit runs the unit tests on Windows. There are two tests failing on Windows that we skip. I spoke to Mathias B and we agreed to defer debugging this for now in favour of getting tests running on Windows. But we didn't want to ignore it forever, hence giving the test a date at which it will start to fail.
2020-04-17 13:27:50 +00:00
- os: "windows"
chore: split out CI into unit tests + extra checks (#5749) * chore: split out CI into unit tests + extra checks Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-27 10:04:09 +00:00
name: 'Unit tests: Windows/Chromium'
chore(ci): re-enable tests on Windows (#5637) * chore: Add Windows to Travis This commit runs the unit tests on Windows. There are two tests failing on Windows that we skip. I spoke to Mathias B and we agreed to defer debugging this for now in favour of getting tests running on Windows. But we didn't want to ignore it forever, hence giving the test a date at which it will start to fail.
2020-04-17 13:27:50 +00:00
node_js: "10.19.0"
env:
- CHROMIUM=true
before_install:
- PUPPETEER_PRODUCT=firefox npm install
script:
- ls .local-chromium .local-firefox
- npm run tsc
chore: migrate `src/USKeyboardLayout` to typescript (#5695) * chore: migrate `src/USKeyboardLayout` to typescript Don't think we need to expose the interface type for the keycodes so I've left it local for now. * retry windows unit tests
2020-04-21 09:21:45 +00:00
- travis_retry npm run unit
chore: tidy up and de-duplicate Travis CI config (#5716)
2020-04-23 08:29:37 +00:00
chore: split out CI into unit tests + extra checks (#5749) * chore: split out CI into unit tests + extra checks Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-27 10:04:09 +00:00
# Runs unit tests on Linux + Chromium
chore: update CI to run Travis + Linux + Chromium (#5583) Our CI build has been incredibly flaky across all three of our current CIs: * Appveyor: Chromium + Windows * Travis: Firefox + Linux, Chromium + Linux * Cirrus: Chromium + Linux, Chromium + Mac Legitimate issues and errors have been missed because it's expected that the CI is red and therefore it's not seen as an issue when a PR's build fails. We should have a build that covers the full combo of browsers and operating systems but it's more important to have a consistent, reliable green build where failures are genuine. So this commit strips our CI back to Chromium on Linux on Travis, and nothing more. Once this is stable we will expand out into more operating systems and bring back Firefox, too.
2020-04-08 09:38:07 +00:00
- node_js: "10.19.0"
chore: update how we track coverage during unit tests (#5779) * chore: update how we track coverage during unit tests The old method of tracking coverage was causing issues. If a test failed on CI, that test's failure would be lost because the test failing would in turn cause the coverage to fail, but the `process.exit(1)` in the coverage code caused Mocha to not output anything useful. Instead the coverage checker now: * tracks the coverage in memory in a Map (this hasn't changed) * after all tests, writes that to disk in test/coverage.json (which is gitignored) * we then run a single Mocha test that asserts every method was called. This means if the test run fails, the build will fail and give the error about that test run, and that output won't be lost when the coverage then fails too. Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-30 12:00:41 +00:00
name: 'Unit tests [with coverage]: Linux/Chromium'
chore: run Chromium on Node.js 12 on Travis (#5582)
2020-04-03 11:22:02 +00:00
env:
- CHROMIUM=true
chore: update CI to run Travis + Linux + Chromium (#5583) Our CI build has been incredibly flaky across all three of our current CIs: * Appveyor: Chromium + Windows * Travis: Firefox + Linux, Chromium + Linux * Cirrus: Chromium + Linux, Chromium + Mac Legitimate issues and errors have been missed because it's expected that the CI is red and therefore it's not seen as an issue when a PR's build fails. We should have a build that covers the full combo of browsers and operating systems but it's more important to have a consistent, reliable green build where failures are genuine. So this commit strips our CI back to Chromium on Linux on Travis, and nothing more. Once this is stable we will expand out into more operating systems and bring back Firefox, too.
2020-04-08 09:38:07 +00:00
before_install:
fix: set revision based on PUPPETEER_PRODUCT (#5643)
2020-04-15 11:30:42 +00:00
- PUPPETEER_PRODUCT=firefox npm install
chore: add test for npm package installing correctly (#5714) * chore: add test for npm package installing correctly This command packs up the module and installs it again to check we're correctly bundling everything we need to allow users to do a fresh install. * install realpath
2020-04-22 14:33:36 +00:00
script:
chore: update how we track coverage during unit tests (#5779) * chore: update how we track coverage during unit tests The old method of tracking coverage was causing issues. If a test failed on CI, that test's failure would be lost because the test failing would in turn cause the coverage to fail, but the `process.exit(1)` in the coverage code caused Mocha to not output anything useful. Instead the coverage checker now: * tracks the coverage in memory in a Map (this hasn't changed) * after all tests, writes that to disk in test/coverage.json (which is gitignored) * we then run a single Mocha test that asserts every method was called. This means if the test run fails, the build will fail and give the error about that test run, and that output won't be lost when the coverage then fails too. Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-30 12:00:41 +00:00
- travis_retry npm run unit-with-coverage
- npm run assert-unit-coverage
chore: split out CI into unit tests + extra checks (#5749) * chore: split out CI into unit tests + extra checks Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-27 10:04:09 +00:00
chore: add Node 12 and Node 14 to CI (#5821)
2020-05-07 09:24:03 +00:00
- node_js: "12.16.3"
name: 'Unit tests [Node 12]: Linux/Chromium'
env:
- CHROMIUM=true
before_install:
- PUPPETEER_PRODUCT=firefox npm install
script:
- travis_retry npm run unit
- node_js: "14.2.0"
name: 'Unit tests [Node 14]: Linux/Chromium'
env:
- CHROMIUM=true
before_install:
- PUPPETEER_PRODUCT=firefox npm install
script:
- travis_retry npm run unit
chore: split out CI into unit tests + extra checks (#5749) * chore: split out CI into unit tests + extra checks Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-27 10:04:09 +00:00
# This bot runs all the extra checks that aren't the main Puppeteer unit tests
- node_js: "10.19.0"
name: 'Extra tests: Linux/Chromium'
env:
- CHROMIUM=true
script:
chore: enforce src/protocol.d.ts is in sync (#5762) * chore: enforce src/protocol.d.ts is in sync On CI we run `npm run compare-protocol-d-ts` which checks that the file on disk is up to date with the protocol we fetch from the browser. Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-28 12:58:42 +00:00
- npm run compare-protocol-d-ts
chore: split out CI into unit tests + extra checks (#5749) * chore: split out CI into unit tests + extra checks Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-27 10:04:09 +00:00
- npm run test-install
- npm run lint
- npm run test-doclint
- npm run test-types
# Runs unit tests on Linux + Firefox
chore(test): re-enable Firefox testing on CI (#5608)
2020-04-08 10:18:29 +00:00
- node_js: "10.19.0"
chore: split out CI into unit tests + extra checks (#5749) * chore: split out CI into unit tests + extra checks Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-27 10:04:09 +00:00
name: 'Unit tests: Linux/Firefox'
chore(test): re-enable Firefox testing on CI (#5608)
2020-04-08 10:18:29 +00:00
env:
- FIREFOX=true
before_install:
fix: set revision based on PUPPETEER_PRODUCT (#5643)
2020-04-15 11:30:42 +00:00
- PUPPETEER_PRODUCT=firefox npm install
chore(test): re-enable Firefox testing on CI (#5608)
2020-04-08 10:18:29 +00:00
script:
chore: turn on Travis retries (#5787) To enable Travis to retry to work around ECONNRESET and similar that pops up.
2020-04-30 11:38:58 +00:00
- travis_retry npm run funit
chore: tidy up and de-duplicate Travis CI config (#5716)
2020-04-23 08:29:37 +00:00
notifications:
email: false
Reference in New Issue Copy Permalink