{"id":1043,"date":"2012-04-23T12:36:31","date_gmt":"2012-04-23T16:36:31","guid":{"rendered":"http:\/\/mainlinetest.com\/?p=1043"},"modified":"2012-04-23T12:52:55","modified_gmt":"2012-04-23T16:52:55","slug":"creating-a-custom-step-type","status":"publish","type":"post","link":"https:\/\/mainlinetest.com\/?p=1043","title":{"rendered":"Creating a Custom Step Type"},"content":{"rendered":"

In a previous blog post called ‘Sequence Call Step Type vs. Sequence Adapter’<\/a> I showed how one can couple the Action Step Type with the Sequence Call Adapter to create a Sequence Call Step that does NOT return a \u2018Passed\u2019 status upon completion.  Feel free to to read my previous blog post if you are wondering why I would want to do such a thing.  However, for this post I do want to remind you that the reason this could not be done with simply using the Sequence Call Step Type is because of the fact that the Status Expression is defaulted to either return \u2018Passed\u2019 or \u2018Failed\u2019 as shown in the Figure below.<\/p>\n

\"image\"<\/a><\/p>\n

Figure 1<\/strong><\/p>\n

Now lets say that you decide to make this a best practice in your organization and want to ensure that all developers going forward will utilize the new coding standards and be consistent with their coding practices when using Sequence Calls.  An ideal way to achieve this is by creating a Custom Step Type.  In this blog post, I am going to expand on a previous blog post to demonstrate how to get started creating Custom Steps.  In this case, to create a custom Sequence Call Step Type such that it does NOT return a \u2018Passed\u2019 status upon successful completion.<\/p>\n

Getting Started<\/em><\/strong><\/p>\n

In order to do this I need to first access the Types window by clicking the Types icon as shown in Figure 2 or I can simply hit (CTRL+T).<\/p>\n

\"image\"<\/a><\/p>\n

Figure 2<\/strong><\/p>\n

Your screen should now look similar to that shown in Figure 3.<\/p>\n

\"image\"<\/a><\/p>\n

Figure 3<\/strong><\/p>\n

Now under the Type Palettes tree, highlight the MyTypes.ini and notice the ability on the right to create custom Step Types and Date Types.  For this post, all I am going to worry about is the Step Types.  So next, where it says <Right click to insert Type>, I am going to do just that and select \u2018Insert Step Type\u2019.  Next, we need to name our new Step Type and for this example I will call it something crazy original like \u2018CustomSequenceCall\u2019.  Note that the name cannot have any spaces or start with a number.  Unfortunately, we aren\u2019t done yet as there is still a little configuration left to go.<\/p>\n

Once we have inserted a new Step Type we now need to configure it such that it will have the behavior we expect it to.  In order to do this, we need to right-click on \u2018CustomSequenceCall\u2019 and select Properties to pull up the Properties window as shown in Figure 4 below.<\/p>\n

\"image\"<\/a><\/p>\n

Figure 4<\/strong><\/p>\n

At first glance, this dialog can be a little overwhelming but remember that the power of TestStand is the configurability and be rest assured that the majority of these options will be rarely used as you will see whenever we configure this step. <\/p>\n

General Tab<\/em><\/strong><\/p>\n

So on the General tab, we are first presented with the ability to select an Icon.  Clicking on the \u2018Designate an Icon\u2019 checkbox will allow you to select from the combo box one of several options of Icons that TestStand comes with.  Note however that a lot of Icons already have a specialized meaning in TestStand and that sometimes it might be better to create your own.  If that is the case, the Icon files can be located in your Program Files>>National Instruments>>TestStand Ver##>>Components>>Icons folder.  Once you have an Icon selected, next we are given the ability to define the \u2018Default Step Name Expression\u2019.  This field accepts a String value representing what you want the Step Name to default to whenever you insert it into a sequence.  I\u2019ll demonstrate with images a little later, but for now note I am going to type in \u201cNew Sequence Call\u201d.  <\/p>\n

The next field is called \u2018Step Description Expression\u2019.  This field accepts a String value representing the text you want displayed under the description column in the Sequence Editor.  Once again, it is easier for me to demonstrate with images a little later, but for now I will enter the string \u201cMy New Step\u201d.  Normally all of these fields would be named something similar, but for this example I want to differentiate between them so you can see exactly where each is used.  <\/p>\n

Finally, we have the ability to \u2018Designate an Adapter\u2019.  If nothing is selected here, the developer has the ability to select any adapter during script development.  For our example, I want to restrict the user to only be able to use the Sequence adapter.  My final configuration for the General tab can be seen in Figure 5 below.<\/p>\n

\"image\"<\/a><\/p>\n

Figure 5<\/strong><\/p>\n

<\/em><\/strong> Menu Tab<\/em><\/strong><\/p>\n

Once we have the General tab configured we now need to jump to the Menu tab to create an \u2018Item Name Expression\u2019.  This field accepts a String value representing the text you want displayed whenever you right-click on the Sequence Editor and select a Step to insert into your sequence.  For our example I will create another unique String called \u2018Custom Sequence Call\u2019.  Our Menu tab should now be configured like that shown in Figure 6 below.<\/p>\n

\"image\"<\/a><\/p>\n

Figure 6<\/strong><\/p>\n

Default Expressions Tab<\/strong><\/em><\/p>\n

The final tab I want you to take a look at is the Default Expressions tab as shown in Figure 7 below.  Nothing needs to be changed here, however this is the major difference between the default Sequence Call Step Type as shown in Figure 1 and our new Custom Step.  Now whenever we insert our new step it will no longer override the Step.Result.Status to \u2018Passed\u2019.<\/p>\n

\"image\"<\/a><\/p>\n

Figure 7<\/strong><\/p>\n

We now have our Step Type fully configured and are ready to use it to create sequences.  Click \u2018OK\u2019 to exit out of the Properties window and go to the Sequence Editor.  Now right-click to insert your new Step and notice that your new step should be selectable on the menu with the \u2018Item Name Expression\u2019 text you defined under the Menu tab as well as the Icon you selected under the General tab as shown in Figure 8.<\/p>\n

\"image\"<\/a><\/p>\n

Figure 8<\/strong><\/p>\n

So next lets go ahead and select our Step Type to insert it into our script.  The first thing that should stick out is that the Step immediately gets named what we defined in the \u2018Default Step Name Expression\u2019 and the description for the Step gets set to what we defined in the \u2018Step Description Expression\u2019 under the General tab.  This is demonstrated below in Figure 9.  Figure 10 shows that under the Step Properties->General option, the Type is set to CustomSequenceCall and the Adapter is set to Sequence.  Now you should be able to see the direct correlation of all the properties we configured and where they get used.<\/p>\n

\"image\"<\/a><\/p>\n

Figure 9<\/strong><\/p>\n

 <\/p>\n

\"image\"<\/a><\/p>\n

Figure 10<\/strong><\/p>\n

Finally I created a really quick script that executes my step and shows the Step.Result.Status upon successful completion.  The results are shown in Figure 11 and as you can see my new Custom Sequence Call now returns a Status of \u2018Done\u2019.  Yay!<\/p>\n

 <\/p>\n

\"image\"<\/a><\/p>\n

Figure 11<\/strong><\/p>\n

Deployment<\/strong><\/em><\/p>\n

Now say you are super stoked about your new Custom Step and want to make sure all your Test Racks come equipped with it.  Under the Type Palettes window, you have the option of saving your changes.  You should notice an asterisk \u2018*\u2019 next to MyTypes.ini.  If you decide to save your changes, TestStand will update the corresponding MyTypes.ini file.  This file is located in the Users>>Public>>Public Documents>>National Instruments>>TestStand Ver###>>Components>>TypePalettes.  You can simply take a copy of the modified .ini file and copy it into the appropriate location on your other Test Racks.<\/p>\n

Secondly, if you are having trouble coming up with proper names for the different String fields under the Custom Step Types Properties dialog.  Navigating to the NI_Types.ini directory and viewing a similar Step Type configuration is always a good idea.  For example, in our case, since we essentially wanted to modify the pre-existing Sequence Call Step Type, we could have configured our Step to look like the regular Sequence Call Step Type shown in Figure 12 below.<\/p>\n

\"image\"<\/a><\/p>\n

Figure 12<\/strong><\/p>\n

In conclusion, Custom Steps are another powerful tool that TestStand has to offer.   They offer a unique way to make both major and minor modifications to the predefined suite of Steps that NI has to offer.  You should now feel comfortable getting started with creating Custom Steps and don\u2019t hesitate to contact your nearest NI Field Service Rep or Alliance Partner (hint hint) if you ever need some extra help.<\/p>\n","protected":false},"excerpt":{"rendered":"

In a previous blog post called ‘Sequence Call Step Type vs. Sequence Adapter’ I showed how one can couple the Action Step Type with the Sequence Call Adapter to create a Sequence Call Step that does NOT return a \u2018Passed\u2019 status upon completion.  Feel free to to read my previous blog post if you are Continue Reading<\/a><\/p>\n","protected":false},"author":2,"featured_media":741,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[40,42,24,32,41,23,43],"class_list":["post-1043","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-custom-step","tag-mytypes-ini","tag-national-instruments","tag-sequence-call","tag-step-result-status","tag-teststand","tag-type-palettes","cat-1-id"],"_links":{"self":[{"href":"https:\/\/mainlinetest.com\/index.php?rest_route=\/wp\/v2\/posts\/1043","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mainlinetest.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mainlinetest.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mainlinetest.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mainlinetest.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1043"}],"version-history":[{"count":3,"href":"https:\/\/mainlinetest.com\/index.php?rest_route=\/wp\/v2\/posts\/1043\/revisions"}],"predecessor-version":[{"id":1051,"href":"https:\/\/mainlinetest.com\/index.php?rest_route=\/wp\/v2\/posts\/1043\/revisions\/1051"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mainlinetest.com\/index.php?rest_route=\/wp\/v2\/media\/741"}],"wp:attachment":[{"href":"https:\/\/mainlinetest.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1043"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mainlinetest.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1043"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mainlinetest.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1043"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}