You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci: Streamline CI browser playwright tests (#13276)
This PR streamlines our browser integration tests a bit more:
1. We now only install chromium for playwright tests in most places.
This may help cut down test run time a bit, as we do not need to install
native dependencies for webkit and firefox everywhere.
2. I changed how we split the matrix jobs for the browser integration
tests. Previously, we sharded this via playwright. Now, we only do this
for esm tests, which we now only run in chromium, not all browsers. Only
the full bundle tests are run in all browsers (they are considerably
faster than the esm tests...), and there we now do not use sharding, but
have one matrix job for chromium (default), one for webkit and one for
firefox (where each can only install the native dependencies it needs).
3. I renamed the jobs a bit so that we can see a bit more of the job
name in the Github UI... it still truncates but you see more than
before, at least...
4. For all other playwright tests (e.g. e2e tests etc) we only install
chromium, AFAIK we do not have any non-chromium tests anywhere there.
Some data points:
* E2E tests seem to be about 10-20% faster than before, by looking
through traces here:
https://sentry.sentry.io/performance/trace/c5c1c643f1db0e8dd97df658405c2035/?field=title&field=event.type&field=project&field=user.display&field=timestamp&name=All+Events&node=txn-8892bc908791478aba163dd3edd373b4&project=5899451&query=&sort=-timestamp&source=discover&statsPeriod=1h×tamp=1723118364&yAxis=count%28%29
* For the playwright steps it's a bit harder to say as they are renamed,
also they are not super consistent in execution time, we'll have to
monitor it a bit afterwards, but subjectively it appears a bit shorter
in most cases too.
0 commit comments