The design goals of this project are as follows:
Android UI logger library.
Main features:
A Simple Log Tool.
An encapsulation of android.util.Log, which provides:
Android UI Automator to JUnit Format Converter.
Reads Android UI automator file outout and write a JUNIT Xml file. For example for usage in CI server as Jenkins.
Just another logging framework. Multiple combinable logging classes. Combine local logging with rolling file logging with Crashlytics with NewRelic...
puree-android is a log collector which provides some features like below:
Puree helps you unify your logging infrastructure.
Sometimes we want/need to know what's going on behind the scenes but our app is not always connected to our computer to let us check the logs. Galgo will let you display your log messages as an overlay on top of your UI.
Extremely useful for testers who want to have more insight into what's going on behind the scenes in our apps when it misbehaves.
You can also define some basic settings such as background color, text color, text size and number of lines to display on screen so it better fits your needs.
Useful logger for Android based on standard android.util.Log class. Simple lightweight (< 50 Kb) implementation of SLF4J API. Easy but powerful configuration via properties file and some additional helpful logging methods. Easy analogue of popular log4j library.
Why?
Debug library provides a lot of useful information. For ex., Java file name as tag, method name and a line number where Debug function was called.
Also, it wraps String.format(), so you can create any message with nearly any quantity of variables to check at almost no pain (and time).
Do you have a library that needs some initial setup like an api key or credentials and without these the library won't work? Now you can use ArrowLogger to highlight this to the developers that use your library.
ArrowLogger allows you to manicly shake your hands infront of your users face and be like "Helllooo you missed this!".
This library is based on the official slf4j-android implementation but with some differences. It does not use the classname as the log tag but instead appends it after the message. It also appends the line number and current thread. Configuration of the log tag is done through a properties file (logger.properties).
A logger with a small, extensible API which provides utility on top of Android's normal Log class.
logback-android brings the power of logback to Android. This library provides a highly configurable logging framework for Android apps, supporting multiple log destinations simultaneously.
The Simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks (e.g. java.util.logging, logback, log4j) allowing the end user to plug in the desired logging framework at deployment time.
Annotation-triggered method call logging for your debug builds.