What is new in v8.2 ?

• Data Coupling for C language:
• Data Coupling is defined as "the dependence of a software component on data not exclusively under the control of the software component" in the Clarification of Structural Coverage Analysis of Data Coupling and Control Coupling document edited by the Certification Authorities Software Team (CAST). The purpose of this feature is to measure and ensure the accuracy of interactions and dependencies between modules/components.
• $$PRODUCT_NAME introduces a new coverage level called 'Data Coupling for C language' that is used to verify that all the global variables of the application under test have been consumed in read (also called use) and write (also called def) mode during the tests, as follows:
  • For each global variable, $$PRODUCT_NAME identifies the def and use. Then it considers all the possible def/use pairs as one Data Coupling.
  • To cover an occurrence of Data Coupling, for example, for example, a def/use pair, at least one existing test should have run the def/use pair.
  • $$PRODUCT_NAME provides a new interactive HTML-based report.

• Worst Case Execution Time for C language:
• Performance analysis now calculates an estimation of the Worst Case Execution Time (WCET) for the C language and provide a new report.
• The WCET measure is calculated from the maximum execution time in each function and the number of times this function is called by the other functions of the application.. The WCET is calculated from the call graph using this metrics collected during the tests. THE WCET is relevant if the tests have called the functions of the application in the worst condition for each of them.
• The new report is in a HTML format including all the information of the previous performance report, and additionally the WCET and the call graph with WCET metrics.

• Code Review MISRA 2012:
• $$PRODUCT_NAME now supports MISRA 2012 standard (Decidable rules).
• In $$PRODUCT_NAME for Eclipse IDE and RationalIBM® Test RealTime Studio you can select MISRA 2004 or MISRA 2012 rules. You can also create you own rules by selecting rules from the MISRA 2004 and/or MISRA 2012 standards.
• MISRA 2004 rules have been enhanced with additional optional rules coming from MISRA 2012 standard.

• Support Red Hat Enterprise Linux 8.0 64 bits.

• Control Coupling
• Report updated: Control Couplings are now grouped by compilation unit pairs in the reports. Each group has its own call graph. Options are available in the report to display or hide information.
• Module as Function: The CAST-19 paper describes the Control Coupling between "modules” but does not explain what a module is in C language. In $$PRODUCT_NAME V8.1.0, a module was considered as a compilation unit (i.e a C file). In $$PRODUCT_NAME V8.2.0, you can set an option to consider a module to be a function. In such case, all the calls between functions (internal or external) are considered as a Control Coupling.
• Component (with Module as Compilation Unit): For Control Coupling with the "Module as Compilation Unit" option enabled, a new option is available to group some of the compilation units into a unique component. In such case, calls between these unit components are not taken into account.

• Worst Stack Size
• Support for multi-threaded application: For such application, it is possible now to provide the list of entry points (one entry point should be the main for a thread). If this information is provided, $$PRODUCT_NAME calculates the Worst Stack Size for each thread, and also the total Worst Stack Size. Optionally, it is possible to provide the maximum Stack Size allocated to the stack in the application and a security margin in percentage. If these options are selected, the report displays an additional section with the verification results.

• Option for requirements tools in $$PRODUCT_NAME for Eclipse IDE
• You can import in $$PRODUCT_NAME for Eclipse IDE the requirements that you have exported into a .cvs file. A list of requirements is proposed when you link a requirement to a test case, test harness or test suite.

• Control Coupling for C language:
• Control Coupling is defined as 'the manner or degree by which one software component influences the execution of another software component' in the 'Clarification of Structural Coverage Analyses of Data Coupling and Control Coupling' document edited by the Certification Authorities Software Team (CAST). See https://www.faa.gov/aircraft/air_cert/design_approvals/air_software/cast/cast_papers/media/cast-19.pdf. The purpose is to 'provide a measurement and assurance of the correctness of these modules/components' interactions and dependencies.'
• $$PRODUCT_NAME introduces a new coverage level call 'control coupling' for C language that consists of verifying that all the interactions between modules have been covered by at least one test. Here is how $$PRODUCT_NAME is doing this new coverage level:
  • Modules for C language and compilation units (i.e. C files that are independently compiled).
  • Interactions are calls between 2 functions that are in 2 different compilation units.
  • A Control Coupling is not a simple interaction. It is a control flow in the calling module that ends with an interaction with another module.
• For Control Coupling, $$PRODUCT_NAME provides a brand new interactive HTML-based report.
• Worst Stack Size for C language:
• $$PRODUCT_NAME introduces this new feature that computes an estimation of the maximum stack size by computing dynamically the stack size of each function and by using static analysis to build the call graph of the application and estimate the worst stack size.
• $$PRODUCT_NAME provides a brand-new interactive HTML-based report for the Worst Stack Size.
• Code Review MISRA 2004 update:
• $$PRODUCT_NAME MISRA 2004 now covers 114 rules (+12) including 99 required rules (+8) and 15 advisory rules (+4).
• $$PRODUCT_NAME includes also 15 custom rules that are not part of MISRA but that can offer a good complement to MISRA 2004:
  • Functions should have less than '100' lines.
  • Functions should have less than '15' V(g) complexity.
  • Identifiers should not be ambiguous because of possible character confusion.
  • Identifiers should not be ambiguous because of possible character repetition.
  • Use the const qualification for pointer variable if not used to change the pointed object.
  • Global variables should be initialised.
  • Avoid implicit bitwise operator precedence in expressions
  • Expressions that are effectively Boolean should not be used as operands to operators other than (&&, || and !).
  • Ternary expressions '?:' should not be used.
  • Expressions should not cause a side effect assignment.
  • Boolean expressions should not contain side effect operators.
  • The return keyword should not be used in a conditional block.
  • The else keyword should be followed by a compound statement.
  • A constant should not be used as a switch expression.
  • All functions should be referenced.
• $$PRODUCT_NAME MISRA 2004 now includes a Qualification Kit.
• Qualification Kit:
• New Qualification Kit for Unit test C and Ada, Coverage C and Ada (HTML reports with improvement in differences between references and obtained results).
• The Qualification Kit supports now MISRA 2004
• $$PRODUCT_NAME Eclipse IDE improvements:
• $$PRODUCT_NAME Eclipse IDE now supports assembler files in the build process.
• $$PRODUCT_NAME Eclipse IDE allows to execute PTU files in the build process.
• $$PRODUCT_NAME supports UTF-16 G/C++ files
• A new TDP for Microsoft Visual C/C++ 2017 in now included in $$PRODUCT_NAME
• List of the platforms supported by $$PRODUCT_NAME:
• Windows 7 Pro (64 bits)
• Windows 10 (64 bits)
• Windows Server 2016 (64bits)
• Red Hat Enterprise Linux 6.0 (64 bits)
• Red Hat Enterprise Linux 7.0 (64 bits)
• SuSE Linux Enterprise Desktop 12 (64 bits)
• SuSE Linux Enterprise Desktop 15 (64 bits)
• Ubuntu 16 (64 bits)
• Ubuntu 18 (64 bits)

• Better support for C/C++
  • $$PRODUCT_NAME supports C/C++ language as defined by the ISO/IEC 14882:2017 ("C++17") standard and can be configured to accept earlier versions of the standard (examples: ISO/IEC 14882:2014, ISO/IEC 14882:2011 and ISO/IEC 14882:2003).
    It also supports C language as defined by the ISO/IEC 9899:2011 ("C11") ISO/IEC 9899:1999 ("C99") and ISO/IEC 9899:1990 ("C89") standards and the 'Embedded C' extensions of ISO/IEC TR 18037.
  • $$PRODUCT_NAME also supports compatibility modes for some of the most popular compiler dialects:
    • A Microsoft C and C++ compatibility mode, which provides the extensions supported by the Microsoft Visual C++ compiler (through Visual Studio 2015, including the C++/CLI features), along with various features and bugs.
    • A GNU C and C++ compatibility mode, which provides the extensions supported by GCC (versions 3.2-5.3), along with various features and bugs.
    • A Clang C and C++ compatibility mode.
    • A Sun C++ compatibility mode.
    • A cfront-compatibility mode, which emulates the old AT&T cfront processor.

• New Qualification Kit for Unit test C and Ada, Coverage C and Ada (HTML reports with improvement in differences between references and obtained results).

• Test Realtime is now available for 64bits Windows 7, Windows 10, and Linux. Read the release note for details.
• Test Realtime For Eclipse IDE offers a more compact Call Graph with colors for call paths and sister methods of selected stubs.
• Possibility to create stub behavior from Test Harness stub tab.
• A search for header/source/lib file paths has been added to search short cut. So copy/paste can be done to fill build setting directories.
• TestRT_test is a new command line allowing to build test with instrumentation, and generate report for legacy testing components. Build options and tested files can be listed into test script itself allowing to use this command into proprietary makefile, and build it in a unique command line.
• TestRT_test --help provide online detailed help for attolcc and TestRT_test commands.
• attolcc4 allows to wrap local variable for testing purpose. So variable local to a method can be checked by the test case.
• studio metrics includes now SFIN and SFOUT metrics.
• Preliminary support of Ada 2005 and Ada 2012 has been added:
  • limited keyword in limited with is silently ignored
  • attolada parsing can be stopped and resumed by inserting --#pragma attol stop_analyze and --#pragma attol start_analyze respectively.
  • in combination with the previous extensions, code can be written to be understood only by the attolada parser using --!attol!--<your on own Ada code>.
  • pre and post conditions are accepted or can be ignored using the stop/start_analyze or rewrote using alternate code.

• 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::$$PRODUCT_NAME::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

• $$PRODUCT_NAME 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 $$PRODUCT_NAME Studio user interface, test scripts, and command-line tools continue to be supported alongside the new environment.
• $$PRODUCT_NAME 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 $$PRODUCT_NAME 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 $$PRODUCT_NAME 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 $$PRODUCT_NAME 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