For a detailed list of the changes in $$PRODUCT_NAME, please take a look at the Release Notes.

What is new in v8.0.1.1 (June 2015)?

• Test Realtime For Eclipse IDE manage Requirements into TestCases and TestHarnesses with possibility to add fields and customize field names.
• Component Testing For C into Test Realtime IDE manage Requirements at TESTs, SERVICEs, and PTU levels with custom fields.
• Both IDE generate requirement reports with test status, code coverage rates and comments in xml format in order to be used as input file into Requirement management and traceability tool. The report can also be seen through web browser. An example of this feature is provided into the StubC project in source.ptu
• Additional requirement fields are allowed into eclipse IDE through window menu::Preferences::Rational Test RealTime::Requirements and into PTU script on the REQUIREMENT line.
• Both IDE accept environment variable as field value through $variableName notation. The expansion of this variable is done at postprocessing, after execution allowing regression testing without rebuild.

• The Eclipse plug-in ported to the new Eclipse 4.2 release (CDT 8.0) which allows to use Code Review Tool for C/C++, Runtime Analysis Tools for C/C++, and Component Testing for C/C++ directly from within the Eclipse shell on Windows, and Linux.
  have a look at the new Eclipse based testing tool www.ibm.com/support/knowledgecenter/SSSHUF_8.0.1/com.ibm.rational.testrt.tour.doc/topics/rtrt_tour_intro.html
• Test RealTime perspective is available into eclipse IDE.
• CallGraph colors can be set into preferences.
• The available eclipse debugger can be used to debug and run the executable on target directly from TestRealtime IDE.
• Any CDT project configuration can be used to create Test RealTime settings automatically.
• All coverage results can be merged into eclipse tool.
• All testing results can be merged into eclipse tool.
• Installation is now based on IBM Install Manager 1.8.
• Memory profiling provide the used stack depth for each thread on target.
• studio tools, Examples and targets are now located into user profile disk space to avoid denied access.
  %USERPROFILE%\AppData\Roaming\TestRealTime\<version>
• Local variables to methods are now accessible from test driver if required.
  an example is provided with the StubC project into source2.ptu that get access to  fct_2(), ret variable.
• Component testing for C can check the stub call order for control flow.
  2 examples of this feature are provided into the StubC project in both source.ptu and source2.ptu
• a new C/C++ instrumentor based on EDG 4.7 parser is now delivered in order to support C++2011.
  It can be selected by the TDP basic settings  key 'USE_ATTOLCC4' =1

• Rational Test RealTime 8.0 introduces a new graphical design for building your test cases and harnesses, based on a the Eclipse IDE environment with the Eclipse CDT extensions. This additional feature is aimed at easily creating new test projects in the C language and is not compatible with test scripts and projects created with previous releases. The original Rational Test RealTime Studio user interface, test scripts, and command-line tools continue to be supported alongside the new environment.
• Rational Test RealTime 8.0 contains key enhancements that include integrations with other popular developer tool environments. These integrations enable developers to ensure quality is built into their daily routine early and continuously throughout the product and software development lifecycle. Benefits of this offering include:

• Key development environment integrations support Agile development practices by bringing together design and construction environments with an advanced verification and testing.

• Integrated with Rational Quality Manager to accelerating test creation and execution across the software life cycle with automated test planning and process workflow.

• Broad host and target support which enables developers to create and reuse test assets across multiple environments.

• Benefits of the new Rational Test RealTime for Eclipse IDE environment include:
• Full integration of component testing and runtime analysis toolchains into the Eclipse IDE.
• Visual editors for test cases, test harnesses and stubs, which eliminate the need to learn a test script language and allow you to concentrate on test data and behavior.
• A call graph view, which helps you analyze the structure of your project and concentrate testing on critical functions.
• A data dictionary, which associates test initialization and expected values with variable types and allows reuse of that predefined data across multiple test cases.
• Easy import of your existing Eclipse C projects and conversion into Rational Test RealTime projects.
• Test harnesses, which contain test cases, stubs, configuration settings and all other source files required to run the test.
• Test suites, which enable you to group multiple test harnesses and run them sequentially. You can also run two test suites in one go, with two different configurations, to compare the results.
• The integration of Rational Test RealTime into the Eclipse IDE also means that you can work in Eclipse with any C language development platform supported by a Target Deployment Port. This brings the comfort of Eclipse development to development platforms that do not natively support Eclipse.

• Please note that this release includes a major change with regards to the instrumentation of C language:
  • The tool 'attolccp' is now used instead of 'attolcc1' to instrument C code, except if in the TDP the basic setting for C 'USE_ATTOLCC1' is defined.
  • By default, when TDPs are migrated over to the new version, the option 'USE_ATTOLCC1' will be set, and therefore 'attolcc1' will still be used.
  • The option '-C99' of the tool 'attolccp' can now be used to analyze C99 source files.
  • Code Coverage MC/DC on bitwise for the C language is now supported via the 'attolccp' tool. The pragma instruction '#pragma attol type_boolean=' can be used to declare which types must be considered as a Boolean.
• New plug-in to the new Eclipse 3.4 release (CDT 5.0) which allows to use Code Review Tool for C, Runtime Analysis Tools for C/C++, and Component Testing for C/C++ directly from within the Eclipse shell on Windows, Linux and Solaris. This plug-in also enables to shell share with IBM Rational Software Architect Standard Edition 7.5.
• Plug-in to the new Eclipse 3.3 release (CDT 4.0) is still available and allows to use Code Review Tool for C, Runtime Analysis Tools for C/C++, and Component Testing for C/C++ directly from within the Eclipse shell on Windows, Linux and Solaris. This plug-in also enables to shell share with IBM Rational Systems Developer 7.0.5, or with WindRiver Workbench 3.0.
• New integration with IBM Rational Quality Manager (RQM) which allows to implement test cases using Test RealTime test script, and to execute regression test suites from within RQM.
• New integration with IBM Rational Test Lab Manager which allows this tool to automatically deploy and install Test RealTime on remote machines.
• When looking at MC/DC code coverage for C/C++ results, a new right-click menu option is available in the viewer to show what conditions could be tested to get to 100% coverage rate.
• The generated code and the runtime for the C language have been optimized further to deal with extremely resource limited target environments. Also note that some files from the runtime have been renamed to avoid conflict with system includes.
• The runtime trace displayed when Component Testing for C tests are executed will now show stub call status and each test status with direct link to the test report.
• Project templates can now be created and then reused in Studio, to speed up the creation of a large number of projects which need to reuse the same settings.
• The new option '-FDCTSFNAME= path' allows to use one single intermediate trace file. Using this option would enable support for parallel instrumentation of source files.
• The System Testing capability now supports test deployment and remote execution over an IPv6 network.
• The new command line option 'studio -view [nodename] ' of studio can now be used to open the test and runtime analysis results of a given project, and optionally for a given project node.
• The command line tool 'attolcc' now generates a new file named 'attolccReport.xtp'. On Windows, when opening this file, you will automatically open all the runtime analysis results associated with it in Studio.

• New plug-in to the new Eclipse 3.3 release (CDT 4.0) which allows to use Code Review Tool for C, Runtime Analysis Tools for C/C++, and Component Testing for C/C++ directly from within the Eclipse shell on Windows, Linux and Solaris. This plug-in also enables to shell share with IBM Rational Systems Developer 7.0.5.
• Plug-in to Eclipse 3.2 (CDT 3.1) is still available and allows using Code Review Tool for C, and Runtime Analysis Tools for C/C++ within the Eclipse shell on Windows only. This plug-in also enables to shell share with Rational Systems Developer 7.0.
• The Code Coverage for C++ capability now also supports MC/DC (Modified Condition/Decision Coverage) coverage level.
• In the Code Review for C tool, user can globally justify some deviations.
• In Memory Profiling, blocks pointed to by a leaked block are now marked as leaked.
• The runtime now supports dynamic allocation of data tables.
• A TDP is available out of the box to support Microsoft Visual C++ 2005 Standard & Express Edition."
• A TDP is available out of the box to support 64 bit Linux.
• The RoseRT plug-in is now available on Windows, Linux and Solaris.

• Code Review for C: A new static analysis tool that Implements most of the rules defined by the MISRA-C 2004 standard can be used to parse your C source code and find potential defects.
• Integration with Eclipse: The Runtime Analysis for C/C++, Static Metrics and Code Review for C capabilities can be used from within Eclipse CDT 3.0 shell. The integration supports both the CDT managed and standard projects. The Target Deployment Port can be used to execute the program compiled within the Eclipse shell and therefore can be executed on a target environment. Results are displayed directly within Eclipse shell.
• A new command has been added in the user interface to update an existing Component Testing for C test script according to the modification that occurred in the source file under test.
• A new settings option makes Component Testing for C to automatically generate the missing stubs in a test script
• The System Testing for C wizard now creates a test script and API template.
• The System Testing for C can launch monoprocess test harness tester without the supervisor.
• The Runtime Analysis capabilities offer a new option to exclude from instrumentation all files located into specified directories.
• A new option allows Code Coverage traces to be compacted. "Code Coverage has an option to ignore the file path allowing to consolidate coverage results from several runs for same files located in different directories
• The Memory Profiling for C/C+ capabilities offers a new option to minimize the size of the instrumented code.
• Memory Profiling for C and C++ can now detect FIM errors (Freeing Invalid Memory).
• Memory Profiling for C and C++ offers an option to not instrument structures and classes which have no methods
• Memory Profiling for C and C++ offers an option to avoid inspection of all variables declared into file located into specified directories.
• A new command can be used to select the entire text in the output windows of the User Interface.
• The Target Deployment Port command line tool attolcc can be customized more easily using the perl language.
• Code size has been optimized for Component Testing for C++ and Runtime Tracing capabilities.
• The Runtime Trace results can now be exported to a file in CSV format.
• The Rose RealTime plug-in has been enhanced to allow parallel build of instrumented model code.
• The Target Deployment Port command line tool attolcc has two new options: -metric to enable the computation of statistical metrics and -codereview to review the code using static analysis