New and Noteworthy


R11A


Message name deciphering

Top


By default, in the MSC view messages are identified by the name of the TTCN-3 type, instance of which is actually sent or received, using the schema @<modulename>.<typename>. In most cases this name is meaningless, as protocol messages are amassed to one top-level TTCN-3 type for more efficient message decoding or, in other cases, the meaninful name are contained in an inner field of the message (like in the SIP protocol). The message name deciphering feature allows the user to select a field for each message to be shown as the message name in the MSC view.


 

 


R8G(1.8)


Searching in TITAN Log files

Top


Using The TITAN Log Search funtionality the user can easily find the log records, matching the given search pattern. To open the search page select the menu option Search/TITAN Log files, or use the key combination: CTRL+H.


 

 

Filtering the displayed log records

Top


The displayed log records can be filtered in the TextTableView and in the MSCView. To set the filtering rule, click on the button on the toolbar of an opened TexTableView or MSC view.


 

 


R4A (1.3)

The main purpose of the 1.3 version was to implement support for zoom and keyboard navigation in the message sequence chart, creation of a new statistical view.


Statistical View

Top


New view

 

A new view is added that displays tables over all included testcases and their verdicts of the selected log files. The Statistical view can be opened for one or several log files.


 

 

Message Sequence Chart

Top


New layout of the message sequence chart

The layout of the message sequence has been changed to the following.

 

Component name at the top of the sequence chart

The component name is displayed at the top of the message sequence chart.

 

Zoom

Zoom in mode . Clicking in the Message Sequence Chart during zoom in mode increases the size of all objects in the Message Sequence Chart.


Zoom out mode . Clicking in the Message Sequence Chart during zoom out mode decreases the size of all objects in the Message Sequence Chart.

 

Overview

An overview of the Message Sequence Chart can be opened by clicking the overview button , which is located in the lower right corner of the Message Sequence Chart. When the overview is shown it is possible to navigate using the keyboard or mouse. To slow down the navigation speed, CTRL and/or SHIFT can be used.


 

Re-ordering component

It is possible to re-order the components (columns) by clicking one of the component headers and draging it to the new prefered position. When the mouse button is released the Message Sequence Chart is redrawn with the new component order.

 

Refresh

Reloads the Messeage Sequence Chart using the current project/workspace settings.

 

Text table view

Top


A message in Text table can be displayed in Value view.

A message in the text table can be displayed in the Value view and displayed as graphical tree or text.

 

Close All open text views

All opened text views can be closed at once by using the button in the toolbar.

 

User Configurations

Top


User configuration for setverdict events

The user can configure what type of setverdict events that will be displayed in the message sequence chart. The strings defining the caused by messages for setverdict(error) and setverdict(fail) can configured.

 

User configuration of coloring keywords in Value view.

The user can configure colors of keywords in a message displayed in the Value view as text.


The following is an example of how the Value view may look when coloring of keywords is used.

 

User configuration of displaying mapping/unmapping and connecting/disconnecting events

The user can configure if mapping and connecting events should be displayed in the message sequence chart.

 

Navigator view - Project tab

Top


Close all connected views

The action Close all connected views will close all associated views to the selected log file.

 

Navigator view - Test case tab

Top


Sorting test cases

The test cases extracted from the log file displayed in the test case tab can be sorted by time, name or verdict, ascending or descending, in the Test Cases tab. To sort the test cases select the prefered sort type in the Sort menu group in the drop-down menu.



 

Filtering test cases

The test cases extracted from the log displayed in the test case tab can be filtered on verdict type. Test cases with verdict error, fail, inconc, none and/or pass can be filtered.To filter the test cases select the prefered verdict type in the Filter menu group in the drop-down menu.



 

Known Issues

Top


Message Sequence Chart

The cursor may flickering when opening large messages in Value view in Tree mode.

 

Message Sequence Chart

The "Input Methods" menu item is shown in the context menu of the MSC view in Solaris and Linux. This is due to GTK and can not be removed within Eclipse.

 

Eclipse 3.3.* and Solaris

Open large files and folders in Solaris may cause out of memory.

 

FAQ

Top


Log event needed for TITAN R/B and R7C generated log files

For a log file generated by TITAN R7B and R7C the event "TTCN Logger v2.n options..." must be included for the Log Viewer to be able to determine what log formats that the new TITAN log formats should be used.

 

Problem with not getting any send and/or receive signal

The Log Viewer is using the messages "Mapping port 'component:port' to 'component:port'. or Connecting ports 'component:port' and 'component:port' for setting up the reference between a component and a port. Theese messages will occurr if the FileMask includes "TTCN_PARALLEL

 

 

 

R3B (1.2.1)

  1. Component name including . and :.

    The rendering has been corrected, so component names including : and . will give the right component reference in the message sequence chart.


R3A (1.2)

  1. Source information displayed in the Value View.

    The source information for the event is displayed first in the Value view.


  2. Message displayed for setverdict(error)/setverdict(fail) in the Value view.

    For setverdict(error) and setverdict(fail) the message displayed in the Value view is the selected event and any event the caused the setverdict(fail/error) event, e.g. a check of earlier messages including any of the predefined string. See the predefined strings in View Message details.
    The check on the predefined strings is case sensitive.

  3. Date displayed for timestamps with dateTime format in the MSC view.

    When the timestamp is of dateTime format the date is displayed after test case name.

  4. Setverdict(inconc) displayed in the MSC view.

    Setverdict(inconc) event is displayed in the MSC view as a black X on the connected component's life line. If no component can be determined the string setverdict(inconc) is displayed over all life lines.
    The setverdict(inconc) is included in the actions Jump to Next/Previous.

  5. Tooltips for Silent Events displayed in the MSC view.

    All silent events that are displayed in the MSC view have tooltips. The tooltip includes the silent event type and the first 500 characters of the message.

  6. Improved filtering in the MSC view.

    Added filtering of functions.
    Added support for using wildcards when filtering components, functions and signals.

  7. Textual representation of log added.

    The Text Table view enables a textual representation of the log file. All log records in the log file are devided into; timestamp, component reference, user message, event type, source info and message. The Text Table view can be opened from a log file in the Projects tab or from a test case in the Test Cases tab or from an event in the message sequence chart.

  8. Improved test case extraction.

    If the extraction of test cases is interrupted due to the log file not fulfilling the requirements, all test cases that were extracted before the interruption will be visible in the Test Cases tab including an indication of that the extraction was interrupted.


Known Issues

The "Input Methods" menu item is shown in the context menu of the MSC view in Solaris and Linux. This is due to GTK and can not be removed within Eclipse.

FAQ

  1. Log event needed for TITAN R/B and R7C generated log files

    For a log file generated by TITAN R7B and R7C the event "TTCN Logger v2.n options..." must be included for the Log Viewer to be able to determine what log formats that the new TITAN log formats should be used.

  2. Problem with not getting any send and/or receive signals:
    The Log Viewer is using the messages "Mapping port 'component:port' to 'component:port'. or Connecting ports 'component:port' and 'component:port' for setting up the reference between a component and a port. Theese messages will occurr if the FileMask includes "TTCN_PARALLEL.


R2A (1.1)

  1. Log formats.

    The TITAN Log Viewer R2A supports TITAN R7A, R7B and R7C log formats.

  2. Enqueued messages.

    Enqueued messages are displayed as arrows with broken lines.

  3. Filtering on silent events.

    The filtering on silent events can be done on either log event category or subcategory. For log files generated by TITAN TTCN-3 R7A the filtering will be on the log event category if any subcategory is selected.

  4. Display of the selected line in the MSCView.

    The selected line in the message is marked with a light grey background.

R1A (1.0)

  1. Setverdict events.

    Only the setverdict(fail) and setverdict(error) events are displayed in the MSC view as a red X or the string setverdict(fail/error) over all life lines if no connected component can be defined.
    In the toolbar of the MSC view two buttons have been added for automatically jump to the next or previous setverdict(fail/error) event.