STRIDE 4.1.03x: Difference between revisions
Line 67: | Line 67: | ||
* [[s2scompile|STRIDE Compiler]] does not omit an error on multiple constructors in a test class | * [[s2scompile|STRIDE Compiler]] does not omit an error on multiple constructors in a test class | ||
* [[STRIDE Runner]] ignores annotation commnets | * [[STRIDE Runner]] ignores annotation commnets | ||
* [[ | * [[Test Point Testing in C/C++ |Test Point]] wait/check with no expectations leaks resources | ||
* [[ | * [[Test Point Testing in C/C++ |Test Point]] check with no expectations hangs | ||
''The following Runtime files have been modified:'' | ''The following Runtime files have been modified:'' |
Revision as of 22:25, 2 June 2010
This page documents the changes in STRIDE version 4.1.03x (code name Campgrounds).
Please review this information before upgrading from an earlier version.
Note that if you are upgrading from a previous installation you must uninstall your existing STRIDE before installing version 4.1.03x. |
What's New
Based on customer feedback, in this release we have many key usability improvements and bug fixes.
Usability Improvements
File Transfer Support
The STRIDE Runtime along with STRIDE Runner have been enhanced with a set of file IO APIs to facilitate the transfer of files between the host and the target device.
Improved Test Points Support
The implementation of Test Points in the STRIDE Runtime has been enhanced for better usability support.
Test Unit Termination
To allow termination of Test Unit execution a new test macro, srEXIT, has been introduced.
Change Details
Fixes
This section describes defects which have been corrected in STRIDE and the customer tracking number associated with them, if any, in brackets [].
- The license files could be overwritten on Linux with roaming home directories.
- In Windows SDK timer resolution was set too high.
- [1553] char, signed char and unsigned char were not recognized as different types
- Generated IM might omit a warning when compiled.
- STRIDE custom rules for Visual Studio were run every time.
- In STRIDE Studio Trace Views had several minor defects.
- In STRIDE Studio external databases were not handled properly.
Test Points
- A Test Point now supports optional binary or string payloads.
- The check/wait on Test Points now is always exclusive against "my set of Test Points" defined with two groups - expected and unexpected.
- To validate the payload associated with a Test Point now requires the use of a predicate.
Intercept Module
- The explicit Name Mangling macro imINTERCEPT macro has been deprecated in favor of the new more intuitive srTEST_INTERCEPT. Both of them behave the same way.
Samples
- All samples were update.
- A new FileServices sample has been added.
Runtime
- STRIDE Host Release 4.1.03x is compatible with the Runtime Version 4.1.03
- Most of the Runtime files have been modified. It is recomended that you update them all.
- All Linux SDK files have been modified.
- All Windows SDK files have been modified.
Minor and Patch releases
4.1.03a
New features and improvements:
- STRIDE Compiler now allows DOS style ("/"-prefixed) options
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- STID release in STRIDE Runtime may cause a crash
- STRIDE Compiler may reject valid C++ syntax
- STRIDE Compiler may crash on template class compilation
- STRIDE Compiler does not omit an error on multiple constructors in a test class
- STRIDE Runner ignores annotation commnets
- Test Point wait/check with no expectations leaks resources
- Test Point check with no expectations hangs
The following Runtime files have been modified:
srmsgrt.c srtest.c
4.1.03b
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- Use of Test Code Macros may cause annotation errors in the report.
- STRIDE Studio may incorrectly render trace return entries for reentrant interfaces.
The following Runtime files have been modified:
srtestutil.h srtest.c srtestutil.c
4.1.03c
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- Test Point data are incorrectly HEX encodded in associated report annotations
- Concurrent use of Runtime Test Services may cause "pointer setup duplicated" errors
- Passing invalid arguments to File Transfer Services may cause crashes in the Windows version of STRIDE Runner
- Linux SDK may error out on SLAP header verification
- In Windows SDK and Linux SDK the serial port is constantly polled
- STRIDE Studio is unable to auto detect dynamic COM ports
The following Runtime files have been modified:
srcfg.h srtestutil.h srtest.c srutil.c srtestutil.c
The following Windows SDK files have been modified:
palIO.c
The following Linux SDK files have been modified:
palIO.c