It's kind of difficult to debug e2e tests as they depend on the entire ecosystem of an application. Sometimes they depend on prior actions such as login, and sometimes they depend on permissions. Another major barrier to debugging e2e is its dependency on WebDriver. As it acts differently with different operating systems and browsers, this makes it difficult to debug e2e. Besides that, it generates long error messages, which makes it difficult to separate browser related issues and test process errors.
Still, we will try to debug all e2e tests and see how that works for our case.
There might be various reasons for the failure of a test suite as long as it depends on WebDriver and various parts throughout the system.
Let's look at some known failure types:
WebDrive failure: WebDriver throws an error when a command can't be completed. For example, a browser can't get the address that's defined to help it navigate, or maybe an element is not found...