I created the same scenario using Gatling1.5.2 & ran the test.The url is correctly passed , but it is throwing error Home page: KO Check ‘in’ failed, found 404 but expected Range(200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210). I read in one of the threads in Gatling Google group that api testing is not supported in lower versions of Gatling. Is it because of that?
I don’t know where you read the sentence “api testing is not supported”, but it wasn’t referring to web API but probably to java API (doing some Java benchmarking, like you usually do with tools such as Caliper).
What you’re trying to do with Gatling is very easy actually.
Could you share your simulation, please?
I tried sending the ${User} as a aparam also, It didnt work.Actually if you have a name to the parameter only you can send as a param no? Like for example:
param(“user”:"${User}")
I do not know what is the name for the parameter, in Jmeter I sent it in Raw Data.
I tried sending the data in body also,
.body("""{ “user”: “${User}” }"""), even this didnt work.
I was just informed that the url was changed because the application went to production & the testing setup was removed. I was on leave for couple of days. Extremely sorry to post the question.