0.47

Released October 15., 2008

Our previous release opened up a slew of new possibilities for other improvements. When it becomes possible to update the target with new configuration files, the need for updating the configuration properties in SeqZap during execution also becomes apparent.

Configuration updating plug-ins

In version 0.47 of SeqZap you can add sources to configuration property collections, these sources are implemented as plug-ins to allow you to support the file format used by _your_ product. But we have added a few default plug-ins used for handling things like setting the configuration properties back to the default value.

Updating the configuration properties

The configuration properties can of course be updated from inside the editor by right clicking the configuration property collection header, this allows the user to both update the default or the local configuration property values.

To update the configuration properties during execution you can use the new step type designed for the purpose.

Procedure models

This version of SeqZap adds more possibilities for structuring your projects. You can now mark a procedure model as a sub-model of another procedure model, this means that you can have a default procedure model for all your test cases, and then define a sub-model for test cases which require special handling.

Special handling is of course a very broad term, normally your sub-models will define an alternative setup method which does something to prepare your target for a test case in addition to what the base models setup is already doing.

In the two dialogs above you can see the partners defined for the base model and the sub-model, the base model has three partners defined, a Setup partner, a Cleanup partner and a partner for doing formal testing which we will not focus on in here.

The sub-model defines a new Setup partner by overriding the partner defined by the base model. The relationship between the two models is expressed graphically in the figure below.

Get custom property step

Custom properties are another thing that can be defined and subsequently overridden on procedures and their models. Custom properties are values or tags that can be applied to procedures to indicate which configuration file to use, where the documentation for a particular procedure is located and similar things.

This release of SeqZap now allows your scripts to access the custom properties of procedures during execution, this can be used in conjunction with the new configuration property updating functionality to ensure that the parameters in the device under test is the same as the ones defined in SeqZap.