Seth Pollack
Seth Pollack
It is a way to control how we compare the expected JSON with the actual JSON. `match_expected` requires all the keys in the expected JSON are present in the response....
The `match_expected_default` and `match_actual_default` are for setting those options globally. The `match_expected` and `match_actual` are for changing the settings individually in test blocks.
Its not currently supported, but, I'll look into implementing it. Thanks for pointing it out!
Is `description` a key on an object?
Pretty sure thats not valid JSON. It should look like: ``` { "description": [{ "program_id": 317103604, "program_description": "This animated series tells of the adventures of boy reporter Tintin, his dog,...
Why are you using the array path matcher `*` for an object?
1. `expect_json_types('*', name: :string)` 2. `expect_json_types(name: :string, age: :int)` 3. Thats not a valid response. This is a JSON validation library. You can browse through the tests to get a...
You can adjust the strictness with `match_expected: true` and `match_actual: true`. If you do that you can just test for the presence of `{ "foo": "bar" }` and if anything...
You can read more about it here https://github.com/brooklynDev/airborne#configuration
You can also test that it is there and expect it to fail