I have a few hundred client tests (--full-app and non---full-app) that all run without problem via meteortesting:browser-tests@1.7.0 in Meteor 2.16, both on two different chromium instances:
- Chromium 137.0.7151.68 (local dev)
- Chromium 112.0.5614.0 (CI, installed by
puppeteer@19.11.1)
When switching to Meteor 3.0, some of them fail, but only on Chromium 112.0.5614.0. At first I thought it was timing issues (async?), but I am now able to reproduce exactly the same failures locally by running that exact same chromium version.
I am going to investigate further, to see what the root cause is for those failures. But maybe someone already knows what could be going on here (@storyteller @jkuester)? Is it because Meteor 3.0 has dropped compatibility with old browsers?
I have two paths to solve the issue without code changes: either force meteortesting:browser-tests to use a more recent version of puppeteer that would embed a more recent chromium, or force puppeteer to run a more recent chromium in CI directly (@puppeteer/browsers?).