Validate all specific elements in JSON using Array Testing (Example: json[*].element)

[Artem0ne]

Hello,

we have question regards the JSON schema validation using array filters.
The JSON has the following structure:

[
{
"id" : 1
"status" :  "open"
},
{
"id" : 2
"status" :  "open"
},
{
"id" : 3
"status" :  "open"
}
]

In the area Test we use the following construction to validate the element status:

json[*].status --> equal --> open

and this gives the error..
How can we check that all elements in the JSON have status "open"?

Small tip: the variable assignation json[0].status (green marked on the picture) works fine.

[rangav]

Hi @Artem0ne

please try this json[status!=open] -> Count -> 0

[Artem0ne]

We have many objects with different types of statuses. For example ["open", "closed", "on hold", "active"] with the potential for further expansion. The resulting JSON varies based on the filter parameters specified within the URL.

Example 1:
URL: {host}?status=open,closed
Output:

[
{
"id" : 1
"status" :  "open"
},
{
"id" : 2
"status" :  "closed"
},
"id" : 3
"status" :  "open"
}
]

Example 2:
URL: {host}?status=active
Output:

[
{
"id" : 5
"status" :  "active"
},
{
"id" : 6
"status" :  "active"
}
]

The question is how to test that only the specific statuses (as in example 1 --> ?status=open,closed) that appear in JSON output.
It means that the status can be either "open" or "closed", but not others. If status "active" appears in JSON, it must trigger an error.

Schema validation in Postman would be like:

 "properties" : {
                "status" : { "type" : "string" , "enum": ["open", "closed"]}, 
                }

[rangav]

Hi @Artem0ne You can do schema validation in Thunder Client also.

• You can use the Tests tab and select scheme action
• Or you can use scripting and manually perform schema validation and the function in Post Request filter
• Or you use scripting to write your custom logic for tests

Custom Scripting:
https://github.com/rangav/thunder-client-support/blob/master/docs/filters.md#custom-filters

[Artem0ne]

hi @rangav,

we wanted to use this mechanism: json[*].status --> equal --> open or closed instead of schema validation.
Otherwise, we get too many different schemas as files and we want to avoid it.

Is there any similar solution like json[*].status --> equal --> open or closed to test 1 or many values?

[rangav]

Here are all possible ways you can test arrays
https://github.com/rangav/thunder-client-support/blob/master/docs/testing.md#test-arrays

Or You can also use built-in filters
https://github.com/rangav/thunder-client-support/blob/master/docs/filters.md#built-in-filters

If you have any suggestions for new built-in filters, we can add them

[Artem0ne]

The possible found solution for this:

json[*]|filter(status!=open ) → count → 0