question

mandonov avatar image
mandonov asked ericnute edited

Rendering limitations?

I created a two-thread test case that worked fine when executed from iTest. Each thread opens a Telnet session to a DUT and closes after doing some work on the DUT. Neither session is associated with a test bed, nor does it use any parameters or global variables. Since I need to run this test case as a Tcl script, I rendered it to Tcl and received the following errors below. Wondering what the field substitutions and async steps errors mean?

 

Attached is the test case.

 

Will appreciate prompt help!

 

Lenny

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

RENDERING LIMITATIONS
---------------------
Procedure main, step 1: Procedural EXEC steps with field substitutions enabled cannot be rendered correctly. Substitutions should be disabled.
Procedure main, step 1: Async steps are not supported
Procedure main, step 2: Procedural EXEC steps with field substitutions enabled cannot be rendered correctly. Substitutions should be disabled.
Procedure main, step 2: Async steps are not supported


VALIDATION ERRORS
-----------------


RENDERING ERRORS
----------------

iTesttcl scriptthreads
stal.fftc (17.5 KiB)
10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
PaulD avatar image
PaulD answered PaulD posted

I don't know how the flag on these two steps that enables command substitution got turned on.  I believe that the original test case may have been created in an earlier version of iTest maybe? 

 

Anyway, if you turn these off, two of these warnings go away.   (Select the two steps, and in the Step Properties General page, uncheck the box that says that the command field contains substitutions.)  The warnings about asynchronous operation are real.  Since Tcl isn't multithreaded, the resulting script will execute these two steps in sequence, rather than in parallel. 

3 comments
10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

mandonov avatar image mandonov commented ·

Thanks Paul - you are right, I used an existing test case to create this one and the enable command substitution flag was turned on there.

After reviewing the iTest help, I am a bit more clear on the rendering limitations, but I am still assessing what the impact will be on what I am trying to do.

 

Thanks for your help.

 

Lenny 

 

0 Likes 0 ·
PaulD avatar image PaulD mandonov commented ·

Lenny,

 

I'm not sure of your exact situation, but I know that several people are using a Tcl wrapper script for running iTest test cases -- and this completely eliminates any limitations (such as multi-threaded execution).  Essentially, instead of rendering the iTest test case into low-level Tcl (with statements corresponding to each step in the iTest test case), a single Tcl script can be written that invokes a higher-level Tcl API that knows how to run an entire iTest test case using a single line of Tcl code.  This may or may not be useful in your situation.  If you'd like to learn more about that, let me know.

0 Likes 0 ·
mandonov avatar image mandonov PaulD commented ·

Paul -- yes, I'd be very interested to find out about the wrapper option. How do we proceed from here?

 

Regards,

 

Lenny 

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.