@@ -397,7 +397,7 @@ bazel test //py:all
397397Test targets:
398398
399399|  Command                                                                          |  Description                                        | 
400- |   --------------------------------------------------------------------------------  |   --------------------------------------------------  | 
400+ | ---------------------------------------------------------------------------------- | ---------------------------------------------------- | 
401401|  ` bazel test //rb/... `                                                             |  Run unit, all integration tests and lint           | 
402402|  ` bazel test //rb:lint `                                                            |  Run RuboCop linter                                 | 
403403|  ` bazel test //rb/spec/... `                                                        |  Run unit and integration tests for all browsers    | 
@@ -406,23 +406,29 @@ Test targets:
406406|  ` bazel test //rb/spec/... --test_size_filters large `                              |  Run integration tests for all browsers             | 
407407|  ` bazel test //rb/spec/integration/... `                                            |  Run integration tests for all browsers             | 
408408|  ` bazel test //rb/spec/integration/... --test_tag_filters firefox `                 |  Run integration tests for local Firefox only       | 
409- |  ` bazel test //rb/spec/integration/... --test_tag_filters firefox-remote  `          |  Run integration tests for remote Firefox only       | 
409+ |  ` bazel test //rb/spec/integration/... --test_tag_filters bidi  `                     |  Run integration tests for all bidi tests            | 
410410|  ` bazel test //rb/spec/integration/... --test_tag_filters firefox,firefox-remote `  |  Run integration tests for local and remote Firefox | 
411411
412412Ruby test targets have the same name as the spec file with ` _spec.rb `  removed, so you can run them individually.
413- Integration tests targets also have a browser and remote suffix to control which browser to pick and whether to use Grid.
414- 
415- |  Test file                                               |  Test target                                                      | 
416- |  ------------------------------------------------------- |  ---------------------------------------------------------------- | 
417- |  ` rb/spec/unit/selenium/webdriver/proxy_spec.rb `          |  ` //rb/spec/unit/selenium/webdriver:proxy `                         | 
418- |  ` rb/spec/integration/selenium/webdriver/driver_spec.rb `  |  ` //rb/spec/integration/selenium/webdriver:driver-chrome `          | 
419- |  ` rb/spec/integration/selenium/webdriver/driver_spec.rb `  |  ` //rb/spec/integration/selenium/webdriver:driver-chrome-remote `   | 
420- |  ` rb/spec/integration/selenium/webdriver/driver_spec.rb `  |  ` //rb/spec/integration/selenium/webdriver:driver-firefox `         | 
421- |  ` rb/spec/integration/selenium/webdriver/driver_spec.rb `  |  ` //rb/spec/integration/selenium/webdriver:driver-firefox-remote `  | 
413+ Integration tests targets also allow specific suffixes to control specific browsers and settings.
414+ These targets are dynamically generated in the ` rb/spec/tests.bzl `  file
415+ Running in BiDi mode will be increasingly important as we re-implement classic selenium functionality with BiDi protocol.
416+ Not every test is set to run with BiDi by default, and which spec files are valid is explicitly
417+ with the ` BIDI_BROWSERS `  in the ` tests.bzl `  file and ` _BIDI_FILES `  in ` //rb/spec/integration/selenium/webdriver/BUILD.bazel ` 
418+ 
419+ |  Test file                                               |  Test target                                                          | 
420+ |  ------------------------------------------------------- | ----------------------------------------------------------------------| 
421+ |  ` rb/spec/unit/selenium/webdriver/proxy_spec.rb `          |  ` //rb/spec/unit/selenium/webdriver:proxy `                             | 
422+ |  ` rb/spec/integration/selenium/webdriver/driver_spec.rb `  |  ` //rb/spec/integration/selenium/webdriver:driver-chrome `              | 
423+ |  ` rb/spec/integration/selenium/webdriver/driver_spec.rb `  |  ` //rb/spec/integration/selenium/webdriver:driver-firefox-beta `        | 
424+ |  ` rb/spec/integration/selenium/webdriver/driver_spec.rb `  |  ` //rb/spec/integration/selenium/webdriver:driver-chrome-remote `       | 
425+ |  ` rb/spec/integration/selenium/webdriver/driver_spec.rb `  |  ` //rb/spec/integration/selenium/webdriver:driver-firefox-bidi `        | 
426+ |  ` rb/spec/integration/selenium/webdriver/driver_spec.rb `  |  ` //rb/spec/integration/selenium/webdriver:driver-chrome-remote-bidi `  | 
422427
423428Supported browsers:
424429
425430*  ` chrome ` 
431+ *  ` chrome-beta ` 
426432*  ` edge ` 
427433*  ` firefox ` 
428434*  ` firefox-beta ` 
@@ -441,6 +447,7 @@ Supported environment variables for use with `--test_env`:
441447-  ` WD_REMOTE_URL `  - URL of an already running server to use for remote tests
442448-  ` DOWNLOAD_SERVER `  - when ` WD_REMOTE_URL `  not set; whether to download and use most recently released server version for remote tests
443449-  ` DEBUG `  - turns on verbose debugging
450+ -  ` WEBDRIVER_BIDI `  - enables ` web_socket_url `  in the capabilities
444451-  ` HEADLESS `  - for chrome, edge and firefox; runs tests in headless mode
445452-  ` DISABLE_BUILD_CHECK `  - for chrome and edge; whether to ignore driver and browser version mismatches (allows testing Canary builds)
446453-  ` CHROME_BINARY `  - path to test specific Chrome browser
0 commit comments