Capture Functionality Overview
In addition to adding script steps using the GUI scripting support, you can also add steps by connecting to a configured device via a console session and input commands to the device. The input commands are both executed on the device are also captured as script steps.
The Capture functionality, which adds command capturing capabilities to the basic Edit mode, enables you to establish multiple device sessions at once to different test devices and to add steps in direct interaction with those devices.
Commands can be issued using a wide range of supported protocol and application interfaces, such as Telnet, TclSh, TL1, SSH1/SSH2/SSHAuto, IxEmail, Raw, COM and Reporter .
Working using the Capture functionality can be combined with working in the basic Edit mode and adding steps manually using the GUI scripting support. For example, you can start working in the basic Edit mode and add commands using the GUI scripting support, then configure a device session and click thebutton of the Session Console pane to connect to a configured device. While connected to the device, input commands are both executed on the device and captured as script steps into the Script Steps table.
Eventually, after having added a number of captured script steps, you can revert to adding more steps in the basic Edit mode using the GUI scripting support.Device sessions specifying connectivity parameters that range from physical to exceptions, can be saved as resources and re-used across multiple tests.
The TestComposer GUI with Capture Functionality Enabled
When switching to the Capture functionality of the Edit mode by clicking the Console
button in the Test ribbon (or alternatively by pressing the Alt+Shift+Ckeyboard shortcut), in addition to the Script Steps table the Session Consoles pane is displayed containing a tabbed view for managing multiple simultaneous connections to configured devices ( Figure:TestComposer GUI with Session Consoles Pane).
Figure:TestComposer GUI with Session Consoles Pane
While using the Capture functionality, the bottom pane displays the Command Response, Validation Errors, Execution Errors, Breakpoints,and Find/Replace tabs described in The Edit Mode GUI.
Table:Capture Functionality Toolbar Buttons and Options describes the toolbar buttons for performing device session related operations that are accessible when using the Capture functionality:
Connects to the configured device using the selected interface.
Disconnects the current session.
Switches to a read-only view of session settings.
Clears the current Console Session pane.
When in the Device Prompts and Exceptions categories, clicking this button adds Device Prompt and Exceptions table entries.
When in the Device Prompts and Exceptions categories, clicking this button removes Device Prompt and Exceptions table entries.
Opens an existing device session saved as a reusable resource.
Saves a device session as a reusable resource.
This toggle type button switches the capturing functionality on or off. On a connected session, switching capturing off would enable you, for example, to input some device commands that are not added as script steps. Eventually, when you wish to add some more script steps while interacting with the device, switch again capturing to on.For an unconnected session, when the capturing functionality is off, you can still connect to the device and issue commands, but without any of the StartSession or subsequent command steps to be added to the Script Steps table.
IxLoad TestComposer sessions span a wide range of supported protocol interfaces, such as Telnet, TclSh, TL1, SSH1/SSH2/SSHAuto, IxEmail, Raw, COM and Reporter.