| Version 2.1 (R2008a) SystemTest™ Software Release Notes | |
This table summarizes what's new in Version 2.1 (R2008a):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
| Yes Details below | Yes Summary | Bug Reports Includes fixes | Printable Release Notes: PDF Current product documentation |
New features and changes introduced in this version are:
You can now override individual Simulink® Inport block signals via the Simulink element.
In the element, you can map test signals to individual Simulink Inport blocks using the new Override Inport Block Signals with SystemTest Data section on the Mappings tab.
For information on using this feature, see Overriding Inport Block Signals in the SystemTest™ documentation.
When you select Inherit from model as the mapping for an individual Inport block, it will not support models that defined their ExternalInput as expressions of t, time series, Simulink Time Series, or TSArray.
Individual Inport mappings restricts the dimension of the mapping variable to a vector (dimension = 1).
The Simulink element has been updated to use collapsible panes for the different mapping options, offering better usability within the element. Any mappings from previous TEST-files are loaded into the appropriate collapsible pane. The four collapsible panes consist of:
Inport Block Signals (new feature – Importing Simulink Inports)
Block Parameters
To Workspace Variables
Outports
In previous releases, when loading TEST-files, Simulink models associated with a Simulink element were not automatically loaded into memory during load time. In Release 2008a, the Simulink element will now load its model during load time, which is indicated by the load progress bar.
In previous releases, the Simulink element would not recognize To Workspace blocks stored within locked masks or block parameter fields for sample time, data type, and scaling. These options are now accessible through the element.
After you run a test that includes results you saved using the Saved Results in the Test Browser, you can view the results in MATLAB® using a test results object. This feature is useful for comparing the results of separate test runs and for postprocessing of test results.
After running a test, a MATLAB variable named stresults is made available, allowing you to access the test results object and work with the data in MATLAB. One of the main advantages to accessing test results in the command line is that all of the MATLAB plotting tools are available to use on the results data. You can plot the data using any of the plot types MATLAB offers.
Another major use of the test results object is to quickly access and view your results in the form of a dataset object. The dataset object offers a convenient form for managing and displaying a large amount of data.
For information on using the new test results object, see Accessing Test Results from the MATLAB Command Line in the SystemTest documentation.
In previous releases, test results were not accessible during test execution. In Release 2008a, the most current test results can be accessed at any time in the test by using the systest.testresults.getCurrent function.
In previous releases, test results were managed in an undocumented MATLAB structure accessible as a variable named "stresults" or from the test results MAT file. For Release 2008a, the test results are now managed as a documented test results object. Any dependencies on the previous undocumented test results format will need to be updated to use the new test results object.
For information on using the new test results object, see Accessing Test Results from the MATLAB Command Line in the SystemTest documentation.
In this release, three test vector types are now available, described as MATLAB Expression, Spreadsheet Data, and Probability Distribution. Test vector data for TEST-files from prior releases will be loaded as a MATLAB Expression test vector type.
The Probability Distribution support now recalls the configuration values used to generate the distribution, avoiding the need to re-enter the configuration values when a distribution needs to be edited.
The Probability Distribution test vector now uses default values for its fields. Previous versions configured the fields blank. You can replace the defaults with the values you want to use.
You can now choose to reuse test vector values each time a test is run. This is useful for Monte Carlo testing when used in conjunction with the new Probability Distribution test vector type. To reuse test vector values, do not check the option called Evaluate Test Vector each time the test is run when configuring a Test Vector.
In previous releases, test vector values were always reevaluated upon loading and running the test. To maintain this behavior, in Release 2008a, any existing TEST-files will be loaded with their test vectors configured to Evaluate Test Vector each time the test is run, which is the new configuration option for test vectors. Any new test vectors created though will, by default, not be configured to re-evaluate each time the test is run.
A new test vector type, Spreadsheet Data, is now available to read data from Excel® files into the SystemTest software. You can import data from multiple files, and can read whole sheets or a subset of a sheet.
For information about using this feature, see Creating Spreadsheet Data Test Vectors in the SystemTest documentation.
If a file has been added to a Spreadsheet Data test vector, any changes within the file (i.e., sheets being renamed, added, or removed) will not be automatically reflected within the SystemTest software. To have the SystemTest software reflect the change, remove the file from the test vector and then add it back.
Specific rows/columns from a Spreadsheet Data test vector can be selected using a new mapping option provided in the Simulink element's Override Inport Block Signals with SystemTest Data option on the Mappings tab. This selection option is not currently supported for other Simulink mapping types or other test elements.
The Spreadsheet Data test vector is officially supported on Windows® platforms and can read all Microsoft® Excel® spreadsheet files. This also includes CSV Files. On platforms other than Windows, the SystemTest software only supports reading XLS files and does not support CSV files.
The following undo/redo actions are not currently supported for the Spreadsheet Data test vector:
Adding, removing, moving up, moving down, selecting, or unselecting of files/spreadsheets
Any edits made on the String Mappings tab
The Spreadsheet Data test vector stores the absolute path to any files added. If the file changes location, even if the file is still on the MATLAB path, it will not be found. You should remove and add the file again if the location or name changes.
The other two test vector types (MATLAB Expression and Probability Distribution) clear their values and set their length to 0 whenever an "Evaluate" fails. For the Spreadsheet Data test vector, if an "Evaluate" fails, then the last known values, headers, and string replacements remain and will only be updated when an "Evaluate" is successful. This can lead to discrepancies between the actual values used and the way the Spreadsheet Data test vector user interface is configured.
For example, if the test vector successfully reads Column A, the values are stored, etc. If the test vector is configured to read Columns B to C, and that leads to an error somewhere, the text fields will still show Columns B to C, even though the values that would be used are from Column A.
In this same example, a failed evaluation would put the test vector in error. However, if you save and then reload the test vector, the error state is removed. Therefore, you could have saved this test vector reading from bad data in Columns B to C, and then reload and the red error borders are gone. When it runs (if you do not re-evaluate each time the test is run, or manually, before hitting the Run button) it will use old values from column A, even though the information in the Test Vectors pane says Columns B to C.
The overall UI for test vectors and test variables has been redesigned into a table and embedded edit area, offering easier management and interaction. By default, the test vectors and test variables are no longer docked in the bottom left of the desktop. Instead, they are docked in the middle pane along with the Properties pane. A listing of test vectors and variables are also provided in the Test Browser.
The list of test vectors in the Test Browser will always reflect an alphabetized order, regardless of their order in the Test Vectors edit pane. The test variables tree is not currently alphabetized and will reflect the order from the edit pane.
Multiple test vectors can be selected in the edit pane to allow for multiple test vector evaluation or deletion. Multiple test vector editing though is not currently supported.
The following changes have been made.
TEST-files are being saved in a new internal binary format as of Release 2008a. Files from previous releases are compatible with 2008a and can be loaded without any problems. TEST-files saved in Release 2008a will not be loadable in previous SystemTest releases.
The results MAT-file generated by the SystemTest software, or those saved by the Test Results Viewer, stores data in the form of a new test results object for Release 2008a. These result MAT-files are not loadable by previous SystemTest releases.
The desktop toolbar has been updated to offer a more concise set of options.
The Run and Stop buttons have been relocated toward the right end of the toolbar.
The buttons that launch the Test Results Viewer, Test Report, and Simulink have been removed. These options continue to be available from the menu bar.
The Current Directory chooser at the top of the desktop has been removed. The current directory can still be changed by using the MATLAB desktop Current Directory chooser.
A progress bar has been introduced providing status when TEST-files are loaded.
The Run Status progress bar has been updated to an indeterminate bar, suggesting ongoing testing when working in distributed mode. The new progress bar no longer displays the percentage complete. Information on current progress is still provided via the status text above the progress bar.
The New button in the Test Browser pane, originally used to add elements, can now be used to add elements, test vectors, and test variables.
Three reserved names have been introduced, restricting the names that can be used for Test Vectors, Variables, Saved Results, or Derived Results (created in the Test Results Viewer). These reserved names are:
ObsNames
Properties
VarNames
Any existing TEST-files that use these names will be loaded with a warning indicating what alternate name is being used in place of the restricted name.
With the addition of a new test results object for exploring and analyzing test results, by default, the Visualize and plot saved results by launching the Test Results Viewer option is turned off when new TEST-files are created. The option is still available in the Test Properties pane.
The default desktop layout no longer displays the Elements pane by default. It is still available via the Desktop menu.
The Test Results Viewer currently supports viewing scalar, vector, time series, and image data. It is not currently compatible with any other data formats. Attempting to load other data formats will produce an error. In particular, using the new Spreadsheet Data test vector to read in multiple columns/rows of data, producing a matrix of values for each test iteration, will likely not be loadable by the Test Results Viewer. It is recommended the new test results object, which is compatible with all data formats, be used instead to view and analyze test results.
When configured to launch, the Test Results Viewer would always launch at the end of a test, even when the test was unable to run to completion or if there were no test results to view. In Release 2008a, the viewer will only launch if the test runs to completion and if test results are being saved. Otherwise the request is ignored.
| SystemTest Release Notes | Version 2.0 (R2007b) SystemTest™ Software | |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |