Skip to content
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

Doesn't pick up the configuration automatically #3

Closed
carlosflorencio opened this issue Apr 19, 2022 · 2 comments
Closed

Doesn't pick up the configuration automatically #3

carlosflorencio opened this issue Apr 19, 2022 · 2 comments

Comments

@carlosflorencio
Copy link

Hi,

I'm giving a try to this extension but found an issue for my use case:

Configuration file not set automatically

My folder structure:

/app
  /tests
    /e2e
      test.spec.ts
  playwright.config.ts

The playwright.config.ts is not used when running the tests, which makes the tests fail (because I have a dedicated webServer.command).

Works after changing the Run Configuration setting, Program arguments option with the value -c /app/playwright.config.ts.

@rickirunge
Copy link

I guess this is the same as #6.

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?
IMO it should (almost) always be the project root - the same ways as when you run playwright using "npm run"

@mbolotov
Copy link
Owner

Fixed in 1.1.2.
The working directory is now set to the project root folder (by searching for a ‘package.json’ file through the file tree up starting from the test file/folder)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants