Security News
Fluent Assertions Faces Backlash After Abandoning Open Source Licensing
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
@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.
Detailed XML test results are found in the standard bazel-testlogs
directory. This may be symlinked in your workspace.
See https://docs.bazel.build/versions/master/output_directories.html
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)
name
Name of the resulting label
srcs
JavaScript source files containing Jasmine specs
Defaults to []
data
Runtime dependencies which will be loaded while the test executes
Defaults to []
deps
Other targets which produce JavaScript, such as ts_library
Defaults to []
expected_exit_code
The expected exit code for the test.
Defaults to 0
tags
Bazel 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
coverage
Enables code coverage collection and reporting.
Defaults to False
jasmine
A label providing the @bazel/jasmine
npm dependency.
Defaults to "@npm//@bazel/jasmine"
jasmine_entry_point
A label providing the @bazel/jasmine
entry point.
Defaults to "@npm//:node_modules/@bazel/jasmine/jasmine_runner.js"
kwargs
Remaining arguments are passed to the test rule
1.6.0 (2020-04-11)
execroot/my_wksp/node_modules
even when running in runfiles (#1805) (5c2f6c1)yarn_urls
should be string_list
, not string
(3357c08)FAQs
Run Jasmine tests under Bazel
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
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.