When selecting a mobile testing platform some people prefer to combine a few tools, which gives them a lot of opportunities to cover the wide range of features. Other people make a choice in favor of all-in-one solutions. Such solutions help to accumulate all the information and reports in one place and there is no need to worry that some data will be lost in one of the used tools.

While Ubertesters is one of the all-in-one solutions, you can not only enjoy its features and manage all your testers in one place, but you can also customize and optimize it to your needs.

Remote logging with Ubertesters

The benefits of remote logging with Ubertesters

Previously we described the Ubertesters API options. One of the API methods is remote logging (custom logging). It allows you to send an important system event information to the Ubertesters server dedicated to storing and archiving this data.

Sometimes the reported issues or crashes do not give you the required info. You can put the logged messages in your code to check what was wrong with an app when the bug was found or what the reason of app crash was. To investigate the issue from inside and to pay developer’s attention to the certain info, add custom logging method and check its results in Ubertesters account.

Where can you check the custom logs?

You can check the sent logs in your Ubertesters account in Activity tab > Feeds > Select the feed > Activity Stream .

Remote logging with Ubertesters

The type of the sent logs depends on the log method you have used during the SDK integration. You can read more about log methods and see how the code samples look like in our API methods article.

What can be logged?

Custom logging method allows you to determine the type and the content of the recorded logs and adds the flexibility in logging different kind of data.

You can log the following log levels:

  • Info
  • Warning
  • Error

The examples of Log method usage for your platform can be found at SDK Guide page.

We do not limit the range of fields you can log. It is possible to log any data you need for your internal usage. The custom logs can include the following:

  • User requests – if you need to receive the users’ data or the info about their IP etc.;
  • Project and revision details – you can indicate the project title, revision id, etc.;
  • System events – all the requests, errors, crashes etc.;
  • Objects – the objects contained in the code of your build;
  • Modify the time stamps – you can manage the time stamp format and modify it to your needs;
  • Other.

Usage of the custom logs can be of a great help to the developers who will check and fix the reported bugs. Being able to check the recorded logs directly in Ubertesters account, next to the reported issues and crashes, they can get much more info that was initially reported by the tester. In addition, it will take much less time to make the improvements and fix the bugs. Try our Custom (Remote) Logging method now and enjoy the results.

Comments
Harvey Specter
Posted at 11:50 pm March 13, 2015
Alfonso
Reply
Author

There is a simple way to replace NSLOG with your UTLOG ?
Testflight used to have a macro TFLog which you can put on the pch to replace your NSLOG

    Harvey Specter
    Posted at 12:12 pm March 17, 2015
    Ran Rachlin
    Reply
    Author

    Hello Alfonso, thank you for your question. It is impossible to convert NSLog into UTLog. However you can use UTLog to send the required data or use UTLog instead of NSLog.

Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>