rafaelsramos/hermeslogger

A Runtime information gathering system aimed at empowering testers/QAs

hermeslogger's Issues

Create Timber tree, to easily anchor to Timber

Create a timber tree, that can be attached to Timber, and log all Timber logs onto Hermes.

This makes it really fast to extract real value from Hermes.

Publish on maven

Have the library accessible from maven repository

• Publish on maven;
• Publish first official release;

Allow filtering by content or date

Allow user to filter all the logs by date, or content, to find what he's looking 4.

Create Info section

In this section/screen the devs should be able to:

1. Communicate general information, to be seen by other devs, QAs and Testers;
2. Provide information that can ease the experience of QA's and testers, such as credentials specific users, or even Service responses, can be copy-pasted into Charles, or other debugging proxy software;

This section/screen must allow for a "folder-like" system, to make it easier to find information.

Add log number on the logs' Overview

As a user, I want to be able to see the number of a Log, to come back to it later on.

Allow devs to place tags on events

In order to group up logs, allow devs to place tags into logs.

This will allow users to more easily find important logs.

Add click listeners on ViewHolders init

Instead of adding the click listeners on the #bind, add it on the init. Minor performance improvement.

Publish beta version

• Clean all code;
• Assure Kotlin coding conventions for libraries:
  • Always explicitly specify member visibility (to avoid accidentally exposing declarations as public API)
  • Always explicitly specify function return types and property types (to avoid accidentally changing the return type when the implementation changes)
  • Provide KDoc comments for all public members, with the exception of overrides that do not require any new documentation (to support generating documentation for the library)
• Allow devs to see implementation;
• Finish readme

Remove external sample App from the project

Create view all logs tab, in the overview section

Allow the user to view all logs, to ease comprehension of what happened

Allow users to interact with the overview, to invoke commands

On the Overview, allow the users to press commands, that will be mapped on the App

Allow adding commands with a ViewTreeObserver, so that it they are recycled automatically

Commands should:

• Have a title;
• Have a brief description (optional);
• Have a confirmation alert;

Example of commands:

• Clear cache or shared preferences;
• Enable / Disable features;
• Enable / Disable other debugging tools;
• Switch between languages;
• Copy something to clipboard;
• Close this tool;

Improve filtering/Search

As a user, I want to be able to:

• Use lower or upper cases to search;
• Use regex to search for it?

Create filter section

Replace the tabs for a filter system, to give us more flexibility

Ensure the toolbox is not shown in production

Start only displaying logs overview after a flag is given

Support some Overview customizability

Allow the library users to edit:

• Overall layout alpha (default value -> 0.9F)
• ...

Improve Info add / show architecture and usability

As a dev, using this library, I want to use it in a structured and meaningful way.

Create settings tab

The settings tab should allow the user to:

• Completly close the toolbox;
• Change the alpha (to allow seeing what's behind it);

Create Overview layout, to ease usage

Add number of notifications

As a user, I want to be able to see how many logs e have, of each type