[BUMP] Update dependency artillery to v2 (load-testing) #7578
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.7.9
->^2.0.0
Release Notes
artilleryio/artillery (artillery)
v2.0.1
: Artillery v2.0.1Compare Source
CLI & Core
think
steps in scenarios (#2272)metrics-by-endpoint
plugin is now enabled by default to capture per-URL metrics in HTTP tests. The metrics will be available only in the JSON report and not output to the console, unless the plugin is loaded explicitly by the user. (#2274)--cpu
and--memory
flags (#2301)$env
not resolving correctly in theconfig
section (#2265)--scenario-name
not picking up the correct scenario (#2314)fake-data
plugin to allow for realistic test data to be generated in your tests (#2318) (docs)ensure
checks (#2284)expect
plugin (#2298)OpenTelemetry
test.step()
calls, page navigation events, and Core Web Vitals metrics (#2259)400
or higher (#2285)HTTP_REQUEST_CONTENT_LENGTH
,HTTP_USER_AGENT
andHTTP_FLAVOR
attributes (#2285)vu.uuid
) not always being set correctlyPlaywright
publish-metrics
plugin (#2259)FID
Core Web Vital metric not being emitted as expectedECS/Fargate
--cpu
and--memory
flags (#2301)Socket.IO
args
/on
options (#2171)match
errors in the reportThis release brought to you by @bernardobridge @InesNi @josh-coderpad @hassy
Configuration
📅 Schedule: Branch creation - "every 1 hour every weekday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.