STRIDE 4.1.04x: Difference between revisions
(Created page with 'This page documents the changes in STRIDE version 4.1.04x (code name ''Turnarounds''). Please review this information before upgrading from an earlier version. {| border="1" …') |
|||
(3 intermediate revisions by 2 users not shown) | |||
Line 16: | Line 16: | ||
== Usability Improvements == | == Usability Improvements == | ||
=== Tests in Script === | === Tests in Script === | ||
A new [[Test Modules Overview|STRIDE scripting solution]] has been developed to allow users to take advantage of the power of dynamic languages on the host to execute expectation and functional test scenarios on the device under test. | A new [[Test Modules Overview|STRIDE scripting solution]] has been developed to allow users to take advantage of the power of dynamic languages on the host to execute expectation and functional test scenarios on the device under test. Note: this is only available for Windows desktops. The next release will also support Linux host machines. | ||
=== File Transfer Support === | === File Transfer Support === | ||
Line 51: | Line 51: | ||
* ''All [[Linux SDK]] files have been modified.'' | * ''All [[Linux SDK]] files have been modified.'' | ||
* ''All [[Windows SDK]] files have been modified.'' | * ''All [[Windows SDK]] files have been modified.'' | ||
= Minor and Patch releases = | |||
== 4.1.04a == | |||
''New features and improvements:'' | |||
* <tt>TestPointSetup</tt> method of [[Perl_Script_APIs#STRIDE::Test|STRIDE::Test]] module has been updated to accept an optional <tt>startup_predicate</tt> parameter. | |||
* <tt>NOTE_xx</tt> logging methods of [[Perl_Script_APIs#STRIDE::Test|STRIDE::Test]] module have been updated to accept an optional <tt>test_point</tt> parameter. | |||
''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | |||
* [[Running Diagnostics With Target|Running diagnostics]] on targets without "long long" generates errors | |||
* [[Test Point| srTEST_POINT_STR8]] macro has a syntax error | |||
* Default [[Runtime_Reference#Runtime_Configuration|STRIDE Runtime configuration]] for non-complex targets results in a too big block allocation | |||
* In [[Perl_Script_APIs#STRIDE::Test|STRIDE::Test]] module test points may not be properly delivered to multiple checkers | |||
* In [[Perl_Script_APIs#STRIDE::Test|STRIDE::Test]] module trace file predicates may not be called under certain conditions | |||
* In [[Perl_Script_APIs#STRIDE::Test|STRIDE::Test]] module <tt>TEST_POINT_EVERYTHING_ELSE</tt> predicate may not be called | |||
''The following Runtime files have been modified:'' | |||
srcfg.h | |||
srtest.h | |||
srdiag.c | |||
== 4.1.04b == | |||
''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | |||
* [[Test Point|Test Points]] incorrectly filtered out on big-endian targets | |||
* [[Runtime_Test_Services#srTestCaseAddAnnotation|srTestCaseAddAnnotation]] may fail when the parrent case ID is bigger then the current suite ID | |||
* <tt>NOTE_xx</tt> logging methods of [[Perl_Script_APIs#STRIDE::Test|STRIDE::Test]] module don't use the offset time when optional <tt>test_point</tt> argument is passed | |||
* A [[Perl_Script_APIs#STRIDE::Test|STRIDE::Test]] module that passes all expectations and don't have any subsequent events will wait for full timeout before exiting | |||
''The following Runtime files have been modified:'' | |||
srtest.c | |||
srtestutil.c | |||
srutil.c | |||
== 4.1.04c == | |||
''New features and improvements:'' | |||
* Exposed a [[Runtime_Reference|STRIDE Runtime]] callback hook for capturing on target raw trace content | |||
* [[STRIDE Studio]] now allows loading captured on target raw trace content | |||
''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | |||
* Duplicate [[Test Point|Test Points]] hits when [[Expectation Tests in C/C++|expecting unordered]] may result in false positive test | |||
* A [[Perl_Script_APIs#STRIDE::Test|STRIDE::Test]] module using multiple test point handlers may result in false positive test | |||
''The following Runtime files have been modified:'' | |||
sribtr.h | |||
sribtr.c | |||
srstid.c | |||
srsuid.c | |||
srtest.c | |||
srthread.c | |||
[[Category:Release Notes]] | [[Category:Release Notes]] |
Latest revision as of 18:39, 16 April 2010
This page documents the changes in STRIDE version 4.1.04x (code name Turnarounds).
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.04x. |
What's New
Based on customer feedback, in this release we have many key usability improvements and bug fixes.
Usability Improvements
Tests in Script
A new STRIDE scripting solution has been developed to allow users to take advantage of the power of dynamic languages on the host to execute expectation and functional test scenarios on the device under test. Note: this is only available for Windows desktops. The next release will also support Linux host machines.
File Transfer Support
The set of File Transfer Services has been expanded with analogs to the C standard fgets/fputs.
Tracing
The STRIDE Runner has been extended to allow tracing on source instrumentation.
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 [].
- Generated IM might be incorrect for extern "C" function doubles
- Built-in STRIDE Runtime diagnostics require too much memory
- Default STRIDE Runtime configuration demands too much memory
Source Instrumentation
- To minimize trafic Test Points are now filtered on the target.
- Test Point and Test Log macros now support upto 9 arguments. In C++ code the "<< operator" could be used.
- STRIDE Runner now allows control of the Test Log level with the new --log_level option.
Tests in C/C++
- srLOGxx macro has been renamed to srNOTExx.
- Expectation Tests APIs has been renamed and refactored.
Samples
- All samples were update.
- A new set of tests in script samples has been added.
Runtime
- STRIDE Host Release 4.1.04x is compatible with the Runtime Version 4.1.04
- 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.04a
New features and improvements:
- TestPointSetup method of STRIDE::Test module has been updated to accept an optional startup_predicate parameter.
- NOTE_xx logging methods of STRIDE::Test module have been updated to accept an optional test_point parameter.
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- Running diagnostics on targets without "long long" generates errors
- srTEST_POINT_STR8 macro has a syntax error
- Default STRIDE Runtime configuration for non-complex targets results in a too big block allocation
- In STRIDE::Test module test points may not be properly delivered to multiple checkers
- In STRIDE::Test module trace file predicates may not be called under certain conditions
- In STRIDE::Test module TEST_POINT_EVERYTHING_ELSE predicate may not be called
The following Runtime files have been modified:
srcfg.h srtest.h srdiag.c
4.1.04b
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- Test Points incorrectly filtered out on big-endian targets
- srTestCaseAddAnnotation may fail when the parrent case ID is bigger then the current suite ID
- NOTE_xx logging methods of STRIDE::Test module don't use the offset time when optional test_point argument is passed
- A STRIDE::Test module that passes all expectations and don't have any subsequent events will wait for full timeout before exiting
The following Runtime files have been modified:
srtest.c srtestutil.c srutil.c
4.1.04c
New features and improvements:
- Exposed a STRIDE Runtime callback hook for capturing on target raw trace content
- STRIDE Studio now allows loading captured on target raw trace content
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- Duplicate Test Points hits when expecting unordered may result in false positive test
- A STRIDE::Test module using multiple test point handlers may result in false positive test
The following Runtime files have been modified:
sribtr.h sribtr.c srstid.c srsuid.c srtest.c srthread.c