@bazel/jasmine
Advanced tools
The Jasmine rules run tests under the Jasmine framework with Bazel.
Add the @bazel/jasmine 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.
This causes the @bazel/jasmine package to be installed as a Bazel workspace named npm_bazel_jasmine.
Runs tests in NodeJS using the Jasmine test runner.
To debug the test, see debugging notes in nodejs_test.
jasmine_node_test(name, srcs, data, deps, expected_exit_code, tags, config_file, coverage, jasmine, jasmine_entry_point, kwargs)
nameName of the resulting label
srcsJavaScript source files containing Jasmine specs
Defaults to []
dataRuntime dependencies which will be loaded while the test executes
Defaults to []
depsOther targets which produce JavaScript, such as ts_library
Defaults to []
expected_exit_codeThe expected exit code for the test.
Defaults to 0
tagsBazel tags applied to test
Defaults to []
config_file(experimental) label of a file containing Jasmine JSON config.
Note that not all configuration options are honored, and we expect some strange feature interations. For example, the filter for which files are instrumented for code coverage doesn't understand the spec_files setting in the config.
See https://jasmine.github.io/setup/nodejs.html#configuration
Defaults to None
coverageEnables code coverage collection and reporting.
Defaults to False
jasmineA label providing the @bazel/jasmine npm dependency.
Defaults to "@npm//@bazel/jasmine"
jasmine_entry_pointA label providing the @bazel/jasmine entry point.
Defaults to "@npm//:node_modules/@bazel/jasmine/jasmine_runner.js"
kwargsRemaining arguments are passed to the test rule
1.0.0 (2019-12-20)
bootstrap attribute & fix $(location) expansions in nodejs_binary templated_args (1860a6a)args to yarn_install & npm_install (#1462) (d245d09)templated_args_file removed from nodejs_binary, nodejs_test & jasmine_node_test. This was a separation of concerns and complicated node.bzl more than necessary while also being rigid in how the params file is formatted. It is more flexible to expose this functionality as another simple rule named params_file.To match standard $(location) and $(locations) expansion, params_file args location expansions are also in the standard short_path form (this differs from the old templated_args behavior which was not Bazel idiomatic) Usage example:
load("@build_bazel_rules_nodejs//:index.bzl", "params_file", "nodejs_binary")
params_file(
name = "params_file",
args = [
"--some_param",
"$(location //path/to/some:file)",
"--some_other_param",
"$(location //path/to/some/other:file)",
],
data = [
"//path/to/some:file",
"//path/to/some/other:file",
],
)
nodejs_binary(
name = "my_binary",
data = [":params_file"],
entry_point = ":my_binary.js",
templated_args = ["$(location :params_file)"],
)
This can be replaced with the --node_options=--require=$(location label) argument such as,
nodejs_test(
name = "bootstrap_test",
templated_args = ["--node_options=--require=$(rlocation $(location :bootstrap.js))"],
entry_point = ":bootstrap.spec.js",
data = ["bootstrap.js"],
)
or
jasmine_node_test(
name = "bootstrap_test",
srcs = ["bootstrap.spec.js"],
templated_args = ["--node_options=--require=$(rlocation $(location :bootstrap.js))"],
data = ["bootstrap.js"],
)
templated_args $(location) and $(locations) are now correctly expanded when there is no space before $(location
such as templated_args = ["--node_options=--require=$(rlocation $(location :bootstrap.js))"].
Path is returned in runfiles manifest path format such as repo/path/to/file. This differs from how $(location)
and $(locations) expansion behaves in expansion the args attribute of a *_binary or *_test which returns
the runfiles short path of the format ./path/to/file for user repo and ../external_repo/path/to/file for external
repositories. We may change this behavior in the future with $(mlocation) and $(mlocations) used to expand
to the runfiles manifest path.
See https://docs.bazel.build/versions/master/be/common-definitions.html#common-attributes-binaries.
args in yarn_install and npm_install can be used to pass arbitrary arguments so we removed the following attributes:npm_package renamed to pkg_npm. This is to match the naming convention for package rules https://docs.bazel.build/versions/master/be/pkg.html.FAQs
Run Jasmine tests under Bazel
The npm package @bazel/jasmine receives a total of 17,854 weekly downloads. As such, @bazel/jasmine popularity was classified as popular.
We found that @bazel/jasmine 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.