saucelabs / saucectl-puppeteer-example

A showcase of saucectl running puppeteer + jest.
Other
10 stars 17 forks source link

Example tests fail on chrome #27

Open lee-bennie opened 1 year ago

lee-bennie commented 1 year ago

When I run this after a fresh clone, with saucectl run, I get failed tests on chrome.

image

Am i doing something wrong here?

My config is untouched from the example:

kind: puppeteer
sauce:
  region: us-west-1
  concurrency: 100 # Controls how many suites are executed at the same time.
  metadata:
    name: saucectl puppeteer example
    tags:
      - e2e
      - release team
      - other tag
    build: Release $CI_COMMIT_SHORT_SHA
defaults:
  mode: docker
docker:
  # Affects how test files are transferred to the docker container when using the docker mode (--test-env docker).
  fileTransfer: copy # Choose between mount|copy.
# Controls what files are available in the context of a test run (unless explicitly excluded by .sauceignore).
rootDir: ./
puppeteer:
  version: 14.2.0 # See https://docs.saucelabs.com/dev/cli/saucectl/#supported-frameworks-and-browsers for a list of supported versions.
suites:
  - name: "chrome"
    testMatch: ["**/*.test.js"] # jest native glob support.
    browser: "chrome"
  - name: "firefox"
    testMatch: ["**/*.test.js"]
    browser: "firefox"
    groups: ["group1"]
alexplischke commented 1 year ago

You are indeed doing everything right 👍 However... we are slowing phasing out our support for puppeteer due to lack of interest (vs. playwright/cypress).

May we interest you in our other test offerings? Or are you set on puppeteer (would love to know why)?

lee-bennie commented 1 year ago

Ah, got it! Thanks so much for the reply. I'm not at all tied to puppeteer. I just sort of know it a little better than the other stuff, but perfectly willing to go in another direction. Thank you!