-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How can I define the --config flag? #6
Comments
Wouldn't I need to do this on every test though? As in the workflow would be run test in margin, let it fail, go edit run configuration then rerun. for each test? |
Oh fantastic, that works well thanks! |
Also works if you manual change "Project Base" to the root of your project. Don't know why this is set to the folder of the test being run - don't know when that would be needed? |
I use NX and so my tests are fairly nested within a folder. The npm script I run to get headed tests is
yarn playwright test --config ./apps/my-app-e2e/playwright.config.ts --headed
I don't have anything special in the config file, but I suspect the
testDir: './src/tests',
field is what is causing this plugin to fail to find my tests?Out of the box if I try to run a test from the gutter I get
the console shows
nothing in that command has the relative path to the spec file so I think the config needs to be passed for discovery (or maybe the plugin can pass the full path directly?)
The text was updated successfully, but these errors were encountered: