|tagger||Kevin Moore <firstname.lastname@example.org>||Wed Feb 03 13:01:35 2021 -0800|
|author||kevmoo <email@example.com>||Wed Feb 03 20:29:04 2021 +0000|
|committer||Kevin Moore <firstname.lastname@example.org>||Wed Feb 03 20:39:06 2021 +0000|
Prepare to publish for stable null safety PiperOrigin-RevId: 355456884
Provides WebDriver bindings for Dart. These use the WebDriver JSON interface, and as such, require the use of the WebDriver remote server.
In your Dart code, you can use:
import 'package:webdriver/io.dart'; WebDriver driver = createDriver(...);
This will use by default the asynchronous, JSON wire spec implementation. You now can also use a synchronous version of WebDriver:
import 'package:webdriver/sync_io.dart'; final driver = createDriver(...);
This version of WebDriver supports both the JSON wire spec and W3C spec, allowing use with modern versions of Firefox. This defaults to the JSON wire spec, but can also be configured to use the W3C spec or even to try and automatically infer the spec during session creation:
final w3cDriver = createDriver(spec: WebDriverSpec.W3c); // Use W3C spec. final anyDriver = createDriver(spec: WebDriverSpec.Auto); // Infer spec.
Unfortunately using bazel with Dart libraries and Dart WebDriver is not yet supported. We hope to add this at some point, but for now pub still works.
As a consequence, running tests is a bit more complicated than we'd like:
Launch a WebDriver binar(ies).
First, bring up chromedriver / geckodriver. Other conforming WebDriver binaries should work as well, but we test against these:
chromedriver --port=4444 --url-base=wd/hub --verbose geckodriver --port=4445
ChromeDriver is used to test our JSON wire spec implementation, and geckodriver is used to test our W3C spec implementation.
Synchronous tests are labeled as Chrome/Firefox. All async tests run exclusively against Chrome (as async, like ChromeDriver supports only the old JSON wire spec).
Run a test. All files suffixed with ‘_test.dart’ are tests.
pub run test/path/to/test.dart -r expanded -p vm
Or to run all tests:
pub run test -r expanded -p vm
You should probably go get a coffee or something, this is gonna take a while.