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

Bug: Cucumber reporter accesses non-existent file when placing playwright-bdd specific files inside subfolder #161

Closed
leimer opened this issue Jun 4, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@leimer
Copy link

leimer commented Jun 4, 2024

Given

Example project as basis, but playwright specific files moved into a subfolder.

When
npm test

Then

╰─❯ npm test
> [email protected] test
> npx bddgen --config subfolder/playwright.config.ts && npx playwright test --config subfolder/playwright.config.ts


Running 1 test using 1 worker
  1 passed (864ms)
Error in reporter [Error: ENOENT: no such file or directory, open 'features/homepage.feature'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: 'features/homepage.feature'
}

An empty cucumber-report html file is created.

But I expect
The cucumberReporter not failing by accessing a non-existing file.

Isolated demo
vitalets/playwright-bdd-example#17

Environment

╰─❯ npx bddgen env --config subfolder/playwright.config.ts 
Playwright-bdd environment info:

platform: darwin
node: v20.10.0
playwright-bdd: v6.5.0
@playwright/test: v1.42.1
@cucumber/cucumber: v10.3.1
Playwright config file: subfolder/playwright.config.ts
@vitalets
Copy link
Owner

Hi @leimer ! Thanks for the report and sorry for delay.
I confirm the bug, fixed in dev. Will be a part of the nearest release.

@leimer
Copy link
Author

leimer commented Jun 15, 2024

Hi @vitalets, Thanks for taking care :-) We are looking forward to the next release 👍

@vitalets
Copy link
Owner

Released in v6.5.1.
Please re-check on your side and re-open in case of any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants