Hi everyone, is it possible in Gatling to use feeder with different certificate for every request?
I've also asked this question on SO (http://stackoverflow.com/questions/28694659/gatling-change-ssl-cert-used-in-feeder-per-request), but a colleague pointed me to your google group.
Consider the test:
Example implementation:
val feeder = Array(
Map("data" -> data(user1_data),
"gatling.http.ssl.trustStore.file" -> "/tmp/test-data/rb.jks",
"gatling.http.ssl.trustStore.password" -> "password",
"gatling.http.ssl.keyStore.file" -> "/tmp/test-data/user1.jks",
"gatling.http.ssl.keyStore.password" -> "password"),
Map("data" -> data(user2_data),
"gatling.http.ssl.trustStore.file" -> "/tmp/test-data/rb.jks",
"gatling.http.ssl.trustStore.password" -> "password",
"gatling.http.ssl.keyStore.file" -> "/tmp/test-data/user2.jks",
"gatling.http.ssl.keyStore.password" -> "password")
)
...
val scn = scenario.exec(reportableTest(
repeat(feeder.length) {
feed(feeder)
.exec(http("test user personal data")
.post(user_url)
.headers(user_headers)
.body(StringBody("${data}")).asJSON
.check(
status.is(201),
header("Content-type").is("application/json"),
)
}))
I did call: .disableClientSharing in scenario setup.
The weird behaviour is, it seems that only the first
"gatling.http.ssl.keyStore.file" -> "/tmp/test-data/user1.jks",
is processed. The next are not (even if I create another reportableTest). I've simply changed the order to see that in fact in both request the first "userX.jks" is being used.
Is this the normal behaviour? Is it a bug?
--
You received this message because you are subscribed to the Google Groups "Gatling User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatling+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
val scn = scenario.exec(reportableTest(
repeat(feeder.length) {
feed(feeder)