[Feature] Allow custom command-line arguments in @playwright/test

When using the Playright test runner, I would like to be able to pass a command-line argument to my Playwright test, similar to this:

npx playwright test --build-path=/path/to/my/application/build/

However, this produces the following error:

error: unknown option '--build-path=/path/to/my/application/build/' 

There should be a way to pass custom command-line arguments to Playwright. This Stack Overflow thread shows that others are looking for this too.

Maybe I’m missing something, but it appears that right now, the only way to pass custom arguments is through environment variables, which seems like an awkward solution.

[refactoreric]

I’m also interested in custom parameters. From an internal requirements document: Various use cases need to be supported, without change to configuration. Preferably as simple as a command line parameter, since environment variables are not self-explanatory.

• Testing from developer/tester machine
• Testing from CI
• Testing against different environments (master, wip, rc, production, etc.) (various variables are dependent on an environment ‘profile’)
• Selecting a predefined type of tests to run (smoke, acceptance, technical release tests, …?)
• Selecting a predefined area of tests to run (bookkeeping, payAndCollect, salesInvoicing, etc.)
• Selecting specific tests.
• Option to run without re-creating a company (useful in CI)

Several of these use cases could be solved with existing command line arguments. But some others can’t.

Since Playwright does not have support for custom command line arguments, I was thinking to just create a wrapper script which sets the appropriate environment variables based on command line arguments and then calls ‘playwright test’. But it’s nicer if that’s not needed.

The ideal solution would also display available arguments (for example with a --usage option) and would show a helpful error+usage message if some arguments were incorrect.

[brunomartinspro]

+1 this is a must, when we have multiple MFEs and we want to do e2e tests we need to pass variables to configure how we want the tests to run. I will try to submit a PR with these changes as soon as possible so you can review.