Morph MORPH
SIGN IN SIGN UP
SeleniumHQ / selenium UNCLAIMED

A browser automation framework and ecosystem.

34182 0 173 Java
Normal View History Raw
Expose local browser drivers through bazel
2020-12-01 16:37:01 +00:00
load(
[bazel] Move common browser data to //common
2021-03-15 15:38:24 +00:00
"//common:browsers.bzl",
[bazel] Move more java test infra into the java package
2021-03-15 16:31:32 +00:00
"COMMON_TAGS",
[java] add test targets for chrome beta (#16860) * add chrome beta to java tests * fix chrome beta references
2026-01-08 12:31:06 -06:00
"chrome_beta_data",
[bazel] Run buildifier
2021-01-19 10:23:10 +00:00
"chrome_data",
"edge_data",
[bazel] Add support for pinning Firefox Dev Edition (#12762)
2023-09-19 16:18:13 +02:00
"firefox_beta_data",
[bazel] Run buildifier
2021-01-19 10:23:10 +00:00
"firefox_data",
[bazel] Move common browser data to //common
2021-03-15 15:38:24 +00:00
)
load(
"//java:browsers.bzl",
[java] add test targets for chrome beta (#16860) * add chrome beta to java tests * fix chrome beta references
2026-01-08 12:31:06 -06:00
"chrome_beta_jvm_flags",
[bazel] Move common browser data to //common
2021-03-15 15:38:24 +00:00
"chrome_jvm_flags",
"edge_jvm_flags",
[bazel] Add support for pinning Firefox Dev Edition (#12762)
2023-09-19 16:18:13 +02:00
"firefox_beta_jvm_flags",
[bazel] Run buildifier
2021-01-19 10:23:10 +00:00
"firefox_jvm_flags",
)
[bazel] Bump contrib_rules_jvm to 0.19.0
2023-10-09 18:04:52 +01:00
load(":junit5_test.bzl", "junit5_test")
Expose local browser drivers through bazel
2020-12-01 16:37:01 +00:00
[bazel] Use the new test suites for selenium test suites In the java tree, at least. This dramatically improves clean build time, with critical path times going from 825s to 263s on my machine. We still achieve good parallelism in the test execution times.
2020-11-30 13:30:00 +00:00
DEFAULT_BROWSER = "firefox"
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
[bazel] Use the new test suites for selenium test suites In the java tree, at least. This dramatically improves clean build time, with critical path times going from 825s to 263s on my machine. We still achieve good parallelism in the test execution times.
2020-11-30 13:30:00 +00:00
BROWSERS = {
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
"chrome": {
Move java sources and tests into a single tree (#9710) This emphasizes that all the java code is inter-related. We make use of bazel to avoid introducing Java 8 incompatible changes, and bazel's visibility rules to ensure that generated jars only contain what they should.
2021-08-03 17:39:24 +03:00
"deps": ["//java/src/org/openqa/selenium/chrome"],
Expose local browser drivers through bazel
2020-12-01 16:37:01 +00:00
"jvm_flags": ["-Dselenium.browser=chrome"] + chrome_jvm_flags,
"data": chrome_data,
[bazel] Move more java test infra into the java package
2021-03-15 16:31:32 +00:00
"tags": COMMON_TAGS + ["chrome"],
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
},
[java] add test targets for chrome beta (#16860) * add chrome beta to java tests * fix chrome beta references
2026-01-08 12:31:06 -06:00
"chrome-beta": {
"deps": ["//java/src/org/openqa/selenium/chrome"],
"jvm_flags": ["-Dselenium.browser=chrome"] + chrome_beta_jvm_flags,
"data": chrome_beta_data,
"tags": COMMON_TAGS + ["chrome", "chrome-beta"],
},
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
"edge": {
Move java sources and tests into a single tree (#9710) This emphasizes that all the java code is inter-related. We make use of bazel to avoid introducing Java 8 incompatible changes, and bazel's visibility rules to ensure that generated jars only contain what they should.
2021-08-03 17:39:24 +03:00
"deps": ["//java/src/org/openqa/selenium/edge"],
Expose local browser drivers through bazel
2020-12-01 16:37:01 +00:00
"jvm_flags": ["-Dselenium.browser=edge"] + edge_jvm_flags,
"data": edge_data,
[java] Enable Edge tests on RBE
2024-03-15 11:26:40 -07:00
"tags": COMMON_TAGS + ["edge"],
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
},
"firefox": {
Move java sources and tests into a single tree (#9710) This emphasizes that all the java code is inter-related. We make use of bazel to avoid introducing Java 8 incompatible changes, and bazel's visibility rules to ensure that generated jars only contain what they should.
2021-08-03 17:39:24 +03:00
"deps": ["//java/src/org/openqa/selenium/firefox"],
Expose local browser drivers through bazel
2020-12-01 16:37:01 +00:00
"jvm_flags": ["-Dselenium.browser=ff"] + firefox_jvm_flags,
"data": firefox_data,
[bazel] Move more java test infra into the java package
2021-03-15 16:31:32 +00:00
"tags": COMMON_TAGS + ["firefox"],
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
},
[bazel] Add support for pinning Firefox Dev Edition (#12762)
2023-09-19 16:18:13 +02:00
"firefox-beta": {
"deps": ["//java/src/org/openqa/selenium/firefox"],
"jvm_flags": ["-Dselenium.browser=ff"] + firefox_beta_jvm_flags,
"data": firefox_beta_data,
[build] allow filtering firefox beta and firefox dev from test runs
2023-10-30 21:12:48 -05:00
"tags": COMMON_TAGS + ["firefox", "firefox-beta"],
[bazel] Add support for pinning Firefox Dev Edition (#12762)
2023-09-19 16:18:13 +02:00
},
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
"ie": {
Move java sources and tests into a single tree (#9710) This emphasizes that all the java code is inter-related. We make use of bazel to avoid introducing Java 8 incompatible changes, and bazel's visibility rules to ensure that generated jars only contain what they should.
2021-08-03 17:39:24 +03:00
"deps": ["//java/src/org/openqa/selenium/ie"],
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
"jvm_flags": ["-Dselenium.browser=ie"] +
[bazel] Automated reformatting of build files
2020-05-14 17:30:31 +01:00
select({
[bazel] Make it easier for external projects to use browser pinning
2021-02-23 08:40:45 +00:00
"@selenium//common:windows": ["-Dselenium.skiptest=false"],
"@selenium//conditions:default": ["-Dselenium.skiptest=true"],
[bazel] Automated reformatting of build files
2020-05-14 17:30:31 +01:00
}),
Expose local browser drivers through bazel
2020-12-01 16:37:01 +00:00
"data": [],
[build] rename skip-remote to skip-rbe differentiate this tag from "remote" which is used to indicate when a test uses the grid
2025-03-21 20:51:16 -07:00
"tags": COMMON_TAGS + ["exclusive-if-local", "ie", "skip-rbe"],
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
},
"safari": {
Move java sources and tests into a single tree (#9710) This emphasizes that all the java code is inter-related. We make use of bazel to avoid introducing Java 8 incompatible changes, and bazel's visibility rules to ensure that generated jars only contain what they should.
2021-08-03 17:39:24 +03:00
"deps": ["//java/src/org/openqa/selenium/safari"],
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
"jvm_flags": ["-Dselenium.browser=safari"] +
[bazel] Automated reformatting of build files
2020-05-14 17:30:31 +01:00
select({
[bazel] Make it easier for external projects to use browser pinning
2021-02-23 08:40:45 +00:00
"@selenium//common:macos": ["-Dselenium.skiptest=false"],
"@selenium//conditions:default": ["-Dselenium.skiptest=true"],
[bazel] Automated reformatting of build files
2020-05-14 17:30:31 +01:00
}),
Expose local browser drivers through bazel
2020-12-01 16:37:01 +00:00
"data": [],
[build] rename skip-remote to skip-rbe differentiate this tag from "remote" which is used to indicate when a test uses the grid
2025-03-21 20:51:16 -07:00
"tags": COMMON_TAGS + ["exclusive-if-local", "safari", "skip-rbe"],
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
},
}
Remove IE from default list of browsers used for java tests (#12152) Co-authored-by: Diego Molina <diemol@users.noreply.github.com>
2023-06-06 04:35:03 +01:00
DEFAULT_BROWSERS = [b for b in BROWSERS.keys() if b != "ie"]
def selenium_test(name, test_class, size = "medium", browsers = DEFAULT_BROWSERS, **kwargs):
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
if len(browsers) == 0:
fail("At least one browser must be specified.")
[bazel] Use the new test suites for selenium test suites In the java tree, at least. This dramatically improves clean build time, with critical path times going from 825s to 263s on my machine. We still achieve good parallelism in the test execution times.
2020-11-30 13:30:00 +00:00
default_browser = DEFAULT_BROWSER if DEFAULT_BROWSER in browsers else browsers[0]
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
test_name = test_class.rpartition(".")[2]
Fix closure tests by not stripping data attribute
2020-10-06 12:47:12 +01:00
data = kwargs["data"] if "data" in kwargs else []
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
jvm_flags = kwargs["jvm_flags"] if "jvm_flags" in kwargs else []
tags = kwargs["tags"] if "tags" in kwargs else []
[java] Remote selenium-remote tag from test targets If it's there, then `bazel query "attr(tags, 'remote', tests(//java/...))` would also return non-remote targets. This happens because Bazel queries for partial match in attribute ("selenium-remote" contains "remote").
2023-05-02 08:16:23 -07:00
remote = False
if "selenium-remote" in tags:
tags.remove("selenium-remote")
remote = True
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
stripped_args = dict(**kwargs)
Fix closure tests by not stripping data attribute
2020-10-06 12:47:12 +01:00
stripped_args.pop("data", None)
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
stripped_args.pop("jvm_flags", None)
stripped_args.pop("tags", None)
[bazel] Mark remaining tests as being skipped for remote builds
2023-06-05 21:16:59 +01:00
inherited_env = stripped_args.pop("env_inherit", []) + ["REMOTE_BUILD"]
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
Correctly generate test suites and all targets for java selenium tests
2022-07-05 15:26:50 +01:00
all_tests = []
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
for browser in browsers:
[bazel] Use the new test suites for selenium test suites In the java tree, at least. This dramatically improves clean build time, with critical path times going from 825s to 263s on my machine. We still achieve good parallelism in the test execution times.
2020-11-30 13:30:00 +00:00
if not browser in BROWSERS:
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
fail("Unrecognized browser: " + browser)
[bazel] Generate a test per test file for java The developer experience of only having a test suite and using filters was pretty nasty in IJ with a single suite. Rolling back that change so that we generate a test target per test class.
2021-03-16 16:25:12 +00:00
test = name if browser == default_browser else "%s-%s" % (name, browser)
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
[bazel] Bump contrib_rules_jvm to 0.19.0
2023-10-09 18:04:52 +01:00
junit5_test(
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
name = test,
test_class = test_class,
size = size,
[bazel] Use the new test suites for selenium test suites In the java tree, at least. This dramatically improves clean build time, with critical path times going from 825s to 263s on my machine. We still achieve good parallelism in the test execution times.
2020-11-30 13:30:00 +00:00
jvm_flags = BROWSERS[browser]["jvm_flags"] + jvm_flags,
[java] Allow linting only on the default test (#10792) After migrating Selenium tests to JUnit 5, java_junit5_test delegates to contrib_rules_jvm’s java_test, and that adds lint tests for every target. We want to add one set of lint tests, since the rest are going to be identical. Therefore, we tag all but one test with no-lint
2022-06-22 11:28:58 +02:00
# Only allow linting on the default test
tags = BROWSERS[browser]["tags"] + tags + ([] if test == name else ["no-lint"]),
Expose local browser drivers through bazel
2020-12-01 16:37:01 +00:00
data = BROWSERS[browser]["data"] + data,
[bazel] Mark remaining tests as being skipped for remote builds
2023-06-05 21:16:59 +01:00
env_inherit = inherited_env,
[bazel] Automated reformatting of build files
2020-05-14 17:30:31 +01:00
**stripped_args
[bazel] closure tests and regular selenium tests share a runner
2020-03-31 15:11:14 +01:00
)
Correctly generate test suites and all targets for java selenium tests
2022-07-05 15:26:50 +01:00
if browser == default_browser:
native.alias(
name = "%s-%s" % (name, browser),
actual = test,
)
all_tests.append(":%s" % test)
Re-enable remote tests for java
2020-07-21 18:35:28 +01:00
[java] Remote selenium-remote tag from test targets If it's there, then `bazel query "attr(tags, 'remote', tests(//java/...))` would also return non-remote targets. This happens because Bazel queries for partial match in attribute ("selenium-remote" contains "remote").
2023-05-02 08:16:23 -07:00
if remote:
[bazel] Bump contrib_rules_jvm to 0.19.0
2023-10-09 18:04:52 +01:00
junit5_test(
Re-enable remote tests for java
2020-07-21 18:35:28 +01:00
name = "%s-remote" % test,
test_class = test_class,
size = size,
[bazel] Use the new test suites for selenium test suites In the java tree, at least. This dramatically improves clean build time, with critical path times going from 825s to 263s on my machine. We still achieve good parallelism in the test execution times.
2020-11-30 13:30:00 +00:00
jvm_flags = BROWSERS[browser]["jvm_flags"] + jvm_flags + [
Re-enable remote tests for java
2020-07-21 18:35:28 +01:00
"-Dselenium.browser.remote=true",
],
[java] Not linting remote tests. [run java]
2022-06-23 13:51:40 +02:00
# No need to lint remote tests as the code for non-remote is the same and they get linted
[java] run all tests
2026-01-14 12:28:21 -06:00
tags = BROWSERS[browser]["tags"] + tags + ["remote", "%s-remote" % browser, "no-lint"],
Expose local browser drivers through bazel
2020-12-01 16:37:01 +00:00
data = BROWSERS[browser]["data"] + data + [
[java] Create new `io` maven artifact and make SeleniumManager use that for executing command lines
2023-08-01 17:54:46 +01:00
"@selenium//java/src/org/openqa/selenium/grid:selenium_server",
Re-enable remote tests for java
2020-07-21 18:35:28 +01:00
],
**stripped_args
)
Correctly generate test suites and all targets for java selenium tests
2022-07-05 15:26:50 +01:00
all_tests.append(":%s-remote" % test)
Re-enable remote tests for java
2020-07-21 18:35:28 +01:00
[bazel] Use the new test suites for selenium test suites In the java tree, at least. This dramatically improves clean build time, with critical path times going from 825s to 263s on my machine. We still achieve good parallelism in the test execution times.
2020-11-30 13:30:00 +00:00
# Handy way to run everything
Correctly generate test suites and all targets for java selenium tests
2022-07-05 15:26:50 +01:00
native.test_suite(name = "%s-all-browsers" % name, tests = all_tests, tags = tags + ["manual"])
Reference in New Issue Copy Permalink