Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[wptrunner] Fix regression in Sauce Labs browser #12170

Merged
merged 1 commit into from Jul 24, 2018

Conversation

jugglinmike
Copy link
Contributor

A recent commit [1] updated the invocation of the start method for
"Browser" instances by introducing a new keyword argument. This
interfered with the use of the "Sauce Labs" browser because its
implementation of the start method did not accommodate any keyword
arguments.

Update the start method to support (but ignore) all keyword arguments.

[1] 91803e3


@jgraham do you have any thoughts on how we could test for this?

A recent commit [1] updated the invocation of the `start` method for
"Browser" instances by introducing a new keyword argument. This
interfered with the use of the "Sauce Labs" browser because its
implementation of the `start` method did not accommodate any keyword
arguments.

Update the `start` method to support (but ignore) all keyword arguments.

[1] 91803e3
@jgraham jgraham merged commit addfa0d into web-platform-tests:master Jul 24, 2018
@jgraham
Copy link
Contributor

jgraham commented Jul 24, 2018

Not really good thoughts about how to test, other than actually running sauce. I suppose the other approach involves mocking out the actual sauce parts and just pretending to the code that we're running tests. Or, you know, using a language with a type system that can catch trivial errors…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants