Intelligent Test Issue Detection
Automate now intelligently detects a number of issues you may have with your test setup, which result in performance or stability problems. These will be flagged in your sessions on the Automate Dashboard if detected. Users can use these cues to make changes to their test configurations for performance and stability gains.
Automate now detects the following issues:
1. BROWSERSTACK_IDLE_TIMEOUT has occurred
This error occurs when BrowserStack does not receive any commands from the client for a specific period of time. Achieve superior stability and performance of tests on BrowserStack by eliminating Idle Timeouts.
2. HTTP keep-alive missing
This indicates a session did not have HTTP keep-alive directive when connecting to the BrowserStack Cloud. This could have contributed to slower performance in this session. Read our documentation to learn how to use keep-alive.
3. Sub-optimal test route leading to poor performance
You were connected to a BrowserStack hub/repeater from a different region than where you belong. This most definitely led to slower than optimal session performance. Read more about what might have caused this and how to rectify it.
4. Build name not specified OR Same build name used in multiple builds
You have either not specified a build capability in this session or specified it in the incorrect way which leads to sub-optimal experience in the BrowserStack Dashboard.
5. Issues identified with BrowserStack Local connection
A few problems with your Local Testing setup are potentially affecting the overall stability of an Automate session.
6. More than 10% URLs received non-200 (Only works if Network Logs are enabled)
There were non-200 responses received from the application server for more than 10% of the URLs. See the network logs for the session to identify the URLs resulting in non-2xx errors.