-
-
Notifications
You must be signed in to change notification settings - Fork 726
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
in BDD or Gherkin mode, the After
is not synchronous where next scenario starts (while the After
is still executing)
#4288
Comments
Agreed… this is really troubling a lot especially handling the after test events in the UI. Would be great if @kobenguyent you can fix this. I believe there was a similar issue with WebdriverIO and they fixed it. |
@DavertMik would you be able to help us with this issue? Pls let us of you need more info… |
sorry, I don't think I can provide a quick fix on this maybe you could use After(() => {
recorder.add(() => {
// my actions
})
}) If you have better suggestion, please send a PR |
@DavertMik Adding the actions to the recorder does not work and it just hangs. Sure, will check for better suggestions. |
This issue is stale because it has been open for 90 days with no activity. |
@DavertMik @kobenguyent - could you please address this? At least if we could use the “I” object in the hooks, it would help us. Currently, adding the “I” object to the recorder inside a hook does nothing and just hangs. |
What are you trying to achieve?
In BDD / Gherkin mode, After to be synchronous so it run to completion before the next scenario starts
Scenario 1
After --- run completely before Scenario 2 start
Scenario 2
What do you get instead?
After
is asynchronous so it might still running while the next scenario already startingIt seems that the
After
implementation is based on event which is independent from the promise chain.Details
The text was updated successfully, but these errors were encountered: