- Issue created by @bradjones1
Functional Javascript tests can be difficult to debug. For instance, if you have an error in PHP code that results in an exception on page load, you will only see an unhelpful message about not finding a button with the correct label or ID to log in. Especially when working locally, this would require a developer to install a working webdriver instance locally and know to drop a breakpoint at a place in the test code where they could see the response. In many cases, this is a "WSOD" type exception that is returned instead of the login screen. None of this helpful information is currently exposed in the test failure. Since logging in to a site is usually one of the first steps in a functional JS test, this is a good place to catch exceptions that result in a "broken" site overall.
Have a PHP error (e.g., mismatched return types) that result in a broken login page. Get an unhelpful error message in Drupal CI.
Show the login page's contents in the assertion message, aiding debugging.
Review and commit.
None.
None.
None.
Don't think we need one.
Active
11.0 🔥