Switching to Gatling for Load Testing

Question

I'd like to use Gatling for REST performance and scalability web service testing. I'm currently using JMeter for this as I wasn't aware of gatling when I started this project. Gatling would integrate better and would be better for the project a number of reasons.

I'd like to ask one main question:

Obviously, there's a lot of overhead in configuring Gatling with the correct web service information. I've already done this in JMeter and I'm not keen to do it again. For one of the sub-projects, we have a WADL but we have no such thing for the other. Is it possible, out of the box, to import:

a. JMeter test plans and
b. WADL documents

into Gatling?

I've looked through the docs but unfortunately I can't find anything that references these.

Answer 1

No, Gatling has neither.

Building a jmx converter is something we might investigate in 2013, as you're not the first one to ask for it. At this point, I'm a bit skeptical, as the logic and the configuration of the 2 JMeter and Gatling are quite different, so the features and the way to use them don't map 1:1.

The easiest way to work with REST APIs is to use the recorder, so you'd dump request bodies as template and then inject data into them. See http://gatling.io/docs/2.1.6/http/http_request.html#request-body

If you work with JSON, you can use our JsonPath (or standard regex) checks in order to make assertions on the response body, or even capture data. See http://gatling.io/docs/2.1.6/http/http_check.html#defining-the-check-type

Answer 2

Using HttpSampler with Raw Post body And last 2.8 version is the right way to test Webservices.

Is it the way you are doing it ? Upcoming 2.9 has new performance improvements related to memory and cpu consumed by Post Processors.

Regarding a, I don't think so.