- #GET AND PRINT APPIUM SERVER LOGS FOR TEST CASE HOW TO#
- #GET AND PRINT APPIUM SERVER LOGS FOR TEST CASE CODE#
The following table lists the supported framework and OS where you can enable telemetry logs.
#GET AND PRINT APPIUM SERVER LOGS FOR TEST CASE HOW TO#
To learn how to visualize request traces using Jaeger, check out the Visualize telemetry logs using Jaeger section. For such complex scenarios, telemetry logs can be integrated with Jaeger to visualize and query the request traces. Handling several requests, tracing logs, or troubleshooting any request failures becomes a complex task in the case of a distributed environment. You can use these insights to troubleshoot your sessions and improve performance. Tracing keeps track of the lifecycle of a request and stores information about the crucial operations performed by the request. With Selenium 4 and OpenTelemetry support, you get greater visibility into the tracing of requests and event logs for each request. The maximum file size you can upload is 2 MB.Īfter you upload the logs, click the Other Logs tab on the Automate dashboard to view them.īrowserStack provides access to the Selenium server in a standalone mode to run multiple tests in parallel, and each test may contain several requests. When you upload terminal logs using build API, the terminal logs will be uploaded for all the sessions associated with the build.įor terminal logs, BrowserStack supports.
You can upload the terminal logs for specific sessions or the entire build using the Session API or the Build API, respectively. On the Automate dashboard, click the Other Logs tab to view the Selenium terminal logs. Note: If the captureContent capability is set to false, the Responses tab is not displayed.Īfter you set the workLogsOptions capability, the Network Logs tab on the dashboard shows the following result:īrowserStack allows you to upload and view your Selenium terminal logs using REST API. In order to capture request and response payload set captureContent to true You can enable them by using the bug capability.īy default network logs does not capture request and response payload. They also help identify any layout or design related issues with your web pages on different browsers. Visual logs help with debugging the exact step and how the page was rendered when the failure occurred.
#GET AND PRINT APPIUM SERVER LOGS FOR TEST CASE CODE#
These contain the screenshots that are auto-generated at every Selenium command that your code executes. You don’t need to set any options for text logs, as these are enabled by default, and cannot be disabled. Text Logs are accessible both from the Automate dashboard, as well as via our REST API to access text logs. They are used to identify all the steps executed in the test and troubleshoot errors for the failed step. These are a comprehensive record of your test. Learn how to debug the running as well as the executed tests on BrowserStack. This document explains the capabilities for enabling the different debugging options that BrowserStack supports. You can use various logging options to debug your failed test cases and fix them with ease.