STRIDE 5.0.01x

This page documents the changes in STRIDE version 5.0.01x (code name Warm Waters), released on Jun 3, 2014.

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 5.0.01x.

What's New

Based on customer feedback this release includes many key usability improvements and bug fixes.

Testspace Schema execution

Now the STRIDE Runner allows execution of tests defined in a Testspace Schema.

Input Parameters

Passing input parameters per test suite has been implemented. A new API in the STRIDE Runtime allow accessing them by name.

Interactive Mode

The File Transfer subsystem has been updated to allow remote (host) interactive prompt and process execution. In addition the STRIDE Runner now supports single test case execution.

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 [].

• Handling of input payload in STRIDE Runner times slower compared to output.
• STRIDE Runner generates report with incorrect timestamps for kernel Test Logs.
• STRIDE Runner may generate a report xml with invalid file annotation content.

Tests in Scripts

• Dynamic Test Suites are not supported no more.

Tests in C/C++

• Dynamic Test Suites are not supported no more.
• Test Assertion macro now by default (controlled via compiler define) throw exceptions.
• Test Annotation macros and Test Log macros now by default (controlled via compiler define) support variadic arguments.
• Error handling has been improved.

Runtime

• STRIDE Host Release 5.0.01x is compatible with the Runtime Version 5.0.01
• SLAP has been move in the core Runtime.
• srCOMPLEX_TARGET is set by default now.
• All of the Runtime files have been modified. It is recommended that you update them all.
• All Posix SDK files have been modified.
• All Windows SDK files have been modified.

Minor and Patch releases

5.0.01a

New features and improvements:

• STRIDE Runner now can run executables (optionally in the background) and consume directly JUnit xml report.
• STRIDE Runner now reports overall suite duration.
• STRIDE Runner has been updated to handle common suite input defined in folder settings.
• STRIDE Runner now has improved error handling and supports "dry" run (for fast input validation).

Defects corrected and the customer tracking number associated with them, if any, in brackets []:

• Incremental "finish" upload via STRIDE Runner does not complete the result set.

5.0.01b

Defects corrected and the customer tracking number associated with them, if any, in brackets []:

• STRIDE Instrumentation Generator produces incorrect code for function callbacks in a 64-bit build.
• Perl Assertions error out with undefined input.
• STRIDE Runner does not honor timeout for executables and scripts.
• STRIDE Runner errors out in "dry" run with no database.
• STRIDE Extensions for Visual Studio error out when solution is opened from a UNC location.

The following Runtime files have been modified:

srcgutil.h

The following Windows SDK files have been modified:

stride.props
stride.targets

5.0.01c

New features and improvements:

• STRIDE Runner traversal of a Testspace schema has been optimized.
• STRIDE Runner now shows the path to local report file and the URL to the uploaded Testspace results.

Defects corrected and the customer tracking number associated with them, if any, in brackets []:

• STRIDE Compiler is unable to compile header files with forwardly declared enums.
• STRIDE Compiler calculates incorrect payload offset for user defined type arguments in a test class constructor.
• STRIDE Compiler errors out on enums with out of range values.
• STRIDE Runner is unable to explicitly run "disabled" folder/suite.
• STRIDE Runner errors out in "dry" run with no database.
• STRIDE Runner creates empty xsl file on host with no internet connection.
• Static analysis of Windows SDK source results in a warning.
• STRIDE Runtime memory pool allocation return misaligned pointers on 64-bit targets.

The following Runtime files have been modified:

srcfg.h
srtest.h
srmem.c

The following Windows SDK files have been modified:

stride.c