-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Question: Run by line number #178
Comments
Why not give your scenarios custom tags (e.g. |
You are right, this is not for the long run, for debugging mostly, it can be used for example to run certain scenarios via IDE extension (e.g. VScode). BTW there is no way to run certain example in Outline using the tag system. |
I saw this in Cucumber, and I also curious what is the dev flow for it? Playwright itself does not provide such feature. It can run particular scenario by file + scenario name. For VSCode the expected way for debugging playwright-bdd tests is using Playwright VSCode extension, that allows to run particular scenario / example just by click: |
Ok. |
I use my own one for WDIO + Cucumber. But really it is more for CI/CD not for extension, there are cases when I need to do this on some heavy e2e outlines. |
How to you run particular line on CI/CD? |
Just put something like |
Can I run a specific scenario by line number? It is a handy feature in cucumber-like tools. Example:
npx wdio --spec ./features/test.feature:N
where N - is the number of a scenario name line or line with a specific example in some Scenario Outline.
Yes I know about the @only tag but in some situations run by line is more suitable
The text was updated successfully, but these errors were encountered: