Failing to launch artillery with typescript playwright configuration #2445
Replies: 3 comments 2 replies
-
Hey @arthurzenika 👋 This is a known limitation of Typescript support right now, and it's due to using We'll work on providing workarounds for this in the near future, but for now you'll have to either not use that package or use Javascript. On a side note, Artillery doesn't use the Playwright Test runner, so you wouldn't be setting configuration with a |
Beta Was this translation helpful? Give feedback.
-
Wow, thanks for the instant response, sorry I didn't understand the link between my traceback and the "known limitations" section. Is there an issue where I can follow the progress on the workarounds ? |
Beta Was this translation helpful? Give feedback.
-
Hey folks / @arthurzenika 👋 The new Artillery release (v2.0.6) contains improvements to the Typescript support. Some documentation: |
Beta Was this translation helpful? Give feedback.
-
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating it.
\-->
Version info:
Running this command:
I expected to see this happen:
artillery works with the
flows.js
demo, but fails when I try to use my existing playwright tests. For "normal" playwright I usenpx playwright test
. The reason I'm using v16.13.1 is that the playwright version used expects this version of node, not a more recent one (I have a hunch this might the problem, so will look into seeing if I can upgrade that version).Instead, this happened:
The above traceback tells me I'm missing some part of the setup.
Files being used:
❯ cat artillery.yml
File: artillery.yml
playwright.config.ts :
Beta Was this translation helpful? Give feedback.
All reactions