Home
Test Execution Specialist Guide
This guide describes tasks that you can perform to test application code in IBM® Rational® Test RealTime for Eclipse IDE. This guide is intended for testers or test execution specialists.
Testing with Rational® Test RealTime for Eclipse IDE
Read these topics to learn how to use the product.
Analyzing source code
Code review
Code review overview
Automated source code review is a method of analyzing code against a set of predefined rules to ensure that the source adheres to guidelines and standards that are part of any efficient quality control strategy.

Test Execution Specialist Guide
This guide describes tasks that you can perform to test application code in IBM® Rational® Test RealTime for Eclipse IDE. This guide is intended for testers or test execution specialists.
- Testing with Rational® Test RealTime for Eclipse IDE
  Read these topics to learn how to use the product.
  - Getting started with Rational® Test RealTime for Eclipse IDE
    Rational® Test RealTime for Eclipse IDE is designed to integrate into your existing Eclipse-based tool chain. Use this section as a guide to a typical workflow for testing and evaluating your C source code in the Eclipse CDT environment.
  - Importing C projects
    You can either create a new C project with the Eclipse CDT tools or you can import your existing C source files or Eclipse projects into your Rational® Test RealTime workspace.
  - Importing Rational® Test RealTime examples
    Rational® Test RealTime is provided with several sample projects to help you get started.
  - Analyzing source code
    - Runtime analysis overview
      The runtime analysis tools are designed to closely monitor the behavior of your application for debugging and validation purposes. These features use source code insertion to instrument the source code providing dynamic analysis of the application while it is running, either on a native or embedded target platform.
    - Enable runtime analysis tools
      When the source code is run with any of the runtime analysis tools enabled, either alone or in a component test, the source code is instrumented and the results are displayed in a report.
    - Running instrumented applications
      To run a program with runtime analysis tools enabled, you must run it as an instrumented application.
    - Estimating Instrumentation Overhead
    - Reducing Instrumentation Overhead
    - Code coverage
    - Memory profiling
    - Performance profiling
    - Runtime tracing
    - Static metrics
    - Code review
      - Code review overview
        Automated source code review is a method of analyzing code against a set of predefined rules to ensure that the source adheres to guidelines and standards that are part of any efficient quality control strategy.
      - Configuring code review rules
        The code review tool uses a set of predefined rules. You can select the default rule configuration file for the code review tool. MISRA 2004 and MISRA 2012 from Rational® Test RealTime V8.2.0 are the default installed rule configuration files. You can disable or set the severity level to Warning. You cal also configure the entry-point option if your application is multi-threaded.
      - Using a customized Naming script file
        In Rational® Test RealTime for Eclipse IDE, you can edit and customize a Perl Naming script file to check your own naming rules (code custom naming rules U99.1). You must set the path to this customized naming script file in the code review settings to check your naming rules.
      - Code review deviations
        In some cases, it can be useful to temporarily ignore a rule non-compliance on a short portion of source code, while documenting the reason why you are allowing this deviation.
      - Code review MISRA 2004 rules
        The code review tool covers rules from the lists the rules that produced and error or a warning. Each rule can be individually disabled or assigned a Warning or Error severity by using the Rule configuration window. Some rules also have parameters that can be changed. Among other guidelines, the code review tool implements most rules from the MISRA-C:2004 standard, "Guidelines for the use of the C language in critical systems". These rules are referenced with an M prefix. In addition to the industry standard rules, Rational® Test RealTime provides some additional coding guidelines, which are referenced with an E prefix.
      - Code review MISRA 2012 rules
        The code review tool covers rules from the lists the rules that produced and error or a warning. Each rule can be individually disabled or assigned a Warning or Error severity by using the Rule configuration window. Some rules also have parameters that can be changed. Among other guidelines, the code review tool implements most rules from the MISRA-C:2012 standard, "Guidelines for the use of the C language in critical systems". These rules are referenced with an M prefix. In addition to the industry standard rules, Rational® Test RealTime provides some additional coding guidelines, which are referenced with an E prefix.
      - Customizing the code review report
        The default code review report is generated in an HTML format from a template named misrareport.template as that you can modify to customize the code review reports.
  - Coupling Analysis overview
    Coupling Analysis consists of Control Coupling and Data Coupling.
  - Application Profiling
    Application Profiling is gathering the main features that provide profiling information at the application level: the Worst Stack Size feature and the Worst performance (coming soon) feature.
  - Testing software components
- Testing with Studio

Code review overview

Automated source code review is a method of analyzing code against a set of predefined rules to ensure that the source adheres to guidelines and standards that are part of any efficient quality control strategy.

IBM® Rational® Test RealTime provides an automated code review tool, which reports adherence to guidelines for your C source code. Among other guidelines, the code review tool implements rules from the MISRA-C:2004 standard, Guidelines for the use of the C language in critical systems.

Code review is part of the runtime analysis tools and can be engaged during a test run or in the project configuration settings.

After the run, the code review report lists the following elements:

The Outline window displays a list of rules that were not compliant for each source file and function. You can use the elements in this view to navigate through the report.
A summary provides information about the general configuration, the date and the number of analyzed files. It also lists the number of errors and warnings that were encountered.
The code review report lists the rules for which errors or warnings were detected. It also provides information about the location of the error. You can click the title to go directly to the corresponding line in the source code.