Coronys Test Automation Framework

How to Create Drill-Down Logs

Objectives

Drill down logs feature takes the user from a general view of the runtime log to the closest in time point in each one of communication logs.
So you will be able to review all communication logs in synchronized manner, just by a click.
This feature is useful for analysis of real time issues in multi-channel systems.

In this tutorial you'll learn HOW TO:
► Create and view HTML run-time logs
► Bind communication logs with the run-time log
► Drill down into run-time and communication logs
► Locate runtime log files on disk

All Tutorials

Coronys Engine is capable to save communication messages of each channel in a separate log file. The drill down logs feature allows you to open one or many communication log files from the Test Case HTML Run-Time log by click. The log will be open at the closest point in time to the Coronys main run-time log message you chose. Taking into account that sometimes communication logs are endless sometimes and synchronization between logs is a hard work, you’ll love this feature.

How to ...

Create HTML Run-Time Logs

By default Coronys ETS does not save run-time logs on disk.
The HTML run-time logs are created just if you configure saving log files.

To save run-time log files of a current test case click on the TC Generate Settings icon.

Double click on "Log File Name" line.

Write down "Auto" in the settings field value.

Locate Log Files on disk

To locate run-time log files on disk go to:

View HTML Log

Run your test case and right click on the "Run Time Log" window.
Select "Open HTML Log" and it will be opened in your default browser.

Bind Communication Logs to Run-Time Log

In order to bind communication logs to the run-time log use ESL command RC_RegisterToMainLog.
Perform this command once for each opened channel to have bookmarks into its communication log.
Bookmarks will be inserted each time your test script issues run-time log message by TMMessage command.
You can define the level of binding - Info, Warning or Error messages.
As your test completed you'll be able to jump from the run-time log messages to the approriate point in all of communication logs.

     Declare Status , PortHdl

     DeclareOnce epIP = '192.168.1.1'

     ; Initialize communication port
     RC_TelnetPortSet PortHdl , epIP
     If Status == 0 Then Abort "Failed to open IP=" $ epIP

     ; Re-route Tx and Rx messages to the HTML communication log
     RC_RouteToFile Status , PortHdl , 1 , "c:\ETS_Workspaces\CLI_1.html" , 3

     ; Bookmarks will be added to the communication log at any Error Message
     RC_RegisterToMainLog Status , PortHdl , 0 , 0 , 1

     End

Drill Down into Your Communication Logs

Link to the Tree-View HTML log to get right to the point fast.

Jump to the first error message or to the error messages list

Open your communication logs at the point closest in time to the run-time log message.

Run-Time log file location.

Use Tree-View HTML Log for Fast Results Analysis