Vitaliy Potapov

Closing due to inactivity.

Thank you @aslafy-z! I will also investigate. UPDATE: It seems to me that GitHub has made some changes to how trending repositories are determined. They appear to be less dynamic...

Step itself binds fixtures statically, as well as regular Playwright tests. If you want single step to handle different fixtures, you can achieve it via intermediate fixture: ```js export const...

@andreasnovak very nice!

Agree with @thulasipavankumar, it's better to mark these incomplete scenarios/features with `@fixme` tag. Otherwise, we will miss cases when step text of working scenario was changed and not matched to...

> If the implementation is not there, the test can fail which is better experience in my opinion How to handle these constantly failing tests in the pipelines? Moreover, if...

Then we can introduce new option for that - `skipScenariosWithMissingSteps`. When it's `true`, scenarios with missing steps will be automatically marked as skipped. Would it be helpful?

Sorry for late reply! I agree we should try to follow Cucumber conventions where possible. Just want to highlight that for Playwright having tests that are knowingly failing is anti-performant:...

> @vitalets looks like `missingSteps` option in not presented in `7.x.x` version, correct me if I'm wrong... Yes, it is in upcoming v8, will be released soon. > also it's...

Released in Playwright-BDD v8. [New option: missingSteps](https://vitalets.github.io/playwright-bdd/#/blog/whats-new-in-v8?id=new-option-missingsteps) > also it's nice to have ability to generate scenario text when it's marked with some tags - at least @skip This is...