chore(deps-dev): bump artillery from 2.0.11 to 2.0.12

[dependabot]

Bumps artillery from 2.0.11 to 2.0.12.

Release notes

Sourced from artillery's releases.

Artillery v2.0.12

AWS Lambda

Artillery can now use Lambda Container Images to run tests on AWS Lambda. Pass the --container flag to run-lambda command to use a container instead of a zip file. No further configuration is required.

This change brings two main benefits:

1. Much faster startup times for tests
2. Ability to use certain features that were previously only available in tests running on AWS Fargate:

• Run test scripts that TypeScript hooks
• Use third-party dependencies
• Use the built-in publish-metrics plugin

Container-based Lambda functions will become the default option in a future release of Artillery.

• artilleryio/artillery#2674 • artilleryio/artillery#2724

Playwright

• Fix tests failing on Fargate with ENOSPC error with Playwright tracing enabled artilleryio/artillery#2717
• Improve reliability of trace collection:
  • Reduce trace collection cooldown period to 1-5m
  • Increase the number of concurrent trace recordings to 3 up from 1
• Track the number of collected/discarded recordings with browser.traces_collected and browser.traces_discarded metrics

CLI & Core

• Make path to the config directory available to test scripts via the special $dirname variable artilleryio/artillery#2614 docs
• The --scenario-name flag will now default to using an exact string match, and fall back to using a regex artilleryio/artillery#2709
• Clarify the meaning of --tags flag artilleryio/artillery#2699
• Remove an unnecessary dependency artilleryio/artillery#2703

Slack integration

• Artillery now includes an official Slack integration, which can be used to post test results to a Slack channel automatically artilleryio/artillery#2688 docs

---

With contributions from: @​bernardobridge @​InesNi @​hassy @​43081j @​MIJOTHY-V2

Commits

• 91a1445 ci: release v2.0.12 artillery (#2740)
• bf75e55 feat: include Slack integration (#2735)
• fa6acff feat(cli): expose dirname utility to test scripts (#2614)
• 6680314 fix(fargate): replace special characters in task name (#2736)
• 0e34b80 feat(lambda): enable typescript support with container lambda (#2734)
• 88e686a fix(core): allow scenario name exact match without using regex (#2709)
• 5374048 dep(playwright): update Playwright to v1.44.0 (#2732)
• fedb959 fix(lambda): revert console log to debug log (#2733)
• 129c69a feat(lambda): use artillery-hosted ECR image (#2724)
• 81717f9 ci(docker): build docker image in single line command (#2731)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coveralls]

Pull Request Test Coverage Report for Build 2dcc7621-20de-4c8d-b62a-9d071df203b1

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 92.124%

---

Totals
Change from base Build da4a0299-0618-4221-9a53-c61ff5fd3f9e:	0.0%
Covered Lines:	6737
Relevant Lines:	7313

---

💛 - Coveralls