Difference between revisions of "STRIDE 4.1.01x"

From STRIDE Wiki
Jump to: navigation, search
(→‎4.1.01b)
Line 28: Line 28:
  
 
=== Framework ===
 
=== Framework ===
−
The product has been repackaged. In addition to the [[STRIDE Studio]] package, a new [[Package_Installation|STRIDE Framework]] package has been introduced. The new package provides support for Windows and Linux host clients.
+
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  =

Revision as of 17:19, 17 May 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 [].

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

Minor and Patch releases

4.1.01a

New features and improvements:

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

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

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
Retrieved from "https://www.stridewiki.com/index.php?title=STRIDE_4.1.01x&oldid=12459"