The specification briefly mentions a reference to the following fact:

You may already understand that WebdriverIO creates one session of Selenium for each spec file (or feature file in cucumber). In general, you should try to test one function of your application in a single spec file.

However, by the very logic of the organization of mocha-tests, a separate session of the browser is needed for each describe() block, which can also be nested in each other.

Also, I don’t really understand where this fact comes from.

How do you really need to organize tests that work correctly in parallel,
those. with maxInstances larger than one?

    1 answer 1

    Parallelization in WebdriverIO is achieved by sequential execution of individual spec files in parallel running sessions of selected browsers .

    It should be borne in mind that this involves a separate class of ChromeDriver problems, leading to a massive crash of browser sessions for no apparent reason.