What is RTRT?

RTRT is an Automation tool

RTRT can perform the following activities:

1. Component Testing.
2. Coverage Analysis
3. Memory Profiling
4. Performance profiling
5. Trace
6. System Testing.

Why RTRT ?

1. Automation Tool for Testing Software
2. Creates test scripts, drivers, harnesses, stubs and runtime analysis probes directly from your source code
3. Uses your IDE for on-target test execution.
4. Uploads results into detailed, consolidated, exportable reports
5. Targets all platforms – from an 8-bit microchip to a 64-bit RTOS
6. Easy to switch from Component testing to integration testing. (With SIMUL and END SIMUL)
7. Comparing last two consecutive test reports.
8. Provides detailed code coverage information required for safety- and mission-critical certification
9. Enables target-based memory leak detection, bottleneck profiling, and run-time function tracing
10. Integrates with Rational Rose Real-Time, ClearCase, ClearQuest, Test Manager, and Rational Unified Process.
11. Supports full regression testing
12. Automated function, procedure and class testing (also called unit or component testing)
13. Automated multi-threaded and distributed embedded systems testing for integration and validation testing
14. Target-based code coverage sufficient for stringent industry certification standards
15. Target-based memory leak detection, performance profiling, and on-the-fly, UML-based tracin

RTRT GUI :

The RTRT user interface looks like

RTRT browsers are

Project Browser shows project/Group/Node Organization

The project browser looks like

Assert Browser shows all files loaded into Test Real time

1. Easy Navigating to a file for analysis or editing
2. Can expand to see declarations and definitions for file
3. Can sort by files, Objects or packages

And the asset browser looks like

Report Browser gives overview by Report type

1. Independent window, associated with each report
2. Format and content depends on which report has focus

And the Report browser looks like (Coverage)

Tool Bars of RTRTR GUI

The standard tool bar is

Report specific tool bars are enabled when the respective reports are active

Run time trace bar    

Coverage tool bar  

Text Editor Windows

• Edit scripts and source code directly from within Test RealTime.
• Popular editing features:
  • Syntax coloring.
  • Search/replace (with regular expressions).
  • Parenthesis matching.
• Integrated with browsers, report viewers and output window.
• Double-click in a report to open a text editor at the corresponding line of code.
• Select ‘Preferences …’ from main ‘Edit’ menu.
• Control over most aspects of the GUI presentation

Configuration Settings of RTRT

• This window is used to set options for test generation, compilation and execution.
• Any element can have configuration settings:
  • for instance, project, group, node, file
•  Settings are inherited from containing elements as a default

HOST CONFIGURATION:

The Host Configuration area lets you override any information about the machine On which the Target deployment port is to be compiled.

Host Name:    The host name of the machine .By default this is the local host.  

Address:         The IP address of the host. If you are only running Test real time on the  Local host, use 127.0.0.1.

TCP/IP Port:  The port number used by System testing Agents. The default is  100000. 

Socket up loader port: The default is 7777.

Target Deployment Port: Select the applicable TDP from list.

COMPILER:  

Compiler Settings are used during the build of the current node.

Preprocessor options: Specify compilation flags to be sent to the test compiler (if any).

Compiler Flags: Extra flags to be sent to the compiler.

Preprocessor macro definitions: Specify any macro definitions that are to be sent to both the compiler preprocessor (if used) and the test compiler, several generation

Conditions must be separated by comma “ , ” with no space , as in the following

Example : WIN32,DEBUG=1

Directories for include Files: Indicates where Test real time should search for included files when the include statement is encountered in source code and test scripts.

LINKER:

This area contains parameter to be sent to the linker during the build of the current node.

Link Flags: Flags to be sent to the linker.

Additional objects or libraries: A list of object libraries to be linked ti the generated executable.

Test Driver Filename: The name of the generated test driver binary. By default, Test Realtime uses the name of the test or application node.

Directories for Libraries: Indicates Where Test Real-Time Should search for library link files.

BUILD TDP & EXTERNAL COMMAND:

Measure time used by: Selects between a real time operating system clock or per-process or task clock for time measurement. Only if both options are available in the current TDP; otherwise, this setting is ignored.

Maximum on target buffer size: These Box Sets the size of the I/O buffer .A smaller I/O buffer can save memory when resources are limited. A larger buffer improves performance .The default setting for the I/O buffer is 1024 bytes.

Multi-threads: This box when selected protects TDP global variables against concurrent access when you are working in a multi threaded environment such as posix, Solaris or windows. This can cause an increase in footprint of the Target package and also has an impact on performance .therefore select this option only when necessary.

Max number of threads: When the multi thread option is enabled, this setting set the maximum number threads that can be run at the same time by the application.

Use the External Command setting to set a command line for external Command nodes. An External Command is a command line that can be included at any point in your project. External commands can contain Test Real-Time Macro language variables, making them context-sensitive.

How To create a project/ procedure for execution of a project

Step1:

• Launch the RTRT application.
• Start->All programs->IBM rational->IBM Rational Test Real Time.
• Click on New project.

Step2:

Enter the project name and browse the folder in which project can be saved and click on Next button

Step3:

Select the TDP which is applicable and click on Finish button

Step4:

Click on component testing

Step5:

• Click on add file button
• Add the source file and press next button.

Step6:

Click on next button 2 times.

Step7:

• Click on finish button.

Step8 :

Test node is created

Compiling and building the test

• Edit the ptu file with input data and compile the file.
• To compile ptu, right click on ptu file and use compile
• To build the file right click on node and use the Build option
• To view the report right click on node and use view report option.