Evaluation copy

Request for an evaluation copy by filling the contact form here.

OpenTTCN Newsletter

Request OpenTTCN Newsletter by filling your contacts here.


OpenTTCN TTCN-3 Debugger

 


 

 

 

 

 

Introduction

OpenTTCN developed OpenTTCN Debugger already in 2007 as a command-line tool based on largely popular user interface of GNU debugger. Now OpenTTCN has integrated this native TTCN-3 source code debugger to OpenTTCN's TTCN-3 Integrated Development Environment (IDE) so that TTCN-3 debugger can be controlled directly from TTCN-3 editor and debugger control panel. OpenTTCN Debugger is a part of OpenTTCN Tester 2012.

 

Benefits

  • learn TTCN-3 faster by following TTCN-3 code execution step by step,
  • test protocols in a simulated environment using virtual time before the real hardware becomes available,
  • debug complex System Under Test (SUT) problems using breakpoints and tracepoints,
  • debug complex Abstract Test Suite (ATS) problems using single stepping and variable view, and
  • save time and money when SUT and ATS problems can be resolved more quickly.

Features

  • OpenTTCN Debugger is a native TTCN-3 source code debugger,
  • Run TTCN-3 code in debug mode without special debug compilation,
  • Set breakpoints and tracepoints by double clicking next to the source code line of interest directly from the TTCN-3 editor,
  • Breakpoints allow suspending TTCN-3 test case execution in order to allow examination of parameter and variable values at any given line (breakpoints suspend the TTCN-3 timers as well),
  • Tracepoints allow inspection of parameter and variable values without suspending test case execution (most useful when using debugging in non-virtual time environment),
  • Execution can be suspended when a breakpoint is hit, or when a user breaks execution manually,
  • When execution has been suspended with the debugger, execution can be continued with step in, step over, step out, and continue instructions,
  • Multiple test components can be debugged in sequence,
  • Test component to be debugged can be selected from the list of available test components,
  • Under the selected test component, the user can select a specific stack frame for display of parameters and variable values at that context, and
  • Debugger can interface with user provided timer implementation for the use of the same virtual time that is used when running System Under Test (SUT) in a simulated virtual time environment.