STRIDE 4.1.01x: Difference between revisions
No edit summary |
|||
(10 intermediate revisions by one other user not shown) | |||
Line 28: | Line 28: | ||
=== Framework === | === Framework === | ||
The product has been repackaged. In addition to the [[STRIDE Studio]] package, a new [[ | The product has been repackaged. In addition to the [[STRIDE Studio]] package, a new [[Desktop_Installation|STRIDE Framework]] package has been introduced. The new package provides support for Windows and Linux host clients. | ||
= Change Details = | = Change Details = | ||
Line 49: | Line 49: | ||
== Runtime == | == Runtime == | ||
* STRIDE Host Release '''4.1.01x''' is compatible with the Runtime Version '''4.1.01''' | * STRIDE Host Release '''4.1.01x''' is compatible with the Runtime Version '''4.1.01''' | ||
* [[ | * [[Test Point Testing in C/C++ |Test Points]] APIs have been changed. | ||
* The signature of the [[Platform_Abstraction_Layer#PAL_Input.2FOutput_Services|PAL IO Service]] InData callback (''palInDataCallback_t'') has changed. The first argument is now a '''const''' pointer. | * The signature of the [[Platform_Abstraction_Layer#PAL_Input.2FOutput_Services|PAL IO Service]] InData callback (''palInDataCallback_t'') has changed. The first argument is now a '''const''' pointer. | ||
* ''Most of the Runtime files have been modified. It is recomended that you update them all.'' | * ''Most of the Runtime files have been modified. It is recomended that you update them all.'' | ||
Line 60: | Line 60: | ||
* ''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.'' | ||
* ''All [[:Category:SDKs|Platform SDKs]] has been reorganized to | * ''All [[:Category:SDKs|Platform SDKs]] has been reorganized to better support the[[Off-Target Environment]]. | ||
= Minor and Patch releases = | = Minor and Patch releases = | ||
== 4.1.01a == | == 4.1.01a == | ||
''New features and improvements:'' | ''New features and improvements:'' | ||
* | * [[STRIDE Runner]] now supports transactional [[Stride_Runner#Options | upload]] to [[STRIDE Test Space]] | ||
''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ||
* [[STRIDE Runner]] rejects device address with dots in the name. | |||
* [[STRIDE Runner]] may deadlock during diagnostics. | |||
* Removed extra "()" in the test point annotation | * Removed extra "()" in the test point annotation | ||
* STRIDE enabled Target applications may log an error on exit. | |||
* In [[Linux SDK]] the PAL timer callback may deadlock. | |||
''The following Runtime source files have been modified:'' | ''The following Runtime source files have been modified:'' | ||
srtest.c | srtest.c | ||
''The following [[Windows SDK]] files have been modified:'' | |||
palIO.c | |||
''The following files have been modified:'' | ''The following [[Linux SDK]] files have been modified:'' | ||
palIO.c | palIO.c | ||
palOS.c | palOS.c | ||
palcfg.h | palcfg.h | ||
== 4.1.01b == | == 4.1.01b == | ||
''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ||
* Runner on Windows fails to operate on COM port number greater than 9. | * [[STRIDE Runner]] on Windows fails to operate on COM port number greater than 9. | ||
* Runner on Windows may log an error like "log4cplus:ERROR Unable to open file: ...". | * [[STRIDE Runner]] on Windows may log an error like "log4cplus:ERROR Unable to open file: ...". | ||
* Runner may fail to HTTP redirect on results uploading. | * [[STRIDE Runner]] may fail to HTTP redirect on results uploading. | ||
* [[s2sbind]] and [[s2sinstrument]] on Windows may log an error like "log4cplus:ERROR Unable to open file: ...". | |||
* Resource leak when using [[Test Point Testing in C/C++ | Test Points]]. | |||
* Default [[Runtime Reference|STRIDE Runtime]] configuration values (srcfg.h) for a non-complex target are too restrictive. | |||
* In [[Windows SDK]] COM port connection may not work. | |||
* [[C/C++ Samples]] source code was updated to remove compiler warnings | |||
* Resource leak when using Test Points. | |||
* Default configuration values (srcfg.h) for a non-complex target are too restrictive. | |||
''The following Runtime source files have been modified:'' | ''The following Runtime source files have been modified:'' | ||
Line 131: | Line 108: | ||
srsuid.c | srsuid.c | ||
''The following [[Windows SDK]] files have been modified:'' | |||
palIO.c | palIO.c | ||
palOS.c | palOS.c | ||
== 4.1.01c == | == 4.1.01c == | ||
''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ||
* Runner freezes on unexpected connection termination. | * [[STRIDE Runner]] freezes on unexpected connection termination. | ||
* Runner on Windows may omit an error on COM port disconnect. | * [[STRIDE Runner]] on Windows may omit an error on COM port disconnect. | ||
* Added support for any count (0 or more) per [[Test Point Testing in C/C++ |Test Point]] expectation. | |||
* In [[Linux SDK]] and [[Windows SDK]] too big buffer used in palLog(). | |||
* [[C/C++ Samples]] source code was updated to fix a resource leak | |||
* Added support for any count (0 or more) per [[ | |||
''The following Runtime source files have been modified:'' | ''The following Runtime source files have been modified:'' | ||
Line 169: | Line 128: | ||
srtest.c | srtest.c | ||
''The following [[Linux SDK]] files have been modified:'' | |||
palOS.c | palOS.c | ||
''The following [[Windows SDK]] files have been modified:'' | |||
palIO.c | palIO.c | ||
palOS.c | palOS.c | ||
== 4.1.01d == | == 4.1.01d == | ||
''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ||
* | * [[STRIDE Runner]] accepts non-standard Test Space URL format. | ||
* [[STRIDE Runner]] may incorrectly remove test cases on dynamic suite/case creation. | |||
* [[s2scompile]] may crash on compilation of invalid use of [[scl_test_flist]]. | |||
* Added support for printf like format to [[Test Code Macros]]. | |||
* Added support for printf like format to [[Test | |||
''The following Runtime source files have been modified:'' | ''The following Runtime source files have been modified:'' | ||
Line 218: | Line 149: | ||
== 4.1.01e == | == 4.1.01e == | ||
''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ||
* Dynamic test case result has no duration. | * Dynamic test case result has no duration. | ||
* Unable to build in Windows on a read-only ClearCase mount. | |||
* Timestamp fraction (srCFG_TIMESTAMP_DURATION) not taken in consideration. | * Timestamp fraction (srCFG_TIMESTAMP_DURATION) not taken in consideration. | ||
Line 238: | Line 158: | ||
srtestutil.c | srtestutil.c | ||
srutil.h | srutil.h | ||
== 4.1.01f == | == 4.1.01f == | ||
''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ''Defects corrected and the customer tracking number associated with them, if any, in brackets []:'' | ||
* [[STRIDE Runner]] on Windows may log errors like "log4cplus:ERROR No appenders could be found ...". | |||
* [[s2sbind]] and [[s2sinstrument]] on Windows may log errors like "log4cplus:ERROR No appenders could be found ...". | |||
* Misbehaviour on Linux systems with non standard NPTL implementation. | |||
* Microsecond srCFG_TIMESTAMP_UNITS treated as seconds. | * Microsecond srCFG_TIMESTAMP_UNITS treated as seconds. | ||
Line 265: | Line 170: | ||
srtestutil.c | srtestutil.c | ||
srutil.h | srutil.h | ||
''The following [[Linux SDK]] files have been modified:'' | |||
palcfg.h | |||
palOS.c | |||
stride.c | |||
[[Category:Release Notes]] | [[Category:Release Notes]] |
Latest revision as of 22:21, 2 June 2010
Release Notes
This page documents the changes in STRIDE version 4.1.01x (code name Grandview).
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.01x. |
What's New
Based on customer feedback, in this release we have many key usability improvements and bug fixes.
Usability Improvements
STRIDE Runner
Stride Runner is a new command line host based tool that allows performing target diagnostics and running target-based tests from a host computer and optionally uploading results to STRIDE Test Space.
STRIDE Test Space
STRIDE Test Space is a hosted web application for storing and analyzing your test results. Manually (using the web interface) or automatically from one of the STRIDE execution tools (STRIDE Runner or STRIDE Studio) the user now can create a fluid hierarchy of test results that adapts to shifting needs during a product lifecycle.
Framework
The product has been repackaged. In addition to the STRIDE Studio package, a new STRIDE Framework package has been introduced. The new package provides support for Windows and Linux host clients.
Change Details
License
- A new licensing scheme has been implemented. Existing licenses will not work anymore and need to be reissued. Old and new licenses could co-exist at the same location.
Fixes
This section describes defects which have been corrected in STRIDE and the customer tracking number associated with them, if any, in brackets [].
- In Linux SDK the PAL timer APIs may deadlock.
- In Windows SDK the COM ports 1-9 may not be handled properly.
- Generated IM code for Test Doubles is incorrect (compiler warning)
- STRIDE Studio may crash when compiling unions with internal discriminants.
- STRIDE Studio is unable to publish results to STRIDE Test Space. The support for Portal has been discontinued.
Host Tools
- A new command line host based tool, STRIDE Runner, has been introduced.
Runtime
- STRIDE Host Release 4.1.01x is compatible with the Runtime Version 4.1.01
- Test Points APIs have been changed.
- The signature of the PAL IO Service InData callback (palInDataCallback_t) has changed. The first argument is now a const pointer.
- Most of the Runtime files have been modified. It is recomended that you update them all.
- The following Runtime files have been removed:
srinstall.h srinstall.c
- The following new Runtime files have been added:
srdiag.h srdiag.c
- All Linux SDK files have been modified.
- All Windows SDK files have been modified.
- All Platform SDKs has been reorganized to better support theOff-Target Environment.
Minor and Patch releases
4.1.01a
New features and improvements:
- STRIDE Runner now supports transactional upload to STRIDE Test Space
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- STRIDE Runner rejects device address with dots in the name.
- STRIDE Runner may deadlock during diagnostics.
- Removed extra "()" in the test point annotation
- STRIDE enabled Target applications may log an error on exit.
- In Linux SDK the PAL timer callback may deadlock.
The following Runtime source files have been modified:
srtest.c
The following Windows SDK files have been modified:
palIO.c
The following Linux SDK files have been modified:
palIO.c palOS.c palcfg.h
4.1.01b
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- STRIDE Runner on Windows fails to operate on COM port number greater than 9.
- STRIDE Runner on Windows may log an error like "log4cplus:ERROR Unable to open file: ...".
- STRIDE Runner may fail to HTTP redirect on results uploading.
- s2sbind and s2sinstrument on Windows may log an error like "log4cplus:ERROR Unable to open file: ...".
- Resource leak when using Test Points.
- Default STRIDE Runtime configuration values (srcfg.h) for a non-complex target are too restrictive.
- In Windows SDK COM port connection may not work.
- C/C++ Samples source code was updated to remove compiler warnings
The following Runtime source files have been modified:
srcfg.h srdiag.h srdiag.c srmsgque.c srmsgrt.c srstid.c srsuid.c
The following Windows SDK files have been modified:
palIO.c palOS.c
4.1.01c
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- STRIDE Runner freezes on unexpected connection termination.
- STRIDE Runner on Windows may omit an error on COM port disconnect.
- Added support for any count (0 or more) per Test Point expectation.
- In Linux SDK and Windows SDK too big buffer used in palLog().
- C/C++ Samples source code was updated to fix a resource leak
The following Runtime source files have been modified:
srconn.h srconn.c srib.c srtest.h srtest.c
The following Linux SDK files have been modified:
palOS.c
The following Windows SDK files have been modified:
palIO.c palOS.c
4.1.01d
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- STRIDE Runner accepts non-standard Test Space URL format.
- STRIDE Runner may incorrectly remove test cases on dynamic suite/case creation.
- s2scompile may crash on compilation of invalid use of scl_test_flist.
- Added support for printf like format to Test Code Macros.
The following Runtime source files have been modified:
srtest.h srtestpp.cpp
4.1.01e
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- Dynamic test case result has no duration.
- Unable to build in Windows on a read-only ClearCase mount.
- Timestamp fraction (srCFG_TIMESTAMP_DURATION) not taken in consideration.
The following Runtime source files have been modified:
srtest.c srtestutil.c srutil.h
4.1.01f
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- STRIDE Runner on Windows may log errors like "log4cplus:ERROR No appenders could be found ...".
- s2sbind and s2sinstrument on Windows may log errors like "log4cplus:ERROR No appenders could be found ...".
- Misbehaviour on Linux systems with non standard NPTL implementation.
- Microsecond srCFG_TIMESTAMP_UNITS treated as seconds.
The following Runtime source files have been modified:
srtestutil.c srutil.h
The following Linux SDK files have been modified:
palcfg.h palOS.c stride.c