|
|
|
| R2011b Documentation → SystemTest | |
Learn more about SystemTest |
|
| Contents | Index |
This table summarizes what's new in Version 2.6 (R2010b):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems |
|---|---|---|
| Yes Details below | Yes Summary | Bug
Reports Includes fixes |
New features and changes introduced in this version are:
You can now create a SystemTest test from Simulink. It will automatically generate relevant parts of the test based on your model. The feature automatically generates the following in your test:
Simulink element, configured properly
Test Case Data test vector, configured properly
Signals in the Test Case Editor, configured properly
Mappings of the Inports in your model
You can also automatically generate the test harness via the MATLAB command line, using new functions for this feature.
For more information, see Generating a SystemTest Test Harness from a Simulink Model.
The Test Case Editor now supports the use of buses in your model and can be used to create buses and signals within buses. The full bus hierarchy is now reflected in the Test Case Editor and you can work with the signals inside buses.
For more information, see Working with Buses
Two metrics have been added to the Model Coverage support in the Simulink element – Signal Size Coverage and Simulink Design Verifier. Signal Size Coverage records the minimum, maximum, and allocated size for all variable-size signals in a model. The Simulink Design Verifier coverage option collects model coverage data for some Simulink® Design Verifier™ blocks.
Support for External Embedded MATLAB® files was also added. It enables coverage for external functions that Embedded MATLAB functions call in your model. The Embedded MATLAB functions may be defined in an Embedded MATLAB block.
For more information, see Using Simulink Model Coverage.
The functionality of the Test Case Editor is now available via the MATLAB command line. The new functions will allow you to do the following tasks programmatically:
create test cases, signals, and segments
add test cases, signals, and segments to a SystemTest test
configure and edit test cases, signals, and segments in a test
extract test cases, signals, and segments from a test
For more information, see Working with Test Cases and Signals Programmatically
The functionality of requirements linking using Telelogic DOORS® and the Test Case Editor is now available via the MATLAB command line. The new functions will allow you to do the following tasks programmatically:
create requirements links to Telelogic DOORS® objects
add requirements to test cases in the Test Case Editor
For more information, see Creating Requirements Programmatically
In R2010b, the Test Results Viewer is no longer available from the SystemTest desktop. It can still be opened via the stviewer function.
The following have been removed from the desktop user interface:
The Visualize and plot saved results by launching the Test Results Viewer option on the General tab of the Test Properties pane.
The Tools > Test Results Viewer menu command.
In the Preferences dialog box, the confirmation warning "Warn about launching the Test Results Viewer without any saved results."
To open the Test Results Viewer, use the stviewer function in MATLAB after a test run.
The Test Results Viewer will no longer be available in a future release, even via the stviewer function. We recommend using stresults to view saved results instead. You can view the results you have chosen to save for your test using a workspace variable called stresults. It provides access to the test results object, which is useful for comparing the results of separate test runs and for postprocessing test results. For more information on viewing saved results see Accessing Test Results from the MATLAB Command Line.
For visualization of data within the SystemTest software, you can use the General Plot element and view the generated plots after a test run. For information on using the General Plot element, see General Plot Element.
For visualizing test cases and signals, you can use the Test Case Editor. For more information, see Authoring Signals in the Test Case Editor.
When you open a test that was previously configured to use the Test Results Viewer, you will get a warning dialog saying "This test was configured to open the Test Results Viewer when the test finishes running. This option is no longer available."
If you do open the Viewer using the stviewer function, you will get a warning on the command line saying "The viewer will be removed in a future release."
The following outline describes the timing of the deprecation process:
R2010b — The Test Results Viewer is no longer available from the SystemTest desktop. It can still be opened via the stviewer function.
You will receive the warnings described above.
R2011a — The Test Results Viewer will be removed. The stviewer function will produce an error stating that the Viewer is no longer available.
R2011b (or later) — The stviewer function will be removed.
The Vector Plot and Scalar Plot elements have been replaced by the General Plot element. The General Plot element supports all MATLAB plot types. You can plot any type of data, using any MATLAB plot types or Simulink data.
The General Plot element has special support for the many time-based data formats produced from a Simulink model. The supported data types include an array, a structure, a structure with time, or a time series. You can also plot Simulink data provided by test vectors, such as the Signal Builder Block test vector, the Simulink Design Verifier Data File test vector, or the Spreadsheet Data test vector.
Note As of R2010a, you could no longer create new Scalar Plot or Vector Plot elements. They no longer appear in the Insert menu or the New Element button. |
Tests containing Scalar Plot or Vector Plot elements will not automatically load with those elements. You will be prompted to convert them to General Plot elements.
For information on performing the conversion, and conversion details about the Scalar Plot and Vector Plot elements, see Deprecated Elements.
For an outline of the timing for this deprecation, see Compatibility Considerations in the R2010a section of the release notes.
In a future release, possibly R2011a, the following elements will be removed from SystemTest software:
Data Acquisition > Analog Input
Data Acquisition > Analog Output
Data Acquisition > Digital Input
Data Acquisition > Digital Output
Image Acquisition > Video Input
Instrument Control > From Instrument
Instrument Control > Query Instrument
Instrument Control > To Instrument
These elements will be removed in a future release (R2011a or later). We therefore recommend not creating new tests using these elements.
In a future release, (R2011a or later), the SystemTest software will no longer be supported on any Mac® platform, including maci64.
 | Version 2.6.1 (R2011a) SystemTest Software | Version 2.5 (R2010a) SystemTest Software |  |
Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
