Stephane Landelle
Stephane Landelle
Just like we use scalafmt for automatically formatting the Scala code, we should do the same for the Groovy code in gradle based projects. Possible solution: https://github.com/diffplug/spotless
The plugin comes with more and more automatic decisions and configuration. IMHO, it would really help support to have the plugin log its decisions. Some users refuse to share a...
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy
As of Gatling 3.2, as explained in the [documentation](https://gatling.io/docs/3.2/general/simulation_setup/#closed-model): > Setting a smaller number of concurrent users won’t force existing users to abort. The only way for users to terminate...
Server might expect form parameters in a specific order. `formParamXXX`, `form` and `formUpload` should preserve original order.
Recorder doesn't support WebSockets atm, see #3356. Then, an intermediate step would be to record WebSocket Upgrade requests as ws.connect and then automatically add a ws.close at the end. This...
And decompose into parts. Currently, we get things like: ``` scala .body(StringBody("""------WebKitFormBoundary${documentBoundary} Content-Disposition: form-data; name="resumableChunkNumber" 1 ------WebKitFormBoundary${documentBoundary} Content-Disposition: form-data; name="resumableChunkSize" 1048576 ------WebKitFormBoundary${documentBoundary} Content-Disposition: form-data; name="resumableCurrentChunkSize" 10080 ------WebKitFormBoundary${documentBoundary} Content-Disposition: form-data; name="resumableTotalSize"...
Inspiration: https://bitbucket.org/atlassianlabs/gatling-jwt
Based on http://www.websocket.org/echo.html, as chatroom sample was removed from Play 2.3.