Draft
Conversation
This hasn't exactly been great, but it's sort of working locally. I'm going to try this from CI and see what happens.
This strips out most of the browsers so I should get just the one cross-browser test running. It also attempts to disable BS testing on the normal CI build.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR attempts to enable the BrowserStack SDK, for improved UX when testing cross-browser. I can't be 100% certain that it's going to work alongside the NUnit/Screenplay plugin though, so this is very much an experiment.
I'm starting small first.
Additionally, this PR strips out and disables a lot of the customer BS code that I wrote to avoid using the SDK. If I can switch to the SDK then I won't need it.