Debugging is significantly more difficult when several processes spawn dozens of tests in multiple browsers.

Over the last few years a lot of new testing frameworks have evolved that provide different capabilities but also come with certain limitations. While tools like [Selenium](https://www.seleniumhq.org/) are often seen as slow and flaky and others like [Cypress.io](https://www.cypress.io/) or [Puppeteer](https://pptr.dev/) are hyped as the future in the testing space. In reality all tools have their own use cases, have different levels of support and are based on a completely different architecture. Comparing them is rather useless as it ends up comparing apples with oranges. In larger test suites flakiness and race conditions can happen using all of these tools so that we can safely say that up to this point none of them (including WebdriverIO) has found the ultimate solution for world `/(domin|autom)ation/`.

Over the last few years a lot of new testing frameworks have evolved that provide different capabilities but also come with certain limitations. While tools like [Selenium](https://www.seleniumhq.org/) are often seen as slow and flaky and others like [Cypress.io](https://www.cypress.io/) or [Puppeteer](https://pptr.dev/) are hyped as the future in the testing space. In reality all tools have their own use cases, have different levels of support and are based on a completely different architecture. Comparing them is rather useless as it ends up comparing apples with oranges. In larger test suites flakiness and race conditions can happen using all of these tools so that we can safely say that up to this point none of them (including WebdriverIO) has found the ultimate solution for world `/(domin|autom)ation/`.