When I review my report, I can see where all response times > 300 milliseconds get listed as unique rows, so I end up with a huge block of rows that all report the same exact error (see screenshot).
This is a bit overwhelming to look at.
Is there something I could do to have all responses that exceed 300 be put into the same group for reporting purposes?
It still would be helpful if there was a complete example somewhere; especially one that uses different scopes for the assertions. I think that is going to be most applicable to my use case.
@ Stéphane
LOL — thanks for being a good sport and letting me know I misspelled your name. I’ll never look at spoons the same way again!
I would love to contribute to documentation.
Although I’ve done a bit of work with Gatling, I still feel very much like a “newbie”, but there are some things I think I understand well enough to impart to others. Then again, perhaps when you are working with a cutting edge tool, that “newbie” feeling never fully goes away.
BTW, the search link you gave below for RC2 (highlighted below) leads to http 404. I do remember when I found the RC2 docs for Assertion Api, it was not the main subject being discussed in the page; it was more of a passing reference.
We'll add some guidelines for contributing for the documentation.
Basically, it uses rst <http://docutils.sourceforge.net/rst.html>, so the
syntax is fine and it's quite easy to edit the raw files. But then, there's
quite a build chain for generating the html files with all the styles if
you want to check the final result.
In your case, I think that what you're looking for is new entries for the
cookbook.
BTW, the search link you gave below for RC2 (highlighted below) leads to
http 404. I do remember when I found the RC2 docs for Assertion Api, it
was not the main subject being discussed in the page; it was more of a
passing reference.