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

[dependabot]

Bumps artillery from 2.0.12 to 2.0.14.

Release notes

Sourced from artillery's releases.

Artillery v2.0.13

AWS Lambda

Lambda Container Images

Artillery will now always use Lambda Container Images to run tests on AWS Lambda. The --container flag introduced in v2.0.12 is no longer required and will be removed in the next release. Creating Lambda functions from .zip archives is no longer supported.

All existing tests should continue running normally without needing any changes. If you run into any issues please open an issue.

This change brings improved startup times for tests running on AWS Lambda and brings AWS Lambda support to parity with AWS Fargate.

Fixes

• Increase startup timeout time for Lambdas running in a VPC (#2778)
• Exit with non-zero code if a Lambda worker fails (#2766)
• Fix issue that could lead tests to crash when triggered from a Windows machine (#2767)
• Expose current worker ID to Lambda workers as WORKED_ID environment variable (#2754)

Playwright

• Accept 0 values for defaultNavigationTimeout and defaultTimeout settings (#2786)
• A warning will be printed if a Playwright testFunction cannot be found (#2782)

Monitoring & observability (publish-metrics plugin)

• Add url attribute to page spans when tracing is enabled for Playwright tests (#2779)
• Fix issue which could cause Core Web Vitals to not be set as span attributes (#2779)
• A test_id attribute is no longer set on all metrics. The built-in $testId variable may be used to set that attribute when needed (#2779)
• Request timing phases such as DNS lookups and SSL handshake timings are now recorded as attributes instead of spans for HTTP tests (#2779)

Slack integration

Fix a number of issues that prevented the Slack plugin from working with tests running on AWS Fargate and AWS Lambda (#2754)

WebSocket

• Errors thrown by hook functions will now be tracked and reported (#2783)

---

With contributions from: @​bbeesley @​HugoImaios @​InesNi @​bernardobridge @​hassy

Commits

• See full diff 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 e9b95a78-6c8c-412f-adab-995eee40e576

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 94cfa8c0-2cff-488c-b4b7-6f54fde1b9de:	0.0%
Covered Lines:	6737
Relevant Lines:	7313

---

💛 - Coveralls