You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now in case of some failures that's hard to identify the reason especially when application can not work with proxy instruments.
So we need to go to device container and pull entire logcat log.
Ideally we need only log related to the session. And to have it attached right to test run items in Zebrunner.
The text was updated successfully, but these errors were encountered:
in 2.1 we redesigned recorder function. in 2.2 we suppose to migrate onto the unified recorder written in go.
After that ew can think about integrating extra artifacts captring on mobile devices
feature should include providing exact capabilities to be bale to record logcat logs, i.e. don't do this everythine. Also we can start with collecting parameters for logcat so via capabilities user could track everything she needs
Right now in case of some failures that's hard to identify the reason especially when application can not work with proxy instruments.
So we need to go to device container and pull entire logcat log.
Ideally we need only log related to the session. And to have it attached right to test run items in Zebrunner.
The text was updated successfully, but these errors were encountered: