Releases: artilleryio/artillery
Releases · artilleryio/artillery
Artillery 1.5.0
Changelog
- Warn when running on Node.js v6.8.1 - v7.2.0 and using
rampTo
as it can lead to the process entering an infinite loop due to a bug in Node.js timers.
Artillery 1.5.0-22
Changes
Bugfixes
- Fix HTTP error handling
Artillery 1.5.0-21
Changelog
- Much smaller memory footprint for HTTP tests
capture
expression can now contain template strings- RegExp captures can take flags
Artillery 1.5.0-20
Changes
Bugfixes
- Fix installation error
Artillery 1.5.0-19
Artillery 1.5.0-18
Changes
New Functionality
- Loops can now be nested and counters named with the
loop.loopValue
option - WebSocket
send
allows templates and object literals now - Add
jitter
option tothink
- Increase default HTTP timeout to 120 seconds
- User and password options in HTTP Basic auth can now be templated
- HTTP response body now included in debug output
Bugfixes
Artillery 1.5.0-17
What's New
capture
/match
for Socket.io (h/t @gboysko)- Fix bug in
artillery quick
where the-n
parameter would get ignored - Various internal architectural changes and fixes
Artillery 1.5.0-16
Changes
- Artillery will now report how many of each of the scenarios were launched
Artillery 1.5.0-14
Changes
- Bugfix: crash when
-o
is not set - Bugfix: crash on reports that don't contain custom stats
Artillery 1.5.0-13
Changes
- Logs can now be output to a directory with the
-o
parameter. - Custom stats are now included in HTML reports
- HTTP scenarios can now be aborted from hook functions by invoking the callback argument with an error
- HTTP timeout can now be set with
config.http.timeout
(config.timeout
is to be deprecated) - YAML references are now supported
- New more efficient and precise implementation of ramps
- Socket.io - fix for comparing object literals (h/t @outsideris)
think
can now be parameterised with variables (h/t @lordjabez)- Errors in capture transforms won't abort the scenario anymore (h/t @lordjabez)