Custom step types and custom step data.

[Ivar S]

Hello.

I have a good understanding of how TestStand allows custom step types to allow users to store custom data.

I have also read numerous posts about users asking for the ability to store some custom data associated with steps.

In my scenario I am required to write a sequence using a few third party supplied step types.

To assist in developing and debugging this sequence, we would like to store a container of custom data with each steps.

Option 1: Create custom step types.

This is really not an option, relying on third party step types. Any customization made to their step types will magically disappear, along with any custom data, the next time I install one of them service packs.

You may argue that I just have to ensure all custom fields are recreated before opening a sequence file. This works in my office when everyone is at edge with this, but in a few months someone will "take responsibility"

and upgrade the 3rd party packs without reading the entire upgrade procedure.

Option 2: Create links in Sequence Locals

This does work, but is not very associative. To work, the name of the Locals entry would need to be the unique ID of the step it refers to.

Also, it requires some more maintenance to insert new steps, and to remove stale references.

I really hope that someone in TestStand R&D reads this, and enables users to store step custom data, for example by adding a "CustomData" container to the TS property of the step.

Regards,

Ivar S.

[RayFarmer]

Hi,

I am not really sure on what your requirement is!

If its adding some custom data container to Custom Step Types, you know you can create Step Type based on other step types which include Custom Step Type.

Therefore you can create you own Custom Step which includes your additional Data Type but will use. Providing your Supplied Custom Step Type are of a stable design you can use your version of the Custom Step Type instead of the supplied Custom Step Type without having to continually rework your version.

Regards

Ray Farmer 

[Ivar S]

Ray:

Thanks for answering.

I am aware that I can extend a custom step type by creating a new step type based on the first type.

For example, I have this 3rd party JtagExecuteTest step type, supplied by another solution vendor.

In my sequence, I want a custom error & failure handler, that needs information about each step as they fail.

For handling and logging purposes, I need each step in my sequence to carry information in addition to the setup required by JtagExecuteTest.

So I set forth, and modify the step type JtagExecuteTest step, along with some other 10-15 step types that the other solution vendor has put in their package.

This works like a charm until I have to reinstall or upgrade the package.

Because I modified the steps using their original name, all data I put into the steps are lost.

Next attempt, I follow your advice and create MyJtagExecuteTest step, based on the original steps. Again, I repeat this customization for 10-15 step types.

This works like a charm until I have to upgrade the package.

Now some wise guy at the other solution vendor has renamed a DLL or a function call, breaking down every step that I have customized.

Mush better, though, because I can repeat the customization process and the data does not disappear.

Still, this is just too much hassle just to put TestStand to some decent use.

If I could just click on a step, add my custom properties, and have TestStand retain those data as a user customization that particular step instance.

Much like you have Sequence.Locals, it would be extremely useful to have a Step.Locals container for the users to use at will.

Regards,

Ivar Svendsen.

[James_Grey]

There is a new feature in the next version of TestStand that might be what you need. You can apply for the beta program at www.ni.com/beta

Once you have the beta, look for the "Attributes" feature.

[James_Grey]

I should also add that a step type developer can already enable their users to add arbitrary amounts of additional data by creating an empty container sub-property on the step type and marking it with the unstructured flag. This enables users to insert arbitrary properties under the property in any step instance.

Message Edited by James Grey on 02-27-2009 12:07 PM

Message Edited by James Grey on 02-27-2009 12:08 PM

[Ivar S]

Hello. I have submitted an application for the TestStand Beta program. It seems as it may take a while to be approved. Is the "new feature list" from the beta available to the public? Regards, Ivar Svendsen.