Printer FriendlyEmail Article Link

How can I validate my Avalanche TCL script?


You can trial run test parameters before starting a test by adding the ValidateTest function to your test script. The ValidateTest function trials the test by running once through the Client Actions URL list. It performs an internal consistency check, scanning through configuration files, error checking, and ensuring that all files referenced are available.

ValidateTest verifies that all of the URLs are accessible. The trial run proceeds as long as it takes to check each URL once, up to the duration of the load profile. If problems are encountered, check the results file to troubleshoot the test.
During a trial run, the ValidateTest function generates a PCAP (packet capture) trace file for each individual client and server unit involved in the test. The PCAP file is called trace0.pcap or trace1.pcap, for the first or second port in the port group, respectively. The file shows all packets sent and received for the port as the result of one simulated user. You can view this file by using any standard sniffer program, such as Wireshark, Netasyst, Sniffer Pro, or ClearSight. (For more information about this file, see the About Test Results topic in the online Help.)
Also during a trial run, the ValidateTest function generates an XML trace file for individual URLs, which contains errors, bindings of variables, response latency, and so on. One trace file is generated per simulated user, called httptracefile_X_trace.xml, where X is a number that represents the simulated user associated with the file. You can view this file by using the URL Trace Tool.
As the specific commands may be different depending on the release you are running, please refer to the L4_7_Scripting_API.pdf document that can be found in the C:\Program Files\Spirent Communications\Spirent TestCenter [version you are running]\Layer 4-7 Application\TclAPI\Documentation directory.


Product : Avalanche,L4-7,Automation