Release Notes TPT 10 TPT 10U3 TPT 10U2 TPT 10U1. Declaration Editor. Bug Fixes

Size: px

Start display at page:

Download "Release Notes TPT 10 TPT 10U3 TPT 10U2 TPT 10U1. Declaration Editor. Bug Fixes"

Prosper Flowers
5 years ago
Views:

1 Release Notes TPT 10 TPT 10U3 Bug Fixes Bug fix while running files via console or batch tool, if these file had references to other TPT files (libraries). Bug fix while opening old TPT files via API. Bug fix while terminating parts of a test step list, that are embedded in a while-wait-loop when this while-wait-loop is terminated because a higher level part of the test is terminated. TPT 10U2 Bug Fixes Build Progress pause button bug fix. The pause button now pauses the test execution anytime. Bug fixes in TASMO regarding the state-flow instrumentation that caused, under certain circumstances, changes in the model semantics. Bug fix to avoid changes in the MATLAB startup script when upgrading from TPT9 to TPT10. Bug fix when setting breakpoints in PLS UDE. Break points are now set correctly. Bug fix for Python range function data types. Now all data types are supported. TPT 10U1 Bug Fixes Bug fix in the Signal Comparison assesslet. When you enter both an absolute and a relative tolerance to the Signal Comparison assesslet, those tolerances are no longer added up. Instead, the minimum of both tolerances is taken. Bug fix in the report path. In some cases, the report path was too long for Windows systems when composed of test case + test data directory + relative path for the report. The report could not be opened from the build progress. Now the report path is normalized and report opens always from the build progress. Bug fix in the documentation field for all step types to avoid execution error in some cases. Declaration Editor - 1 -

The Declaration Editor has been completely redesigned. Figure 1: Redesigned Declaration Editor Direct display and edit of mapping flavors (scaling, rename,...).

2 The Declaration Editor has been completely redesigned. Figure 1: Redesigned Declaration Editor Direct display and edit of mapping flavors (scaling, rename,...). Direct manage and edit of equivalence classes. Set interface roles directly (IN/OUT/LOCAL). Multi-editing supported. You can switch between the decimal, binary, and hexadecimal representation of an integer. Global undo (CTRL+Z) and redo (CTRL+Y) affects also actions made in the Declaration Editor. You can show and hide columns in the Declaration Editor. shortcuts to create channels (CTRL+1), parameters (CTRL+2), constants (CTRL+3), measurements (CTRL+4), and assessment variables (CTRL+5). The single elements of a struct are now displayed as an expandable list in the Declaration Editor

3 Figure 2: Display of a struct in the Declaration Editor The values of string channels are now displayed. Min and max values for a struct or an array can also be scalar values that apply to all elements of the struct or array. Initial values can be set for: Channels by using an Init Values mapping flavor. Individual test cases by using the Initial Values view. Equivalence Classes Equivalence Classes Editor. Direct editing of all equivalence class sets in the Declaration Editor. Equivalence classes can be accessed in assessment scripts. You can use the representative values of an equivalence class in assesslets: print light_intensity->ec.bright.min. Auto-completion is supported

Sets. Figure 4: Select equivalence classes Equivalence classes can be

4 Figure 3: Equivalence classes set in an assesslet with auto-completion You can automatically generate test cases from subsets of Equivalence Classes Sets. Figure 4: Select equivalence classes Equivalence classes can be defined as mandatory or forbidden in the Equivalence Classes assesslets

5 Figure 5: Equivalence Classes assesslet Mapping Editor The Mapping Editor has been redesigned

Figure 6: Mappings with selected flavors Bug fix If a mapping with Init Values flavor specifies initial values for constants or system constants, these initial values will be now considered during

6 Figure 6: Mappings with selected flavors Bug fix If a mapping with Init Values flavor specifies initial values for constants or system constants, these initial values will be now considered during test modeling and test assessment. As a consequence, system constants can be specified in the "System constants" settings of the platform as well as in the Init Values mapping flavor. If the value of a system constant is specified in the "System constants" settings and in the Init Values mapping flavor, the value must be identical to avoid conflicts. Import Interface Instead of remove, you can hide a signal during the interface import if this signal is declared in TPT but cannot be found in the external interface. Import and Export - 6 -

TPT can import array elements from MDF files as array. The import can be configured in the Preferences dialog, TPT Model Behavior section. Comment information from MDF3 is imported as string.

7 TPT can import array elements from MDF files as array. The import can be configured in the Preferences dialog, TPT Model Behavior section. Comment information from MDF3 is imported as string. MDF4 event blocks are imported as string variables. These string variables are also displayed in the Test Data Viewer. Test step list A new test step has been added, the Table step. You can use the Table step to set and check signals in form of a data table. You can also copy and paste data from the Table step into EXCEL files. Figure 7: Table step Each step in the step list has its own documentation field. This field is only visible when the step is selected or when text has been entered in the documentation field. The Ramp channel step can now ramp parameters

8 Figure 8: Ramped parameter A Testlet step in another Testlet step does no longer need to be a child node of the referencing testlet. Referencing the parent and cycles (recursion) still forbidden. Figure 9: Testlet step in another Testlet step Inside the step list, the set If, Else, While, and the Parallel steps can now be expanded and collapsed

Figure 10: Collapsed and expanded steps If and Else steps are only used when they have been checked by the pre-compiler and have been found reachable. Test cases can be generated from value ranges.

9 Figure 10: Collapsed and expanded steps If and Else steps are only used when they have been checked by the pre-compiler and have been found reachable. Test cases can be generated from value ranges. The values are derived from mapping flavors. You can modify the step size, start, stop, and quantization value for the generated step list variant. You can use mapping information of test platforms by typing the channel name and flavor and set a ->. For example: light_intensity > light_intensity->min. Figure 11: Mapping information used in a test step Bug fix Bug fix in auto-completion in the test step list. Bug fix in global search performed in different test step list fields. Bug fix in multiple selection in test step lists. Platforms You can now add custom Python scripts to the platform configuration. The scripts run either before or after the execution of the platform / test cases. The following execution platforms support additional Python scripts: ASCET, ASCET@FUSION, dspace HiL@FUSION, EXECUTION, and Stand-alone

Figure 12: Python scripts in the Platform Configuration dialog ASCET You can now extract the SUT interface, generate the test environment, and configure ASCET via the RMI API.

10 Figure 12: Python scripts in the Platform Configuration dialog ASCET You can now extract the SUT interface, generate the test environment, and configure ASCET via the RMI API. option "Limit channels and parameters" in the platform configuration lets you limit the physical values of channels and parameters to the bounds of a Min/Max flavor. ASCET@FUSION: Parameter are read back from the SUT. That is, in case parameter values are limited or changed in the SUT, TPT reads the limited value. ASCET@FUSION: Support of quantized physical experiment. ASCET@FUSION: Support of different implementations. ASCET@FUSION: You can set individual task counter names. ASCET@FUSION: The order of tasks/processes is no longer limited. ASCET@FUSION: You can specify "round" or "cut" for calculations of internal values (scaling). Bug fix TPT 64bit can now communicate with ASCET. VERISTAND TPT checks whether the signals from a TPT project file are present on the HiL. The test cases are executed only when all signals given in the TPT project file can be found on the HiL. FUSION

11 section in the FUSION platform configuration, named "Advanced Options", to specify the runtime and the debug options. Parameters in FUSION have now read-write semantic, so the values of parameters can be read back from the SUT via FUSION and become a part of the test data. 64bit DLLs can be used. MS.NET Assembly Node = Custom Node.NET DLL Changed The name of the MS.NET Assembly Node has been changed to Custom Node.NET DLL. MCD3 client node You can now specify how many times TPT should try to connect to the controller if the initial connection breaks down, and how many seconds take between each attempt to reconnect. INCA node The initialization process for the INCA Node has been optimized, depending on whether it is the first or last test case, and whether the FUSION is in CompileRun or ExecuteRun. An INCA connection establihed by TPT does not try to connect again (re-initialize) when the same script is executed a second time. You can suppress the initialization of INCA if INCA has already been started and configured and a test has to be executed several times. The INCA node supports array signals and measurements. INCA array measurements are now also array channels at TPT. PLS UDE node You can now read from bit fields or write to bit fields, that is from and to consecutive bits of the whole value by using: UDEvariablename.[lastBit:firstBit]. You can specify to open a given Executable and Linking Format file (ELF) automatically when the UDE is opened. If the ELF code is generated with CTC++, also code coverage is possible. The bitcov add-on by CTC is needed to use this feature

12 The code coverage done with CTC++ on the UDE debugger target can be integrated in the HTML report of TPT. You can set the maximal timeout for waiting that UDE stops at a specified breakpoint by setting a breakpoint timeout in the node configuration. LABCAR [NEW] A new platform has been implemented, called "LABCAR Platform". It runs TPT test cases via the FUSION and exchanges the signal data with the LABCAR OPERATOR (LCO). The measurement and calibration is done via INCA. You can configure error-simulation with PinControl (ES4440). dspace HiL@FUSION [NEW] Figure 13: PinControl

13 A new platform has been implemented, called "dspace It runs TPT test cases via the FUSION in non-realtime on a dspace HiL environment. Communication is performed using the ASAM XiL-API. Support of Scalexio HiL, 1005, and MATLAB MATLAB2016b supported. Better support of TargetLink Data Dictionaries. TargetLink subsystems built from a library are supported by TPT for automatic test frame generation. TPT environment variables are now written to the MATLAB workspace. In conjunction with the MATLAB platform, the MinGW 64 bit is supported in TPT. TPT can handle the Simulink.LookupTable that holds explicit values and the Simulink.Breakpoint that represents an axis of a Simulink.LookupTable. LookupTables are imported to TPT as a map or curve. Breakpoints are imported to TPT as an array. The LookupTable references the array. TPT can connect to resettable subsystems in MATLAB to analyze the subsystem's interface and to generate the test frame. Instead of memory blocks in the test frame, unit delay blocks (1 / z) are generated. This way, the sample time can be precisely set to correspond to the sample time set in TPT stepsize. Parameters in referenced Simulink models are taken into account by TPT during the import. Coverage with V&V is always cumulative. When using the "Report only" option, you need to define the coverage settings. Coverage measurement is possible for referenced models. Bug fix Interface import and test frame generation works properly for function-call subsystems where the function option "sample time type" is set to "periodic". The function-call signal is no longer imported as a TPT channel. Simulink.Signal objects referenced in data store memory blocks are now handled correctly when writing parameter values. When you apply a mapping with rename flavor in TPT to parameters, the external name of these parameters is now used when reading them from the MATLAB workspace or writing to them in the MATLAB workspace. When you copy a MATLAB platform setting from one TPT project file to another TPT project file, the "Vector Start Index" and the "Treat Vector as" settings are copied correctly. TPT can now handle the dimension of a boolean array in MATLAB interfaces. Bug fix in the display of bus signals with many signals

14 Bug fix with long strings in the test frame generation for the MATLAB platform. Bug fix in the parameter import from Targetlink models. TASMO TASMO is more robust and faster, and supports more Simulink blocks for coverage goals. TASMO supports decision coverage for the following blocks: Sign (Simulink, TargetLink), Relay (Simulink, TargetLink), and Dead Zone (Simulink). TASMO supports decision and condition coverage for Stateflow Truth Tables. You can filter subsystems by block type and coverage criteria in the "Select Coverage Criteria / Goals" dialog section. signal characteristic named "Constant" has been added. When used along with other types, for example with "Step" or "Sine", the generated signal can have constant sections. Figure 14: Charateristics in TASMO TASMO performs a static analysis of the test model before the test data generation to detect nonreachable coverage goals. TASMO can analyze existing test cases and achieved coverage during the normal test execution to avoid redundant test data and to increase the coverage goals. The coverage information of the test cases generated by TASMO can be exported from TASMO into a CSV file. You can reuse this CSV in EXCEL to set up your own statistic

15 TASMO supports parameter changes in the test data generation. TASMO can generate test data as linear step lists or as parallel step lists. Requirements Figure 15: Select a test step type in TASMO TPT10 supports DOORS 9.6. You can deactivate in the Advanced Report option in TPT, that a requirement which is not linked to any assesslet, derives its result from a test case. When this option is deactivated, the requirement is set to "not covered" instead of "inconclusive". TPT can handle the URI Object attribute from DOORS. URI Objects are links. The link is displayed in the Requirements view with the requirement and now also in the "Meta Information" section of the report. Changed For better visibility, the position of the number located in variant and test case icons that shows how many requirements are linked to that specific test case or variant has moved upward. The requirements result of several execution platforms are displayed in a single report table; the pie charts show the results of the different execution platforms combined

Figure 16: Requirements results table The "Report Linked Requirement" displays more information, for example about the kind of link (direct, inherited).

That is, they do no longer affect the coverage statistics and are no longer displayed in the report.

16 Figure 16: Requirements results table The "Report Linked Requirement" displays more information, for example about the kind of link (direct, inherited). Figure 17: Report shows if the link to a requirement is direct or inherited Bug fix Non-requirement objects requirements are now ignored when using a REQUIREMENTS.checked() function. That is, they do no longer affect the coverage statistics and are no longer displayed in the report. When you import linked objects (test cases, variants, assesslets) of a deleted requirement, the objects are now marked as "Needs to be Reviewed". When you link a TPT element such as a test case, variant, or assesslets to a non-requirement object (objects that are not requirements, like a description), the non-requirement object becomes a requirement. When you remove the link between the TPT element and the former non-requirement object, the former non-requirement becomes a non-requirement object again

Assessment The Jython version has been migrated to Jython 2.7, thus TPT can now load DLLs at assessment time. There are also new libraries available like ctypes.

17 Assessment The Jython version has been migrated to Jython 2.7, thus TPT can now load DLLs at assessment time. There are also new libraries available like ctypes. The Assessment Library is now a regular feature and has been moved to the Preferences dialog. The Assessment Library is used to set paths to custom assessment scripts that can be used in all TPT projects of a TPT installation or only for a specific TPT project. The Assessment Library has file extension *.tptpy. dialog to select variables in assesslets (Min/Max, Signal Comparison, Equivalence Classes). Figure 18: Select variables in an assesslet You can use the mapping information of test platforms by typing the channel name and flavor and set a "->". For example: light_intensity > light_intensity->min. Figure 19: Mapping information used in a Script assesslet You can increase the context interval by positive arguments or reduce them by negative arguments with the new assessment function TPT.extendContextRel (before, after). In STRICT mode, undefined inputs lead to undefined results

18 TPT.boundControl(), TPT.boundControlRel(), TPT.hose(), TPT.deviation() with STRICT mode. The new option in assesslets tree "Copy the Structure of the Selected Test Cases" creates assesslet groups that are structured with regard to the test case groups. The corresponding linked assesslets are sorted accordingly. Figure 20: assesslet structure operator "=~=" that compares two signals with respect to a tolerance. The tolerance is taken from the scaling information of the test platform (mapping). For example: a channel light_intensity with a mapping tolerance of +/-0.05, slope 0.1: (light intensity =~= myval) is true for myval-0.05 <= light_intensity <= myval The semantics of the gettolerance() function also considers that the ScalingMode can be OFF. This influences the signal comparison when: A tolerance for the least significant bit (LSB) is specified. The new =~= operator that compares a signal with the scaling tolerance is used. The function myvar.gettolerance()is used in an assessment. The names of assesslets tree elements that are created, copied or duplicated and have the same name as another assesslet tree element, are automatically extended by an underscore and a number to ensure the uniqueness of the name. Shorter descriptions is possible for the TPT.checkAlways() function

19 Figure 21: TPT.checkAlways() Changed When you redefine signals in an assessment in a specific time interval, the results of the other time intervals remain as they were (passed, failed, or inconclusive). Condition Tree assesslet You can disable and enable single checks by selecting the "Enabled" check box. The checks can also be set using the context menu or the shortcut F4. Bug fix Fix memory leak in Condition Tree assesslet. Bug fix in Conditional Tree assesslet when exporting an assesslet from the Test Data Viewer to the Assesslet view. Conditional Tree assesslet bug fix with copy and paste. Conditional Tree assesslet bug fix when an interval is not found. Trigger Rule assesslet The trigger condition can trigger an "Else check" for the intervals in which "Then check" is not true. Min/Max Comparison assesslet You can now select a mapping with Min/Max flavor in the section "Mapping for bound information"

20 Script assesslet Locally declared functions and variables can be entered via auto-completion. Figure 22: Auto-completion in Script assesslet Already declared elements are highlighted when you hover with the mouse over the script and at the same time press the CTRL key. When you click on a highlighted element, the Declaration Editor opens and directly shows the selected element, so you can immediately edit it

Figure 23: Jump from a Script assesslet directly to the Declaration Editor entry You can access Min / Max mapping flavor values from a script assesslet using foo->min and foo- >max.

21 Figure 23: Jump from a Script assesslet directly to the Declaration Editor entry You can access Min / Max mapping flavor values from a script assesslet using foo->min and foo- >max. Import Measurements assesslet Changed The check box "Use mapping from platform" has been removed. Go to the "Import" section, click and select "Use mapping from platform" from the mapping list. Report Signal graphic assesslet You can now filter signals that differ from default value to include them in the Report Signal graphic. Build Progress dialog The Build Progress dialog has been redesigned

Figure 24: Build Progress dialog The execution details tree shows also which assesslet in what time context has been erroneous and at which Compare step something went wrong.

22 Figure 24: Build Progress dialog The execution details tree shows also which assesslet in what time context has been erroneous and at which Compare step something went wrong. You can directly jump to the assesslet in the Assesslet view or in the Assesslet Content view by clicking on it in the Build Progress. The relevant signals for an assesslet can be displayed in the Test Data Viewer via the context menu entry. toolbar icons added to cancel the current execution, to create and to open the overview report, to automatically generate an overview report after every test case is run. Test Data Viewer Changed You can load several test or measurement data into an independent Test Data Viewer tab or window. Bug fix Bug fix when using several tabs in the Test Data Viewer along with structs. Report

The section "Test Case Status Summary" in the report table shows now the test case status set by you, that is if the test case is new, in progress, to be reviewed, or stable according to your

23 The section "Test Case Status Summary" in the report table shows now the test case status set by you, that is if the test case is new, in progress, to be reviewed, or stable according to your settings in the Test Case Status view. Report shows information, which project has been used for the generation of the DLL. PDF reports are now generated in landscape format for better table display. configuration options for coverage using CTC++. You can specify for which files the coverage report should be generated. Section "Code Coverage" in the report. A coverage table is displayed for each platform. When using CTC++, the statement coverage is always part of the report. Figure 25: Code coverage report section Bug fix Bug fix when opening a report from a file executed on a network drive. Dashboard Changed You can now choose to set the mode of the button widget and check box widget either to push button or to toggle button. When you want to deselect a currently selected item in the Dashboard, press ESC. Bug fix Bug fix in Dashboard with undo and redo actions. Text changes immediately in the Dashboard as soon as you enter it in the properties of a widget. Dashboard Player Simplified generation of the executable Dashboard Player file in a new format called DBPLAY. The DBPLAY files are automatically associated with the Dashboard Player

command line options to start the a DBPLAY file automatically (--autostart) and in fullscreen. button to select a TVM file in case several TVM files exist.

24 command line options to start the a DBPLAY file automatically (--autostart) and in fullscreen. button to select a TVM file in case several TVM files exist. Miscellaneous Figure 26: Choose a TVM file in the Dashboard Player command line option --noconsole to suppress any output in the command prompt. If the command prompt is associated with a parent process of the tpt.exe, the output is still generated but not displayed in the prompt. The variables that should be used in all projects of a TPT installation can be now defined in the "General" section of the Preferences dialog. Variables that should only apply to a specific TPT project are defined in a project-specific section in the Preferences dialog. Select "Enable auto line wrap" menu option in the Description view to automatically break lines. To open the most recently closed TPT file, select the new menu item "Open Most Recent". Multiple selection is now available in the project tree and the test cases tree. When you copy and paste, or duplicate an element in the project tree, the name of the element will be in edit mode to quickly enter the new name without having to use F2. The names of project tree elements (testlet, variant, test case) that are created, copied or duplicated and have the same name as another project tree element, are automatically extended by an underscore and a number to ensure the uniqueness of the name. The local and global search are now in the same search dialog (CTRL+F)

Figure 28: Formatted description in report You can assign initial channel values for every single test case, variant, and group.

25 Figure 27: search dialog Text in the Description view and Documentation steps and fields can be formatted, that is, you can change the size and color of the font or single characters, and change its style to underline, bold, or italic. The formatted text can be displayed in the report. Figure 28: Formatted description in report You can assign initial channel values for every single test case, variant, and group. Use the UP and DOWN keys in the Test Case Details view for navigation. documentation available and searchable in TPT. help view. Improved context sensitive help in TPT (F1)

effect all TPT projects of a given TPT installation, and one for the

26 Figure 29: Searchable help in TPT Changed The Preferences dialog is now separated in two sections: one for the general settings that effect all TPT projects of a given TPT installation, and one for the settings of each currently opened TPT file. Figure 30: Preferences dialog

27 The image resolution settings are directly available in the "Save image as" dialog. Bug fix Bug fix in the quick search of the project browser

Quick Reference Card Business Objects Toolbar Design Mode

Quick Reference Card Business Objects Toolbar Design Mode Icon Description Open in a new window Pin/Unpin this tab Close this tab File Toolbar New create a new document Open Open a document Select a Folder Select a Document Select Open Save Click the button to