SCoE is a tool that can help identify what is causing a certain test to fail. A SCoE will, among other things, take a screen shot for each step of the transaction, enabling you to see the web page rendered when the Dynatrace Browser agent was running the script. All of this information can help you to troubleshoot issues as they occur.
In the Dynatrace Portal, SCoE provides you with the following data about any error:
Screen Captures of the page where the error occurred.
The raw source code for all downloaded frames and windows.
Header information for all the test's requests until the failure.
Trace Route on Error (TRoE). Only captured if the test fails due to a network related failure.
All this information can help diagnose a problem.
For example, if a script fails due to User Script failures ( error code 15001), you can use the Screen Capture to see if the correct page was downloaded. If not, you can adjust the script to point to the correct page. If the correct page was downloaded, you now know that you need to verify that the script's User Actions work against the downloaded source code - the website's code may have recently changed.
The header information is also useful as it can confirm whether or not the Gomez Agent sent the correct HTTP requests to the host server when requesting a specific page. Note that for more complete header information - including any POST data that was sent - you can download the .zip archive from the SCoE page and view the headers.xml file.TRoE can help you diagnose network related timeouts and errors. When a test fails due to a network related failure, the trace route is available in the SCoE so you can determine where the problem occurred.
More information for SCoE and how to enable can be found in the help page Viewing screen captures.