© Copyright International Business Machines Corporation 2008. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
None
None
In a component Testing for C or Ada script, if comments are used in test with loop then these comments are duplicated many times in the report, which might cause the user interface to fail to display the report.
On a source code line containing double comments, Code Coverage shows a magnifying glass where there is no need.
Test Script generator generates duplicate definition of global variables when testing Static/Private data (##including the *.c file).
The statement "STUB my_array 1...3 => ( {1,2,3} )" with 3 dots should fail with a syntax error message.
When creating a new test script using the Component Testing for C Component Test Wizard, SERVICE blocks are created for functions that were not selected while working through the steps of the wizard. If there are functions in the file whose names are a subset of the name of the selected function, SERVICE blocks are generated for these functions in the test script file.
Test reports for a Component Testing for C test do not display the expected value for members of a structure that are pointers.
When stubbing a function that has a "signed char" array as a parameter, the array syntax cannot be used in the STUB statement. The C test script compiler will report a syntax error.
For more information, please could you refer to the Annex 1 document "Simulating Functions with char* parameters".
The test script generator might generate a DEFINE STUB block name that contains an hyphen if the name of the stubbed file contains one, which would cause an syntax error when parsing the test script.
Multiple C style comments in a single line distorts MC/DC coverage result.
Test script compiler fails to correctly analyze the declaration of an array of which the size is defined using an enum.
None
None
None
When Rational Test RealTime 7.0.5 Eclipse plugin is installed on Rational Systems Developer 7.0.5 on Solaris 10 then, when opening the Test execution test log, the Eclipse UI freezes.
When using Test RealTime within Eclipse, and when trying to create a new component test for C, then selecting "create only C test component" in the wizard, then going to the next page, and then back again, and selecting "create empty test component", in that case, the Finish and Next buttons are grayed out. Therefore, generating the test is not possible. Workaround: Close the wizard and start over the test creation.
In the test suite editor in Eclipse for component testing for C on Linux, the initial height of the Test elements view is too small. Workaround: click two times on the test element arrow to change the height back to normal.
When performing runtime analysis and if the report is already open, adding Code Review in the settings, and rerunning, then the Code Review report is not opened automatically , even when double clicking on the results.xtp.
Workaround: Close the report and open it again by double-clicking on the results file.
The user interface does not detect TDPs contained in a directory whose name includes a Japanese character.
On a Japanese PC using Windows, if no valid licenses are found or the license is going to expire, then a dialog will pop up and display a warning message that is corrupted. There is no clear indication of what user should do to resolve the license issue.
The selection of scenarios in the Virtual Tester Driver List (Tab Scenario) does only work with the mouse.
In the user interface (studio), changing a setting might cause the entire setting to disappear in some cases. For example, in the section "Linker" > "Additional objects or libraries" click on the ... to open up the edit window. In this window, you will see that the list of objects is duplicated. Delete part of the setting and click on OK. The settings window will be empty.
On SuSE Linux Enterprise Desktop (SLED) or SuSE Enterprise Linux Enterprise Server (SLES) 10 and 10SP1, Studio will abnormally terminate if Syriac fonts are used.
Exporting the metrics report using the menu entry File > Export might result in an abnormal termination.
Workaround: Use the menu entry Metrics > Generate HTML.
None
None
None
None
None
None
None
None
Code Coverage shows a statement as executed after the "long_jmp" function, or after the function that calls the "long_jmp" function.
System Testing script compiler does not generate ATL_TIMEOUT value when WTIME is only in the OK part of the WAITTIL statement.
The TDP runtime for ADA defines a default "epsilon" value (for float types 1.0e-5, and for double types 1.0e-14). If the user defines a delta smaller than this, this would have no effect. Any result within the range of the TDP "epsilon" would be accepted as correct. The smaller range of the "delta" is not applied.
Workaround: Modify the "epsilon" value of the TDP runtime.
When performing a clean build of a Component Testing for C test script, a warning is sometimes reported by the compiler when compiling the image.c file.
When having a customized TDP that deals with the @ symbol, then the @ symbol can no longer be used for "const" parameters of a DEFINE STUB statement.