DefinitelyTyped icon, indicating that this package has TypeScript declarations provided by the separate @types/jest-json-schema package

6.1.0 • Public • Published


npm version Build Status Mentioned in Awesome Jest

JSON schema matcher for jest

Want to get paid for your contributions to jest-json-schema? Send your resume to

Matchers included


Validates that an object matches the given JSON schema

it('validates my json', () => {
  const schema = {
    properties: {
      hello: { type: 'string' },
    required: ['hello'],
  expect({ hello: 'world' }).toMatchSchema(schema);


$ npm install --save-dev jest-json-schema


In any test file:

import { matchers } from 'jest-json-schema';

Or if you want it available for all test files then set it up the same way in a test framework script file

You can pass Ajv options using matchersWithOptions and passing it your options object. The only option passed by default is allErrors: true.

import { matchersWithOptions } from 'jest-json-schema';

const formats = {
  bcp47: /^[a-z]{2}-[A-Z]{2}$/,

expect.extend(matchersWithOptions({ formats }));

Additionally you can also use a callback to further configure and extend the Ajv instance used by the matchers:

import ajvKeywords from 'ajv-keywords';
import { matchersWithOptions } from 'jest-json-schema';

const formats = {
  bcp47: /^[a-z]{2}-[A-Z]{2}$/,

expect.extend(matchersWithOptions({ formats }, (ajv) => {
  // This uses the `ajv-keywords` library to add pre-made
  // custom keywords to the Ajv instance.
  ajvKeywords(ajv, ['typeof', 'instanceof']);

You can also customize the Ajv class with the AjvClass option:

import Ajv2020 from 'ajv/dist/2020'
import { matchersWithOptions } from 'jest-json-schema';

expect.extend(matchersWithOptions({ AjvClass: Ajv2020 }));

Verbose errors

Ajv supports a verbose option flag which enables more information about individual errors. This extra information can mean that we can output to Jest more meaningful errors that can help the development process:

const { matchersWithOptions } = require('jest-json-schema');

  verbose: true

test('check that property errors are outputted', () => {
  const schema = {
    $id: 'testSchema',
    type: 'object',
    properties: {
      name: {
        type: 'string',
      dob: {
        type: 'string',
        format: 'date',

  const invalidData = {
    name: null,
    dob: '02-29-2000',

  expect(() => {

  .name should be string
    Received: <null>
    Path: testSchema#/properties/name/type
  .dob should match format \\"date\\"
    Received: <string> 02-29-2000
    Path: testSchema#/properties/dob/format

Example using multiple schema files

If you organise your schemas into separate files and use refs which point to the various different schemas, it will be important to include those dependent schema files when extending Jest's expect handler, using the matchersWithOptions interface:


  "$id": "schemaA",
  "$schema": "",
  "description": "Example of a definition schema.",
  "definitions": {
    "testA": {
      "type": "number",
      "const": 1
    "testB": {
      "type": ["null", "string"]


  "$id": "schemaB",
  "$schema": "",
  "description": "Example of a schema that references another schema.",
  "$ref": "schemaA#/definitions/testB"


const { matchersWithOptions } = require('jest-json-schema');

// Local schema files are imported like normal. If you use TypeScript you
// will need to ensure `--resolveJsonModule` is enabled.
const schemaA = require('./schemaA.json');
const schemaB = require('./schemaB.json');

  // Loading in a schema which is comprised only of definitions,
  // which means specific test schemas need to be created.
  // This is good for testing specific conditions for definition schemas.
  schemas: [schemaA]

test('schemaA is valid', () => {

test('using schemaA to build a test schema to test a specific definition', () => {
  // This is a test schema which references a definition in one of the
  // pre-loaded schemas. This can allow us to write tests for specific
  // definitions.
  const testSchema = {
    $ref: 'schemaA#/definitions/testA'


  // Valid

  // This example runs through a number of values that we know don't match
  // the schema, ensuring that any future changes to the schema will require
  // the test to be updated.
  ['1', true, false, null, [], {}].forEach(value => {

test('using schemaB which already references a definition in schemaA', () => {

  // Valid
  ['', '1', null].forEach(value => {

  // Invalid
  ['1', true, false, [], {}].forEach(value => {

TypeScript support

If you would like to use jest-json-schema library in your TypeScript project, remember to install type definitions from @types/jest-json-schema package.

npm install --save-dev @types/jest-json-schema

Or if yarn is your package manager of choice:

yarn add @types/jest-json-schema --dev


We welcome Your interest in the American Express Open Source Community on Github. Any Contributor to any Open Source Project managed by the American Express Open Source Community must accept and sign an Agreement indicating agreement to the terms below. Except for the rights granted in this Agreement to American Express and to recipients of software distributed by American Express, You reserve all right, title, and interest, if any, in and to Your Contributions. Please fill out the Agreement.

Please feel free to open pull requests and see to learn how to get started contributing.


Any contributions made under this project will be governed by the Apache License 2.0.

Code of Conduct

This project adheres to the American Express Community Guidelines. By participating, you are expected to honor these guidelines.

Package Sidebar


npm i jest-json-schema

Weekly Downloads






Unpacked Size

47.3 kB

Total Files


Last publish


  • pixnbits
  • anescobar1991
  • jsmartfo
  • amexopensource
  • 10xlacroixdrinker