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

feat: add latest webdriverIO runner #207

Merged
merged 1 commit into from
Oct 16, 2019
Merged

Conversation

ineedfat
Copy link
Contributor

@ineedfat ineedfat commented Oct 15, 2019

Details

This PR adds runner-webdriverIO to support the latest webdriverIO (v5) whereas the previous runner-webdriver was based on an older version webdriverIO(v4).

The new webdriver runner implementation is consistent with the existing runner-headless minus the tracing ability (simply because we are supporting multiple browsers).

Tested the new runner with Best running locally and behind agent-hub against Selenium-Standalone-Server with both chromedriver and geckodriver.

Possible future improvement:

Ideally, it would be best if we can run webdriverIO using client -> agent-hub -> agent (runner-remote) -> runner-webdriverIO. This would allow us to use the agent-hub for scaling and the runner-remote agent as a broker to run different runners, but currently it's somewhat complex to implement this with the current implementation. :D

Oct-15-2019 14-21-32

Does this PR introduce a breaking change?

  • Yes
  • No

@@ -19,7 +19,7 @@
{ "path": "./packages/@best/runner-headless" },
{ "path": "./packages/@best/runner-remote" },
{ "path": "./packages/@best/runner-hub" },
// { "path": "./packages/@best/runner-webdriver" },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove comment

return { results, environment, benchmarkInfo, projectConfig };
} catch (e) {
runnerLogStream.onBenchmarkError(benchmarkEntry);
throw e;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we await browser.close() and terminate() before throwing?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't it it really matters

@diervo diervo merged commit 7e457b0 into salesforce:master Oct 16, 2019
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