JsonUnit

JsonUnit is a library that simplifies JSON comparison in tests.

• APIs
  • AssertJ integration
  • Hamcrest matchers
  • Spring MVC assertions
  • Spring WebTestClient
  • Spring REST client assertions
  • Vintage APIs
• Features
  • JsonPath support
  • Ignoring values
  • Ignoring elements
  • Ignoring paths
  • Regular expressions
  • Type placeholders
  • Custom matchers
  • Options
  • Array indexing
  • Numerical comparison
  • Escaping dots
  • Lenient parsing of expected value
  • Jackson Object Mapper customization
• Release notes

APIs

There are several different APIs you can use. They all have more or less the same features, just the usage is slightly different.

AssertJ integration

The recommended API is AssertJ integration which combines the power of JsonUnit and AssertJ.

import static net.javacrumbs.jsonunit.assertj.JsonAssertions.assertThatJson;
import static net.javacrumbs.jsonunit.assertj.JsonAssertions.json;

...

// compares two JSON documents (note lenient parsing of expected value)
assertThatJson("{\"a\":1, \"b\":2}").isEqualTo("{b:2, a:1}");

// objects are automatically serialized before comparison
assertThatJson(jsonObject).isEqualTo("{\n\"test\": 1\n}");

// AssertJ map assertions (numbers are converted to BigDecimals)
assertThatJson("{\"a\":1}").isObject().containsEntry("a", BigDecimal.valueOf(1));

// Type placeholders
assertThatJson("{\"a\":1, \"b\": {\"c\" :3}}")
    .isObject().containsValue(json("{\"c\" :\"${json-unit.any-number}\"}"));

// AssertJ string assertion
assertThatJson("{\"a\": \"value\"")
    .node("a").isString().isEqualTo("value");

// AssertJ array assertion
assertThatJson("{\"a\":[{\"b\": 1}, {\"c\": 1}, {\"d\": 1}]}")
    .node("a").isArray().contains(json("{\"c\": 1}"));

// Can ignore array order
assertThatJson("{\"a\":[{\"b\": 1}, {\"c\": 1}, {\"d\": 1}]}")
    .when(Option.IGNORING_ARRAY_ORDER).node("a").isArray()
    .isEqualTo(json("[{\"c\": 1}, {\"b\": 1} ,{\"d\": 1}]"));

// custom matcher
assertThatJson("{\"test\":-1}")
    .withConfiguration(c -> c.withMatcher("positive", greaterThan(valueOf(0))))
    .isEqualTo("{\"test\": \"${json-unit.matches:positive}\"}");

// and
assertThatJson("{\"test\":{\"a\":1, \"b\":2, \"c\":3}}").and(
    a -> a.node("test.a").isEqualTo(1),
    a -> a.node("test.b").isEqualTo(2)
);

// JsonPath support
assertThatJson(json)
    .inPath("$.store.book")
    .isArray()
    .contains(json(
        "            {\n" +
            "                \"category\": \"reference\",\n" +
            "                \"author\": \"Nigel Rees\",\n" +
            "                \"title\": \"Sayings of the Century\",\n" +
            "                \"price\": 8.96\n" +
            "            }"
    ));

JsonUnit tries to be clever when parsing the expected value. If the value can be parsed as valid JSON, it's parsed so. If it can't be parsed, it's considered to be just a string to be compared. It usually works, but it can lead to unexpected situations, usually with primitive values like numbers and booleans.

// This test does NOT pass. "1" is parsed as JSON containing number 1, the actual value is a string.
assertThatJson("{\"id\":\"1\", \"children\":[{\"parentId\":\"1\"}]}")
    .inPath("children[*].parentId")
    .isArray()
    .containsOnly("1");

// You have to wrap the expected value by `JsonAssertions.value()`
// to prevent parsing
assertThatJson("{\"id\":\"1\", \"children\":[{\"parentId\":\"1\"}]}")
    .inPath("children[*].parentId")
    .isArray()
    .containsOnly(value("1"));

// "true" is valid JSON so it gets parsed to primitive `true`
// Have to wrap it to JsonAssertions.value() in order to make sure it's not parsed
assertThatJson("{\"root\":[\"true\"]}").node("root").isArray().containsExactly(value("true"));

On the other hand, if you want to make sure that the expected value is parsed as JSON, use JsonAssertions.json().

Kotlin support

Following Kotlin API is supported (notice different import)

// Kotlin
import net.javacrumbs.jsonunit.assertj.assertThatJson

assertThatJson("""{"root":{"a":1, "b": 2}}""") {
    isObject
    node("root.a").isEqualTo(1)
    node("root.b").isEqualTo(2)
}

To use AssertJ integration, import

<dependency>
    <groupId>net.javacrumbs.json-unit</groupId>
    <artifactId>json-unit-assertj</artifactId>
    <version>3.0.0</version>
    <scope>test</scope>
</dependency>

For more examples see the tests.

Hamcrests matchers

You use Hamcrest matchers in the following way

import static net.javacrumbs.jsonunit.JsonMatchers.*;
import static org.junit.Assert.*;
import static net.javacrumbs.jsonunit.core.util.ResourceUtils.resource;
...

assertThat("{\"test\":1}", jsonEquals("{\"test\": 1}"));
assertThat("{\"test\":1}", jsonPartEquals("test", 1));
assertThat("{\"test\":[1, 2, 3]}", jsonPartEquals("test[0]", 1));

assertThat("{\"test\":{\"a\":1, \"b\":2, \"c\":3}}",
    jsonEquals("{\"test\":{\"b\":2}}").when(IGNORING_EXTRA_FIELDS));

// Can use other Hamcrest matchers too
assertThat("{\"test\":1}", jsonPartMatches("test", is(valueOf(1))))

assertThat("{\"test\":1}", jsonEquals(resource("test.json")));

To use import

<dependency>
    <groupId>net.javacrumbs.json-unit</groupId>
    <artifactId>json-unit</artifactId>
    <version>3.0.0</version>
    <scope>test</scope>
</dependency>

For more examples see the tests.

Spring MVC assertions

JsonUnit supports Spring MVC test assertions. For example

import static net.javacrumbs.jsonunit.spring.JsonUnitResultMatchers.json;
...

mockMvc.perform(get("/sample").andExpect(
    json().isEqualTo("{\"result\":{\"string\":\"stringValue\", \"array\":[1, 2, 3],\"decimal\":1.00001}}")
);
mockMvc.perform(get("/sample").andExpect(
    json().node("result.string2").isAbsent()
);
mockMvc.perform(get("/sample").andExpect(
    json().node("result.array").when(Option.IGNORING_ARRAY_ORDER).isEqualTo(new int[]{3, 2, 1})
);
mockMvc.perform(get("/sample").andExpect(
    json().node("result.array").matches(everyItem(lessThanOrEqualTo(valueOf(4))))
);

Following Kotlin DSL is supported:

mockMvc.get(path).andExpect {
    jsonContent {
        node("root").isEqualTo(CORRECT_JSON)
    }
}

Inside jsonContent you have access to all AssertJ API capabilities as described here.

To use import

<dependency>
    <groupId>net.javacrumbs.json-unit</groupId>
    <artifactId>json-unit-spring</artifactId>
    <version>3.0.0</version>
    <scope>test</scope>
</dependency>

For more examples see the tests.

Spring WebTestClient

To integrate with Spring WebTest client do

import static net.javacrumbs.jsonunit.spring.WebTestClientJsonMatcher.json;
...

client.get().uri(path).exchange().expectBody().consumeWith(
    json().isEqualTo("{\"result\":{\"string\":\"stringValue\", \"array\":[1, 2, 3],\"decimal\":1.00001}}")
);
client.get().uri(path).exchange().expectBody().consumeWith(
    json().node("result.string2").isAbsent()
);
client.get().uri(path).exchange().expectBody().consumeWith(
    json().node("result.array").when(Option.IGNORING_ARRAY_ORDER).isEqualTo(new int[]{3, 2, 1})
);
client.get().uri(path).exchange().expectBody().consumeWith(
    json().node("result.array").matches(everyItem(lessThanOrEqualTo(valueOf(4))))
);

For Kotlin, you can use our bespoke DSL

import net.javacrumbs.jsonunit.spring.jsonContent
...
client.get().uri(path).exchange().expectBody()
    .jsonContent {
        isEqualTo(CORRECT_JSON)
    }

Import

<dependency>
    <groupId>net.javacrumbs.json-unit</groupId>
    <artifactId>json-unit-spring</artifactId>
    <version>3.0.0</version>
    <scope>test</scope>
</dependency>

For more examples see the tests.

Spring REST client assertions

import static net.javacrumbs.jsonunit.spring.JsonUnitRequestMatchers.json;
...
mockServer.expect(requestTo(URI))
      .andExpect(json().isEqualTo(json))
      .andRespond(withSuccess(jsonResponse, MediaType.APPLICATION_JSON_UTF8));

To use import

<dependency>
    <groupId>net.javacrumbs.json-unit</groupId>
    <artifactId>json-unit-spring</artifactId>
    <version>3.0.0</version>
    <scope>test</scope>
</dependency>

For more examples see the tests.

Features

JsonUnit support all this features regardless of API you use.

JsonPath support

You can use JsonPath navigation together with JsonUnit. It has native support in AssertJ integration so you can do something like this:

// AssertJ style
assertThatJson(json)
    .inPath("$.store.book")
    .isArray()
    .contains(json(
        "            {\n" +
            "                \"category\": \"reference\",\n" +
            "                \"author\": \"Nigel Rees\",\n" +
            "                \"title\": \"Sayings of the Century\",\n" +
            "                \"price\": 8.96\n" +
            "            }"
    ));

For the other API styles you have to first import JsonPath support module

<dependency>
    <groupId>net.javacrumbs.json-unit</groupId>
    <artifactId>json-unit-json-path</artifactId>
    <version>3.0.0</version>
    <scope>test</scope>
</dependency>

and then use instead of actual value

import static net.javacrumbs.jsonunit.jsonpath.JsonPathAdapter.inPath;

...
// Fluent assertions
assertThatJson(inPath(json, "$.store.book[*].author"))
    .when(Option.IGNORING_ARRAY_ORDER)
    .isEqualTo("['J. R. R. Tolkien', 'Nigel Rees', 'Evelyn Waugh', 'Herman Melville']");

Ignoring values

Sometimes you need to ignore certain values when comparing. It is possible to use ${json-unit.ignore} or #{json-unit.ignore} placeholder like this

// AssertJ API
assertThatJson("{\"a\":1}")
    .isEqualTo(json("{\"a\":\"${json-unit.ignore}\"}"));

Please note that the assertion will fail if the test element is missing in the actual value.

Ignoring elements

If the element needs to be ignored completely you can use ${json-unit.ignore-element} placeholder.

// AssertJ API
assertThatJson("{\"root\":{\"test\":1, \"ignored\": null}}")
      .isEqualTo("{\"root\":{\"test\":1, \"ignored\": \"${json-unit.ignore-element}\"}}");

The assertion will not fail if the element is missing in the actual value.

Ignoring paths

whenIgnoringPaths configuration option makes JsonUnit ignore the specified paths in the actual value. If the path matches, it's completely ignored. It may be missing, null or have any value. Also when(paths(...), thenIgnore() can be used.

// AssertJ style
assertThatJson("{\"root\":{\"test\":1, \"ignored\": 1}}")
    .whenIgnoringPaths("root.ignored"))
    .isEqualTo("{\"root\":{\"test\":1}}");

// Hamcrest matcher
assertThat(
  "{\"root\":{\"test\":1, \"ignored\": 2}}",
  jsonEquals("{\"root\":{\"test\":1, \"ignored\": 1}}").whenIgnoringPaths("root.ignored")
);

Array index placeholder

assertThatJson("[{\"a\":1, \"b\":2},{\"a\":1, \"b\":3}]")
    .whenIgnoringPaths("[*].b")
    .isEqualTo("[{\"a\":1, \"b\":0},{\"a\":1, \"b\":0}]");

Please note that if you use JsonPath, you should start the path to be ignored by $ Also note that whenIgnoringPaths method supports full JsonPath syntax only in AssertJ API, all the other flavors support only exact path or array index placeholder as described above.

JsonPath with whenIgnoringPaths example:

// AssertJ API
assertThatJson("{\"fields\":[" +
        "{\"key\":1, \"name\":\"AA\"}," +
        "{\"key\":2, \"name\":\"AB\"}," +
        "{\"key\":3, \"name\":\"AC\"}" +
    "]}")
    .whenIgnoringPaths("$.fields[?(@.name=='AA')].key")
    .isEqualTo("{\"fields\":[" +
        "{\"key\":2, \"name\":\"AA\"}," +
        "{\"key\":2, \"name\":\"AB\"}," +
        "{\"key\":3, \"name\":\"AC\"}" +
    "]}");

Regular expressions

It is also possible to use regular expressions to compare string values

assertThatJson("{\"test\": \"ABCD\"}")
    .isEqualTo("{\"test\": \"${json-unit.regex}[A-Z]+\"}");

For matching just part of the string, you can use this (we have to escape twice, once for Java, once for JSON)

assertThatJson("{\"test\": \"This is some text followed by: ABCD, followed by this\"}")
            .isEqualTo("{\"test\": \"${json-unit.regex}^\\\\QThis is some text followed by: \\\\E[A-Z]+\\\\Q, followed by this\\\\E$\"}");

Since this is quite hard to write, you can implement an expression builder like this.

Type placeholders

If you want to assert just a type, but you do not care about the exact value, you can use any-* placeholder like this

assertThatJson("{\"test\":\"value\"}")
    .isEqualTo("{test:'${json-unit.any-string}'}");

assertThatJson("{\"test\":true}")
    .isEqualTo("{\"test\":\"${json-unit.any-boolean}\"}");

assertThatJson("{\"test\":1.1}")
    .isEqualTo("{\"test\":\"${json-unit.any-number}\"}");

You can also use hash instead of string #{json-unit.any-string} for example if you are using language with string interpolation like Kotlin.

Custom matchers

In some special cases you might want to use your own matcher in the expected document.

 assertThatJson("{\"test\":-1}")
             .withMatcher("positive", greaterThan(valueOf(0)))
             .isEqualTo("{\"test\": \"${json-unit.matches:positive}\"}");

In even more special cases, you might want to parametrize your matcher.

 Matcher<?> divisionMatcher = new DivisionMatcher();
 assertThatJson("{\"test\":5}")
    .withMatcher("isDivisibleBy", divisionMatcher)
    .isEqualTo("{\"test\": \"${json-unit.matches:isDivisibleBy}3\"}");

 private static class DivisionMatcher extends BaseMatcher<Object> implements ParametrizedMatcher {
     private BigDecimal param;

     public boolean matches(Object item) {
         return ((BigDecimal)item).remainder(param).compareTo(ZERO) == 0;
     }

     public void describeTo(Description description) {
         description.appendValue(param);
     }

     @Override
     public void describeMismatch(Object item, Description description) {
         description.appendText("It is not divisible by ").appendValue(param);
     }

     public void setParameter(String parameter) {
         this.param = new BigDecimal(parameter);
     }
 }

If you need a matcher with more than one parameter, you can implement it like this.

Options

There are multiple options how you can configure the comparison

TREATING_NULL_AS_ABSENT - fields with null values are equivalent to absent fields. For example, this test passes

assertThatJson("{\"test\":{\"a\":1, \"b\": null}}")
    .when(TREATING_NULL_AS_ABSENT)
    .isEqualTo("{\"test\":{\"a\":1}}");

IGNORING_ARRAY_ORDER - ignores order in arrays

assertThatJson("{\"test\":[1,2,3]}")
    .when(IGNORING_ARRAY_ORDER)
    .isEqualTo("{\"test\":[3,2,1]}");

IGNORING_EXTRA_ARRAY_ITEMS - ignores unexpected array items

assertThatJson("{\"test\":[1,2,3,4]}")
    .when(IGNORING_EXTRA_ARRAY_ITEMS)
    .isEqualTo("{\"test\":[1,2,3]}");


assertThatJson("{\"test\":[5,5,4,4,3,3,2,2,1,1]}")
    .when(IGNORING_EXTRA_ARRAY_ITEMS, IGNORING_ARRAY_ORDER)
    .isEqualTo("{\"test\":[1,2,3]}");

IGNORING_EXTRA_FIELDS - ignores extra fields in the compared value

assertThatJson("{\"test\":{\"a\":1, \"b\":2, \"c\":3}}")
    .when(IGNORING_EXTRA_FIELDS)
    .isEqualTo("{\"test\":{\"b\":2}}");

IGNORE_VALUES - ignores values and compares only types

assertThatJson("{\"a\":2,\"b\":\"string2\"}")
    .when(paths("a", "b"), then(IGNORING_VALUES))
    .isEqualTo("{\"a\":1,\"b\":\"string\"}");

It is possible to combine options.

assertThatJson("{\"test\":[{\"key\":3},{\"key\":2, \"extraField\":2},{\"key\":1}]}")
    .when(IGNORING_EXTRA_FIELDS, IGNORING_ARRAY_ORDER)
    .isEqualTo("{\"test\":[{\"key\":1},{\"key\":2},{\"key\":3}]}");

In Hamcrest assertion you can set the option like this

assertThat("{\"test\":{\"a\":1, \"b\":2, \"c\":3}}",
    jsonEquals("{\"test\":{\"b\":2}}").when(IGNORING_EXTRA_FIELDS));

You can define options locally (for specific paths) by using when(path(...), then(...)):

// ignore array order for [*].a
// AssertJ
assertThatJson("{\"test\":{\"a\":1,\"b\":2,\"c\":3}}").when(paths("test.c"), then(IGNORING_VALUES))
    .isEqualTo("{\"test\":{\"a\":1,\"b\":2,\"c\":4}}");
// ignore array order everywhere but [*].b
assertThatJson("[{\"b\":[4,5,6]},{\"b\":[1,2,3]}]")
    .when(IGNORING_ARRAY_ORDER)
    .when(path("[*].b"), thenNot(IGNORING_ARRAY_ORDER))
    .isEqualTo("[{\"b\":[1,2,3]},{\"b\":[4,5,6]}]");
// ignore extra fields in the object "a"
assertThatJson("{\"a\":{\"a1\":1,\"a2\":2},\"b\":{\"b1\":1,\"b2\":2}}")
    .when(path("a"), then(IGNORING_EXTRA_FIELDS))
    .isEqualTo("{\"a\":{\"a1\":1},\"b\":{\"b1\":1}}"))
// ignore extra array items in the array
assertThatJson("{\"a\":[1,2,3]}")
    .when(path("a"), then(IGNORING_EXTRA_ARRAY_ITEMS))
    .isEqualTo("{\"a\":[1,2]}");
// Hamcrest
assertThat("{\"test\":{\"a\":1,\"b\":2,\"c\":3}}",
    jsonEquals("{\"test\":{\"a\":1,\"b\":2,\"c\":4}}").when(path("test.c"), then(IGNORING_VALUES)));

Note that TREATING_NULL_AS_ABSENT and IGNORING_VALUES require exact paths to ignored fields:

// ignoring number and str
assertThatJson("{\"a\":2,\"b\":\"string2\"}")
    .when(paths("a", "b"), then(IGNORING_VALUES))
    .isEqualTo("{\"a\":1,\"b\":\"string\"}");
// treat null B as absent B
assertThatJson("{\"A\":1,\"B\":null}")
    .when(path("B"), then(TREATING_NULL_AS_ABSENT))
    .isEqualTo("{\"A\":1}");

All other options require paths to objects or arrays where values or order should be ignored.

Array indexing

You can use negative numbers to index arrays form the end

assertThatJson("{\"root\":{\"test\":[1,2,3]}}")
    .node("root.test[-1]").isEqualTo(3);

Numerical comparison

Numbers are by default compared in the following way:

• If the type differs, the number is different. So 1 and 1.0 are different (int vs. float). This does not apply when Moshi is used since it parses all numbers as Doubles.
• Floating number comparison is exact, down to the scale - 1.0 and 1.00 are considered to be different.

You can change this behavior by setting tolerance. If you set tolerance to 0 two numbers are considered equal if they are equal mathematically even though they have different type or precision (a.compareTo(b) == 0)).

assertThatJson("{\"test\":1.00}").node("test").withTolerance(0).isEqualTo(1);

If you set tolerance to non-zero value, the values are considered equal if abs(a-b) < tolerance.

assertThatJson("{\"test\":1.00001}").node("test").withTolerance(0.001).isEqualTo(1);

Or you can use Hamcrest matcher

import static java.math.BigDecimal.valueOf;
...
assertThatJson("{\"test\":1.10001}").node("test")
    .matches(closeTo(valueOf(1.1), valueOf(0.001)));

If you are interested why 1 and 1.0 are treated as different numbers please read this comment.

If you want to have special handling of numerical values, you can inject your own number comparator.

assertThatJson("{\"a\":1.0}")
    .withConfiguration(c -> c.withNumberComparator(numberComparator))
    .isEqualTo("{\"a\":1.00}");

Escaping dots

Sometimes you have dots in JSON element names, and you need to address those elements. It is possible to escape dots like this

assertThatJson("{\"name.with.dot\": \"value\"}").node("name\\.with\\.dot").isStringEqualTo("value");

Lenient parsing of expected value

Writing JSON string in Java is huge pain. JsonUnit parses expected values leniently, so you do not have to quote keys, and you can use single quotes instead of double quotes. Please note that the actual value being compared is parsed in strict mode.

assertThatJson("{\"a\":\"1\", \"b\":2}").isEqualTo("{b:2, a:'1'}");

Jackson Object Mapper customization

If you need to customize Jackson 2 Object Mapper, you can do using SPI. Implement net.javacrumbs.jsonunit.providers.Jackson2ObjectMapperProvider.

public class Java8ObjectMapperProvider implements Jackson2ObjectMapperProvider {
    private final ObjectMapper mapper;

    private final ObjectMapper lenientMapper;


    public Java8ObjectMapperProvider() {
        mapper = new ObjectMapper().registerModule(new JavaTimeModule());
        mapper.configure(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS, false);

        lenientMapper = new ObjectMapper().registerModule(new JavaTimeModule());
        lenientMapper.configure(JsonParser.Feature.ALLOW_UNQUOTED_FIELD_NAMES, true);
        lenientMapper.configure(JsonParser.Feature.ALLOW_COMMENTS, true);
        lenientMapper.configure(JsonParser.Feature.ALLOW_SINGLE_QUOTES, true);
    }

    @Override
    public ObjectMapper getObjectMapper(boolean lenient) {
        return lenient ? lenientMapper : mapper;
    }
}

and register it in META-INF/services/net.javacrumbs.jsonunit.providers.Jackson2ObjectMapperProvider. See this example.

Logging

Although the differences are printed out by the assert statement, sometimes you use JsonUnit with other libraries like Jadler that do not print the differences between documents. In such case, you can switch on the logging. JsonUnit uses SLF4J. The only thing you need to do is to configure your logging framework to log net.javacrumbs.jsonunit.difference on DEBUG level.

Selecting underlying library

JsonUnit is trying to cleverly match which JSON library to use. In case you need to change the default behavior, you can use json-unit.libraries system property. For example -Djson-unit.libraries=jackson2,gson or System.setProperty("json-unit.libraries", "jackson2");. Supported values are gson, json.org, moshi, jackson2

Licence

JsonUnit is licensed under Apache 2.0 licence.

Release notes

3.0.0 (2023-07-05)

• Requires Java 17
• Requires Spring 5.2 (when used with Spring)
• Options class hidden
• Deprecated methods and classes removed
• Dependency upgrades

2.38.0 (2023-05-22)

• Support for NumberComparator
• Dependency updates

2.37.0 (2023-03-23)

• Make custom matcher regexp DOTALL (#617)
• Dependency updates

2.36.1 (2023-01-29)

• #595 Fix slf4j dependency
• Dependency updates

2.36.0 (2022-10-05)

• Support for node method in JsonMapAssert #560
• Fixed number parsing in Jackson, so it works as intended (see #564 for details)
• Dependency updates

2.35.0 (2022-05-06)

• Special handling of numeric values in containsEntry #512
• Dependency updates

2.34.0 (2022-04-12)

• Prevent re-parsing of a value #502
• Dependency updates

2.33.0 (2022-04-02)

• Fixed #493 comparison of Tuples from extracting function

2.32.0 (2022-02-17)

• Fixed #474 ClassCastException in isArray()

2.31.0 (2022-02-07)

• Replaced JsonObjectAssert by JsonAssert

2.30.0 (2022-02-06)

• Parent type of JsonObjectAssert changed to AbstractAssert

2.29.0 (2022-02-05)

• #465 fixed assertion on array of objects. May introduce some backward incompatibility when using isArray().element(i).
• Dependency updates

2.28.0

• Automatically register available Jackson 2 modules
• Dependency updates

2.27.0

• Made compatible with AssertJ 3.20.x - due to braking changes in AssertJ this version also requires AssertJ 3.20.x and higher.

2.26.0

• Fixed containsEntries in AssertJ object assert. This required to change the return type of isObject() method which may be an incompatible change for tests which store the result in a variable.

2.25.0

• Hamcrest matcher made compatible with Rest Assured #338
• Various library upgrades

2.24.0

• Fix OSGi configuration
• AssertJ updated to 3.19.0

2.23.0

• Better error message for multiple matches in isAbsent check
• Various library upgrades

2.22.1

• Better exception message in case of JSON that can not be parsed

2.22.0

• Support for Spring WebTestClient

2.21.0

• Fixed Kotlin AssertJ bundle #299

2.20.0

• assertThatJson accepts null as the actual value

2.19.0

• opentest4j made optional #276
• updated all dependencies

2.18.1

• Fix multiple when method application #234

2.18.0

• Support for URI assertions

2.17.0

• Do not append tolerance with zero value to diff message (thanks @valfirst)

2.16.2

• Fix regex issues on older Androids #227 (thanks @Sirrah)

2.16.1

• Add missing Kotlin classes to distribution Jars

2.16.0

• Kotlin DSL for AssertJ API

2.15.0

• Spring DSL Koltin support
• JUnit upgraded to 5.6.0

2.14.0

• Allow differentiating between number and integer

2.13.1

• Fix Jackson2NodeFactory thread safety issue in usage of ServiceLoader (thanks @cnauroth)

2.13.0

• Recompiled with AssertJ 3.15.0 to fix #216
• (Not)Null annotations added
• Spring dependency updated to 5.2.3.RELEASE

2.12.0

• Updated dependencies
• Jackson node is not reparsed when compared #214

2.11.1

• Parse content as UTF-8 in Spring MVC test if not specified otherwise #212

2.11.0

• Fix Kotlin 'Inaccessible type' warning in when-path (@Vladiatro)
• Load resources as UTF-8 (@bencampion)

2.10.0

• Support for PathOptions
• AssertJ - support for chaining assertions in the same root
• Support for json-path in AssertJ whenIgnoringPaths

2.9.0

• Hamcrest upgraded to 2.1
• AssertJ dependency upgraded to 3.12.3 (requires AssertJ > 3.10.0)

2.8.1

• hamcrest-core dependency marked as required

2.8.0

• #185 JsonUnitRequestMatchers for client-side REST testing
• Support for array (non)emptiness in Fluent assert

2.7.0

• Support for Johnzon (requires 1.1.12) (thanks to elexx)

2.6.3

• Ignoring paths even when present in expected value #182

2.6.2

• Fixed AssertionErrors messages in MultipleFailuresError #181

2.6.1

• Path with backspaces matching fixed #176

2.6.0

• ${json-unit.ignore-elements} introduced

2.5.1

• Array comparison optimization

2.5.0

• Fix bug and performance issues in array comparison
• Performance optimizations

2.4.0

• Introduced JsonAssertions.value()
• Fixed AssertJ withFailMessage

2.3.0

• Support for Jackson 2 ObjectMapper customization
• Some AbstractObjectAssert marked as unsupported

2.2.0

• Using opentest4j
• Refactored exception reporting

2.1.1

• Better exception reporting
• Fixed invalid Automatic-Module-Name

2.0.3

• Fixed missing node handling with JsonPath
• Fixed some complex AsserJ comaprisons

2.0.2

• Fixed #144 (AssertJ object handling)

2.0.1

• Support for # instead of $ in placeholders

2.0.0.RC5

• More expressive Spring assertions (isNull, isNotNull, isTrue, isFalse)

2.0.0.RC4

• AssertJ - fix bug with '%' in error message
• Removed support for Jackson 1

2.0.0.RC3

• Support for and() in AssertJ assert
• asNumber() in AssertJ added
• Allow description before inPath() in AssertJ

2.0.0.RC2

• Fixed JsonPath bug #132
• Fixed AssertJ number comparison with Jackson 2 #130
• Fixed AssertJ asString() #131

2.0.0.RC1

• Depends on Java 8
• Some deprecated APis removed
• Introduces AssertJ module
• Introduces JsonPath module

Please do not hesitate to report issues.

1.31.0

• Introduced DifferenceContext into DifferenceListener

1.30.0

• Introduced DifferenceListener
• Array comparison reports extra/missing elements when comparing with array order preserved.

1.29.1

• Fixed error in JsonFluentAssert.ofLength error message
• Fixed matcher handling when comparing arrays #111

1.29.0

• [*] placeholder works even when ignoring array order

1.28.2

• Fixing matcher pattern

1.28.1

• Fixing NPE when accessing element of nonexistent array

1.28.0

• Support for [*] placeholder in ignored path

1.27.0

• Better array comparison and error messages

1.26.0

• IDE friendly error messages
• isStringEqualTo is chainable (thanks to @gsson)
• Dropped support of Java 5
• Automatic module names added

1.25.1

• Support for Jackson BinaryNode

1.25.0

• Support for ignoring paths whenIgnoringPaths()

1.24.0

• Support for parametres in custom matchers ${json-unit.matches:matcherName}param

1.23.0

• Support for custom matchers ${json-unit.matches:matcherName}

1.22.0

• Support for Moshi

1.21.0

• Better diff reporting for unordered arrays with single difference

1.20.0

• Negative array indexes added (thanks roxspring)

1.19.0

• isArray().thatContains(...) fluent assert added

1.18.0

• Resource reading helper added

1.17.0

• System property to specify JSON libraries to be used

1.16.1

• Array pattern accepts non-word characters

1.16.0

• isAbsent and isPresent checks take TREAT_NULL_AS_ABSENT into account

1.15.0

• Dependency on slf4j made optional

1.14.1

• Preferring org.json library to process JSONArray

1.14.0

• Support for org.json library
• Fix: Element out of array bounds is treated as missing

1.13.0

• Support for any-* placeholders

1.12.1

• Single quote values in expected String allowed

1.12.0

• Lenient parsing of expected values

1.11.0

• Option setting methods made deprecated if called after assertion in JsonFluentAssert
• JsonFluentAssert constructors made private. Please file an issue if you need them.

1.10.0

• Added support for IGNORING_EXTRA_ARRAY_ITEMS

1.9.0

• Made compatible with Jackson 1.4

1.8.0

• OSGi support thanks to @amergey

1.7.0

• Support for Spring MVC tests assertions

1.6.1

• Gson nodes are not reconverted

1.6.0

• Added support for Hamcrest matchers

1.5.6

• Fixed handling of empty value in the expected parameter

1.5.5

• Support for dot in node name

1.5.4

• Added isObject method to fluent assertions

1.5.3

• Jackson 1 is preferred if the serialized class contains Jackson1 annotation

1.5.2

• Added support for regular expressions

1.5.1

• isStringEqualTo() added to fluent assertions
• isArray added to fluent assertions

1.5.0

• One runtime now supports Jackson 1.x, Jackson 2.x and Gson
• Internal JsonUnit class changed in backwards incompatible way

1.3.0 + 0.3.0

• Options renamed
• assertJsonNot* asserts added
• Support for online configuration in Hamcrest and standard asserts added

1.2.0 + 0.2.0

• Error messages changed a bit when comparing structures
• Refactoring of internal classes
• Support for ignoring array order
• Support for ignoring values
• Support for ignoring extra fields

1.1.6 + 0.1.6

• Treat null as absent added

1.1.5 + 0.1.5

• Absence/presence tests added

1.1.4 + 0.1.4

• Path to array in root fixed

1.1.3 + 0.1.3

• Numeric comparison tolerance added

1.1.2 + 0.1.2

• jsonStringEquals and jsonStringPartEquals added

1.1.1 + 0.1.1

• Generics in JsonMatchers fixed

1.1.0 + 0.1.0

• Simplified API
• Invalid JSONs in String comparison quoted
• Runtime incompatible (compile-time compatible) changes

1.0.0

• Switched to Jackson 2.x
• Fluent JsonAssert renamed to JsonFluentAssert

0.0.16

• Fluent assertions made framework independent.

0.0.15

• Switched from FEST to AssertJ

0.0.14

• Modules refactored
• Added support for FEST assert

0.0.13

• Logging categories changed

0.0.12

• Added logging

0.0.11

• Ignore placeholder "${json-unit.ignore}" added

0.0.10

• Text differences are closed in quotes

0.0.9

• Matchers added

0.0.7

• Made Java 5 compatible

0.0.6

• assertJsonPartStructureEquals added

0.0.5

• assertJsonPartEquals added

0.0.4

• Better error messages in case of different types

0.0.3

• Support for array types and other oddities in root

0.0.2

• Support for nulls