Validate a WebService Inteface contract with Gatling.

[Cedric_LP]

Hi all,

I’m starting with Gatling and I want to know what’s the best way to validate json rest API Responses, in order to verify the interface of my WebService.

I tried to use the Gatling’s Check API with JsonPath, but it’s very boring to declare all I want to check (my json can be very huge). Does it exist a “feeder” like that can do it ?

Example :
{
“myDTO”: {
“meta1”: “value1”,
“meta2”: “value2”,
“meta3”: {
“submeta1”: “value1”,
“submeta2”: “value2”
},
“meta4”: [
{
“submeta1”: “value”,
“submeta2”: null
},
{
“submeta1”: “value”,
“submeta2”: "value
}
]
}

thanks a lot.

[Excilys]

What do you want to check exactly? The whole exact message?

[Cedric_LP]

I want to check if all expected objects are in my json response and if their values are correct.

[Excilys]

So, first you’re more doing functional testing than stress testing.

I see 2 solutions:

• check the whole bodyString: https://github.com/excilys/gatling/wiki/Checks#wiki-bodyString, but that means having a JSON string to match against, so if it changes depending on the user, you could inject it with a feeder
• check the checksum (MD5 ou SHA1):https://github.com/excilys/gatling/wiki/Checks#wiki-checksum but that means having precomputed the checksum to match against
  I’d personally go with the 2nd solution.

[Cedric_LP]

It sounds great. I’ll try it as soon as possible.

Thanks.