--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/gatling/c3619469-086a-41cd-96ee-6a6d6aa99c86n%40googlegroups.com.
Hi,
I don't see is as a toy - the check() syntax actually makes it a powerful functional test tool.
For example, in one test "suite" I have a series of specs in a HttpFunSpec, the first of which takes an input json file (with some parameterized values) and submits it to a REST endpoint which processes and persists the data, then returns the constructed object, and it takes the values from this response and saves them to the session. The following series of specs hit the various other endpoints in the service, which return objects constructed from that first spec, and use a comprehensive series of jsonPaths to compare the response data against the values stored in the session. The tests are all driven from the input data, with clean separation between the test data and test logic. So I just have a set of input files that run against the same functional test to fully verify the functionality.
I have no idea if this is how it was envisaged to be used, but it's actually quite elegant and clean. But there are some niggles currently, and I would love to see this developed further.
I wish I could post some of the test code to better show what I mean, but I'm afraid my company prohibits it.