When exam fail, users often ask & quot; Why do I expend so much time debugging tests and often can ’ t find the subject? & quot; and “ My tests neglect randomly and I know it ’ s not the test, how do I get more visibleness into the seed of my tryout failures? ” Today, we provide a way to answer these questions with Extended Debugging.

When a test fails and it ’ s not an app subject, users want to dive into execution details of how the test was run. In particular, flaky tests are those that fail for no obvious reason – so the failure is usually assigned to the testing infrastructure. To best understand these failure, testers want to entree browser execution and networking data. There are two beginning of this datum:

• Browser console logs give item of how JavaScript is executed by the browser (including execution errors and warnings)

  Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

• HAR (HTTP Archive Files) supply the details of postulation / responses that the browser has made during the test execution process (which browser requests have timed out, not loaded or decelerate down the loading process as easily as faulty API calls).

Extended Debugging provides additional info to help users debug the Selenium tests they run on the Sauce Labs program. The feature helps you understand app issues and nail the root cause of examination failure by providing JS Console log and networking logs with each automated tryout. With these data, developer gain insights into browser and networking issues to facilitate them more speedily identify the root movement of exam failure.

Update: Protracted Debugging is now GA..