Warning Older Docs! - You are viewing documentation for a previous released version of RhoMobile Suite.

Testing and Logging, and Debugging


Adding Unit Tests

When you generate a model, you get an _spec.rb file generated along with your controller. You would get the following for a model named “Person”.

Generating with model generator:
[ADDED]  app/test/person_spec.rb

This file contains tests for your controller and is in the mspec format: rubyspec.org

describe "Person" do
  #this test always fails, you really should have tests!

  it "should have tests" do
    true.should == false

We use this test format internally as well. You can see our specs for the core framework here which use many functions of mspec.

To run these tests however, you need the testing framework to be included in your app. To add this, you would run the rhogen task in your application folder:

$ rhogen spec

You will then see the mspec framework added to your application:

Generating with spec generator:
     [ADDED]  app/SpecRunner
     [ADDED]  app/mspec.rb
     [ADDED]  app/spec_runner.rb

Finally, add the fileutils and mspec extensions to your build.yml:

extensions: ["fileutils", "mspec"]

You are now ready to run the tests. Simply add a link to the SpecRunner controller, and you will get a summary of number of passing/failing tests

In your index.erb: :::html

  • Run tests
  • A summary of the results will be displayed on the screen.

    Detailed results will be displayed in your rholog.txt:

    I 01/15/2010 16:36:33 b0185000                  APP| FAIL: Product - Expected true
     to equal false
    apps/app/mspec/expectations/expectations.rb:15:in `fail_with'
    apps/app/mspec/matchers/base.rb:8:in `=='
    apps/app/Product/product_spec.rb:5:in `block (2 levels) in <main>'

    And finally, a summary will be printed in rholog.txt as well:

    I 01/15/2010 16:36:33 b0185000                  APP| ***Total:  3
    I 01/15/2010 16:36:33 b0185000                  APP| ***Passed: 1
    I 01/15/2010 16:36:33 b0185000                  APP| ***Failed: 2

    Disabling tests

    When you are ready to do a production build of your application, change build.yml’s build property to ‘release’ and the specs will not be included in the binary:

    vendor: Acme, Inc.
    build: release


    There are two methods to log messages.

    From any controller you can log using the methods app_info and app_error. These methods take a string and will write that to rholog.txt with the category of your controllers name. See platform specific build topic to see notes on how to get rholog.txt.

    Call app_info and app_error from a method in your controller:

    def index
        app_info "My info message"
        app_error "My error message"

    There also is a logging Ruby class called RhoLog. This class has methods info and error which take 2 strings. The first string is the category, the second string is the message.

    The RhoLog API has methods to print error messages. Click the links below for detailed information about the methods.

    • info - Print an information message in the rholog.txt file.
    • error - Print an error message in the rholog.txt file. The message will have an “ERROR” prefix.

    Call the RhoLog error or info methods from a method in your Rhodes app:

    def index
        RhoLog.error("Some Category", "Some error message")
        RhoLog.info("Some Category", "Some info message")

    Additionally all common ruby output routines (like puts, print) are redirected to rhodes log with INFO level.

    In rholog.txt the lines appear as follows:

    <Timestamp> <category> | <message>

    To enable remote logging just add the line to rhoconfig.txt:

    rhologurl = 'http://<host>:<port>[/path]'

    Then all log messages will be sent to the specified URL via POST HTTP-requests.

    You can also send log to remote server manually: Log server address where log will be posted by using RhoConf.send_log or from the log view. Log server source code is open and available at http://github.com/rhomobile/rhologs, so you can deploy your own logserver.

    Add the lines to rhoconfig.txt:

    logserver = 'http://rhologs.heroku.com'

    Then call RhoConf.send_log:

    def index

    See Log Configuration for all Logging configuration parameters.

    How see log messages from iOS device.

    You have next ways for get log from iOS device :

    1. See full console output

    2. open XCode

    3. open Organizer (“window” submenu in top menu)
    4. select “Devices” tab
    5. select your connected device in left panel
    6. select “Console”

    7. Get the rholog.txt file from device

    8. open XCode

    9. open Organizer (“window” submenu in top menu)
    10. select “Devices” tab
    11. select your connected device in left panel
    12. select “Applications”
    13. select your application and wait few seconds
    14. you can select local file in your application’s local folder and download it to computer - use “Download” button in bottom panel

    15. Send log to server from application

    RhoError class

    You may find access to the error class useful in logging and reporting:

    This class contains error codes and the method message() to translate error code to a text message. All callbacks return an error code from this class. The status text in the callback contains some internal error message, so in most cases it should not be exposed to user. Currently RhoError contains the following error codes:

    ERR_NONE = 0


    See Login/Logout Manager as an example.


    You can use the RhoStudio debugger to debug your Rhodes app.


    To perform performance measurements or found applications bottlenecks you can use RhoMobile Profiler tool.

    RhoMobile Profiler use performance counters to calculate execution time of specific function/code. There are 2 types of counters: global and local:

    • Global counters created once and can be stopped/started many times. When Global counter destroyed, it log accumulative time of all start/stop intervals.
    • Local counters can be stopped/started only once. While stopped, counter will log time interval between start and stop.

    Profiler log.

    When Counter stopped (Local counters) or destroyed(Global counters) information from counter will be logged in the following format:

    (log prefix) PRFILER| (counter name)( (counter time Minutes:Seconds:Milliseconds) ): START/STOP

    For example:

    I 06/18/2012 23:27:20:311 00002ffc PROFILER| BROWSER_PAGE (0:03:104) : STOP

    Enable Profiler.

    Profiler is configurable at build time in build.yml file(Turned Off by default):

    profiler: 1

    Will turn on Profiler

    After Profiler ON/OFF - full rebuild is required.

    Built-in performance counters.

    These counters start working after you turn on Profiler in build.yml:

    • ERB_RENDER - ERB-file render (Ruby)
    • CTRL_ACTION - Controller action (Ruby)
    • INDEX_ACTION - Index page render
    • ERB_RENDER - ERB-file render (Ruby)
    • BROWSER_PAGE - Browser page loading time (Native)
    • SyncEngine components has several native counters:

      ‘Sync’ - Full sync time

      ‘DB’ - Time spend for database insert/update/delete while sync

      ‘Net’ - Time spend for network communication while sync

    These counters works only if you create them in application. You can create counter in controller action and destroy it after some operations:

    • Sqlite database (Native)

      ‘SQLITE’ - counter for whole time processing SQL query including data conversion , sqlite3_step and prepare statement

      ‘SQLITE_EXEC’ - sqlite3_step time only.

    To Enable Ruby Garbage collector logging modify rhoconfig.txt(set log level to Trace):

    MinSeverity = 0

    There are two Profiler API available: Ruby and Native(C/C++).

    RhoProfiler Ruby API Examples

    The RhoProfiler Ruby API contains the following static methods.

    • create_counter creates a Global counter.
    • destroy_counter destroys a Global counter.
    • start_counter starts a Local or Global counter. If a Global counter with this name exists, this global counter will be started. If no global counter exists, a local counter will be created and started.
    • stop_counter stops a Global or local counter.
    • flush_counter logs information from a counter (Local or Global). Counter does not stop or start.
    • start_created_counter - The counter will start only if it is already created previously (Global counter).

    Example of custom counter:

    def index
        #do something
        RhoProfiler.destroy_counter('Counter1') #Will log summary of function1 and function2 execution time

    Example using ‘SQLITE’ built-in counter:

    def some_method
     #do something: create/update objects for example

    RhoProfiler C/C++ API.

    RhoProfiler C/C++ API contains several defines to manipulate Performance Counters. Here is the list of defines:

    //Global accumulative counters
    #define PROF_CREATE_COUNTER(name)     // Create Global counter
    #define PROF_DESTROY_COUNTER(name)    // Destroy Global counter
    #define PROF_START(name) //Start Local or Global counter. If Global counter with this name exist , this global counter will started. If no global counter exists, local counter will be created and started.
    #define PROF_STOP(name) // Stop Global or local counter. 
    #define PROF_FLUSH_COUNTER(name,msg) //Log information from counter(Local or Global). Counter does not stopped or started. 
    #define PROF_START_CREATED(name) //Counter will start only if it is already created previously(Global counter)


    #include "statistic/RhoProfiler.h"
    void testFunction()
        //do something
        PROF_DESTROY_COUNTER("Counter1") #Will log summary of function1 and function2 execution time
    Back to Top