in BDD or Gherkin mode, the `After` is not synchronous where next scenario starts (while the `After` is still executing) about codeceptjs HOT 5 OPEN

this is closely related to this #3870 but in this case, we are on After where we requires teardown of certain UI steps (which means we need to use the I and the approach of recorder doesn't work for us) before proceeding to next scenario

from codeceptjs.

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.

from codeceptjs.

@DavertMik would you be able to help us with this issue? Pls let us of you need more info…

from codeceptjs.

It seems that the After implementation is based on event which is independent from the promise chain.

@nnanoob @myrepojuly1987

sorry, I don't think I can provide a quick fix on this

maybe you could use recorder to synchonize actions inside it?

After(() => {
recorder.add(() => {
   // my actions
  })
})

If you have better suggestion, please send a PR

from codeceptjs.

@DavertMik Adding the actions to the recorder does not work and it just hangs. Sure, will check for better suggestions.

from codeceptjs.