Michael Bodnarchuk

Thanks, @asolodova Please, could you look into failing tests?  They seem to be related to your change > Why is the .seeInField helper implemented this way? I assume this...

Is this still valid? ``` // close other sessions try { const contexts = await this.browser.contexts(); const currentContext = contexts[0]; if (currentContext && (this.options.keepCookies || this.options.keepBrowserState)) { this.storageState = await...

Thanks, due to war in :ukraine: and lot of work on my primary business I don't have time and energy at this moment to enforce this change. I'm not closing...

Sorry, I don't think I will have time to invest into this change This will take too much effort and can affect lots of details It's just naming and no...

I agree to make 2.0 with the only W3C protocol. However, bringing such support without feature cut could be a tricky issue. This really depends on how strict implementation of...

Let me just clarify that Background is indeed executed as beforeEach:  See lib/interfaces/gherkin.js:101

Following documentation before creating an issue is highly recommended Thanks

Any volunteers to send pull request?

I agree that this implementation would be better. I think our implementation was created based on the API of mocha which didn't have any parallelization on the time we implemented...

> It seems that the After implementation is based on [event](https://github.com/codeceptjs/CodeceptJS/blob/3.x/lib/container.js#L320-L322) which is independent from the promise chain. @nnanoob @myrepojuly1987 sorry, I don't think I can provide a quick fix...