Schema registry

Jasmine

jasmine JSON config file

jasmine.json

Validate

Check your file against this schema

Opens the validator with this schema already loaded. Paste your jasmine.json and it validates in your browser — nothing is uploaded.

Validate a jasmine.json → View raw schema

Reference

Fields

Generated directly from the schema, following local $refs, to two levels of nesting.

Field	Type	Description
`spec_dir`required	`string`	Spec directory path relative to the current working dir when jasmine is executed. default: `""`
`spec_files`required	`array<string>`	Array of filepaths (and globs) relative to spec_dir to include and exclude. default: `[]`
`helpers`	`array<string>`	Array of filepaths (and globs) relative to spec_dir to include before jasmine specs default: `[]`
`env`	`object`	Configuration of the Jasmine environment
`env.autoCleanClosure`	`boolean`	Clean closures when a suite is done running (done by clearing the stored function reference). This prevents memory leaks, but you won't be able to run jasmine multiple times. default: `false`
`env.failSpecWithNoExpectations`	`boolean`	Whether to fail the spec if it ran no expectations. By default a spec that ran no expectations is reported as passed. Setting this to true will report such spec as a failure. default: `false`
`env.hideDisbaled`	`boolean`	Whether or not reporters should hide disabled specs from their output. Currently only supported by Jasmine's HTMLReporter. default: `false`
`env.random`	`boolean`	Whether to randomize spec execution order. default: `true`
`env.seed`	`anyOf`	Seed to use as the basis of randomization. Null causes the seed to be determined randomly at the start of execution. default: `null`
`env.stopOnSpecFailure`	`boolean`	Whether to stop execution of the suite after the first spec failure. default: `false`
`env.stopSpecOnExpectationFailure`	`boolean`	Whether to cause specs to only have one expectation failure. default: `false`
`env.verboseDeprication`	`boolean`	Whether or not to issue warnings for certain deprecated functionality every time it's used. If not set or set to false, deprecation warnings for methods that tend to be called frequently will be issued only once or otherwise throttled to default: `false`
`autoCleanClosure`	`boolean`	Clean closures when a suite is done running (done by clearing the stored function reference). This prevents memory leaks, but you won't be able to run jasmine multiple times. default: `false`
`failSpecWithNoExpectations`	`boolean`	Whether to fail the spec if it ran no expectations. By default a spec that ran no expectations is reported as passed. Setting this to true will report such spec as a failure. default: `false`
`hideDisbaled`	`boolean`	Whether or not reporters should hide disabled specs from their output. Currently only supported by Jasmine's HTMLReporter. default: `false`
`random`	`boolean`	Whether to randomize spec execution order. default: `true`
`seed`	`anyOf`	Seed to use as the basis of randomization. Null causes the seed to be determined randomly at the start of execution. default: `null`
`stopOnSpecFailure`	`boolean`	Whether to stop execution of the suite after the first spec failure. default: `false`
`stopSpecOnExpectationFailure`	`boolean`	Whether to cause specs to only have one expectation failure. default: `false`
`verboseDeprication`	`boolean`	Whether or not to issue warnings for certain deprecated functionality every time it's used. If not set or set to false, deprecation warnings for methods that tend to be called frequently will be issued only once or otherwise throttled to default: `false`

Audit

What we found in this schema

Declared draft: draft-07
Validates cleanly against its own meta-schema.
12 properties, 92% carrying a description, max nesting depth 7.

Standards

Specification sections for the keywords in this schema

Keyword	Document	Section
`$id`	JSON Schema Core, draft 2020-12	§8.2.1 — The "$id" Keyword
`$ref`	JSON Schema Core, draft 2020-12	§8.2.3.1 — Direct References with "$ref"
`$schema`	JSON Schema Core, draft 2020-12	§8.1.1 — "$schema"
`allOf`	JSON Schema Core, draft 2020-12	§10.2.1.1 — "allOf"
`anyOf`	JSON Schema Core, draft 2020-12	§10.2.1.2 — "anyOf"
`default`	JSON Schema Validation, draft 2020-12	§9.2 — "default"
`description`	JSON Schema Validation, draft 2020-12	§9.1 — "title" and "description"
`items`	JSON Schema Core, draft 2020-12	§10.3.1.2 — "items"
`properties`	JSON Schema Core, draft 2020-12	§10.3.2.1 — "properties"
`required`	JSON Schema Validation, draft 2020-12	§6.5.3 — "required"
`type`	JSON Schema Validation, draft 2020-12	§6.1.1 — "type"

Documents

JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.

Source

Attribution

This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.

← All schemas