Advanced debugging options

For each test, you are able to further analyze the results by doing the following:

1. Reviewing console logs

After the test finishes running, you can go to "Test log", where you can see the portion of the log related to each step in the test. You can also filter by the level of the log detail that you want to retrieve for each step (verbose, error, warning, or info). This will give detailed information about what happened at each step to better put the information you need at the precise location you need it.


2. Viewing warnings/errors directly from the step result

You will be able to hover over the icons at the top of the steps to get more insights such as console logs (see step 1 above), network errors, or significant page change warnings.

A page change warning is indicated on a test run when the confidence level of the Smart Locator for that element varies by more than 20% as compared to the recorded test. This could be an indication that the underlying code has changed and the user should "Improve" or "Reassign" the Smart Locator for that element.


3. Chrome DevTools debugger

You can use the Chrome DevTools debugger to help you debug your code during a local test run.
You need to add the line debugger; to your JavaScript code, and you need to have Chrome DevTools open in your AUT browser (F-12 (⌥⌘I on Mac)). When your test is running, the Custom step code will stop when it reaches the debugger line, and you'll be able to see it in the Sources tab of the Chrome DevTools debugger with all of its features, like watching variables, step into, step over, etc.

//Your code