@bazel/protractor
Advanced tools
WARNING: this is beta-quality software. Breaking changes are likely. Not recommended for production use without expert support.
The Protractor rules run tests under the Protractor framework with Bazel.
Add the @bazel/protractor npm package to your devDependencies in package.json.
Your WORKSPACE should declare a yarn_install or npm_install rule named npm.
It should then install the rules found in the npm packages using the `install_bazel_dependencies' function.
See https://github.com/bazelbuild/rules_nodejs/#quickstart
This causes the @bazel/protractor package to be installed as a Bazel workspace named npm_bazel_protractor.
Runs a protractor test in a browser.
protractor_web_test(name, configuration, on_prepare, srcs, deps, data, server, tags, peer_deps, protractor_entry_point, kwargs)
nameThe name of the test
configurationProtractor configuration file.
Defaults to None
on_prepareA file with a node.js script to run once before all tests run. If the script exports a function which returns a promise, protractor will wait for the promise to resolve before beginning tests.
Defaults to None
srcsJavaScript source files
Defaults to []
depsOther targets which produce JavaScript such as ts_library
Defaults to []
dataRuntime dependencies
Defaults to []
serverOptional server executable target
Defaults to None
tagsStandard Bazel tags, this macro adds one for ibazel
Defaults to []
peer_depsList of peer npm deps required by protractor_web_test.
Defaults to ["@npm//@bazel/protractor", "@npm//protractor"]
protractor_entry_pointA label providing the @npm//protractor entry point.
Default to @npm//:node_modules/protractor/bin/protractor.
Defaults to "@npm//:node_modules/protractor/bin/protractor"
kwargspassed through to protractor_web_test
Defines a test_suite of web_test targets that wrap a protractor_web_test target.
protractor_web_test_suite(name, browsers, web_test_data, wrapped_test_tags, kwargs)
nameThe base name of the test
browsersA sequence of labels specifying the browsers to use.
Defaults to None
web_test_dataData dependencies for the wrapoer web_test targets.
Defaults to []
wrapped_test_tagsA list of test tag strings to use for the wrapped karma_web_test target.
Defaults to ["manual", "noci"]
kwargsArguments for the wrapped karma_web_test target.
0.42.1 (2019-11-27)
To upgrade:
http_archive(
name = "build_bazel_rules_nodejs",
sha256 = "c612d6b76eaa17540e8b8c806e02701ed38891460f9ba3303f4424615437887a",
urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/0.42.1/rules_nodejs-0.42.1.tar.gz"],
)
and run yarn upgrade --scope @bazel to update all your @bazel-scoped npm packages to the latest versions.
(or manually do the npm equivalent - they don't have a way to update a scope)
In 0.41.0 we noted that a feature for inserting <script> and <link> tags was dropped from ts_devserver and pkg_web but the replacement wasn't available. Now it is thanks to @jbedard who published a standalone npm package html-insert-assets. You can see how it's wired in the examples.
If you waited to upgrade before, now you should.
npm_package_bin and all rules generated by it, to match genrule behavior as documented at https://docs.bazel.build/versions/master/be/make-variables.html#predefined_genrule_variables
This means that usage of the $@ shortcut to refer to the output directory should now be $(@D) when output_dir=True
and you can now use $@ to refer to the location of a single outputFAQs
Run Protractor tests under Bazel
The npm package @bazel/protractor receives a total of 11,881 weekly downloads. As such, @bazel/protractor popularity was classified as popular.
We found that @bazel/protractor demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.