---
title: Jasmine
layout: default
stylesheet: docs
---
<!-- *********************
 DO NOT EDIT THIS FILE
  It is a generated build output from Stardoc.
  Instead you must edit the .bzl file where the rules are declared,
  or possibly a markdown file next to the .bzl file
 ********************* -->
# Jasmine rules for Bazel

The Jasmine rules run tests under the Jasmine framework with Bazel.


## Installation

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`.

[name]: https://bazel.build/docs/build-ref.html#name
[label]: https://bazel.build/docs/build-ref.html#labels
[labels]: https://bazel.build/docs/build-ref.html#labels


## jasmine_node_test

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`.


### Usage

```
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