If we are running many tests over and over on the same device, it could be difficult to locate the point in the logs where our test ran (and maybe failed).

Test your apps on real devices and get accurate results. The example code at the end of this post demonstrates this.

The beginning of the system logs are only returned on the first call to logs().get('logcat'). Something interesting to note is that every call to logs().get('logcat') will only return log entries since the last time logs().get('logcat') was called. Also check: Getting Started with Appium for Android on Windows A single LogEntry object has toString() and toJson() methods, as well as some methods to get individual parts of the message such as timestamp or log level. The logs are returned as a LogEntries class which implements the interface. We are looking for 'logcat' logs, but notice that Appium also provides android bug report data. The first method returns a collection of Strings which represent the logs which Appium provides.

Remotely test and debug mobile, web, audio and video applications on thousands of devices around the world.

Appium server log example