Skip to content

Conversation

@rhcarvalho
Copy link
Contributor

The integration tests still work, independent of running them on multiple browsers through BrowserStack.

This change re-enables part of the old "BrowserStack" job, without the BrowserStack-dependant part.

It is unclear why we disabled everything at once, seems like an oversight. The tests were disabled in #3199.

The integration tests still work, independent of running them on
multiple browsers through BrowserStack.

This change re-enables part of the old "BrowserStack" job, without the
BrowserStack-dependant part.

It is unclear why we disabled everything at once, seems like an
oversight.
@rhcarvalho rhcarvalho requested review from a team, AbhiPrasad and iker-barriocanal and removed request for a team December 3, 2021 12:45
@rhcarvalho rhcarvalho added this to the Release Stability milestone Dec 3, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2021

size-limit report

Path Base Size (bebd1f9) Current Size Change
@sentry/browser - CDN Bundle (gzipped) 22.45 KB 22.45 KB +0.03% 🔺
@sentry/browser - Webpack 23.29 KB 23.29 KB 0%
@sentry/react - Webpack 23.32 KB 23.32 KB 0%
@sentry/nextjs Client - Webpack 49.7 KB 49.7 KB 0%
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped) 29.89 KB 29.9 KB +0.01% 🔺

@rhcarvalho
Copy link
Contributor Author

Ignoring the ember test failure that is being worked on by the team independent of this PR.

@rhcarvalho rhcarvalho merged commit 87ecf66 into master Dec 3, 2021
@rhcarvalho rhcarvalho deleted the rhcarvalho/browser-integration-tests branch December 3, 2021 13:05
@rhcarvalho
Copy link
Contributor Author

For future reference:

I've noticed this low-hanging fruit while reviewing #3989 and trying to understand what was the state of the existing yarn test:integration script. Upon quick inspection, it turned out everything still works except for running the tests on BrowserStack.

onurtemizkan pushed a commit that referenced this pull request Dec 19, 2021
The integration tests still work, independent of running them on
multiple browsers through BrowserStack.

This change re-enables part of the old "BrowserStack" job, without the
BrowserStack-dependant part.

It is unclear why we disabled everything at once, seems like an
oversight.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants