Why use the sequencer when you can just do stc::perform?
I'm trying to understand why?
I read that the sequencer returns control to the script after once the command is done executing. Is it the same thing when calling a command for stc::perform. Is it because stc::perform is not sequential and that multiple commands can run at the same time?
Best Answer
Besides the GUI exports you may also need to use it to run "Spirent-Canned-Tests" (like RFC tests) where the API command for RFC-Tests are "wizards" that create Tests in the sequencer "automatically" that would be very complex to hand write, then you would need to run these in the sequencer.
,The sequencer is mainly used in GUI exported scripts (you would not generally use it in hand written scripts), the sequencer allows you to use automation like command "in the GUI".
Thank you Steve. What about when you export to code (python for example) in iTest. Would I see the use of sequencer in it?
You may want to talk to iTest support, but generally I would think it will use the sequencer as well (maybe with "global-service-commands which are hand written scripts you can add to the sequencer).
Thank you so much.
Finally, can you explain in a little bit more details what you meant by:
- Spirent-Canned-Tests
- RFC test
A canned test (think Hollywood - it's in the "can") is a very complex test written by Spirent (basically a wizard).
RFC tests are generally benchmark tests defined by an RFC (google RFC-2544 for an example). There are several canned RFC tests available in the STC product.
I Say Canned as it would be just about impossible to duplicate the same test outside the wizard as many functions are not available in the API itself.
Thanks Steve, that was helpful.
