ci: Add Browserstack GIthub workflow #798
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instructions
development
Summary
This PR sets up Browserstack tests in a Github Action. It follows the example workflow provided by the Browserstack docs here - https://www.browserstack.com/docs/automate/selenium/github-actions#sample-github-workflow-showing-a-browserstack-test
We originally discussed having it only be on release. However, I think it makes sense for it to be on push/pr also because we wouldn't want something to pass our non-CBT tests, merge them in, then upon release see that something is broken. Given that it is its own workflow, and our workflow minutes are unlimited for public repos, I see no issue with this. Note that this successfully runs here (although there are some failed tests, Chrome 48 tests here fail a few in the GHA, which matches the locally run Browserstack npm task, and Chrome 49 simply has a failed flaky test):
Testing Plan
Not locally, but the action successfully runs here - https://github.com/mParticle/mparticle-web-sdk/actions/runs/6818006161/job/18542716276
Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)