URGE*T = Offer to Pay. We are all volunteers here.
Basic info: RTE exists for terminal based applications
Architecture: You are emulating a physical text terminal (not an Xwindows or graphical terminal like windows), communicating to a ‘NIX, 5250, 3270 or other style host which supports a terminal interface to the application
How to record: Be curious. Try it out. Read the section on RTE in the manual. For gosh sakes, it’s nowhere near as complicated as web or database as an example
Parameterization is common across all protocols, Correlation? [f1] please
How to map keys (see terminal config for your recording). Mouse clicks? This is a text interface, not XWindows
Reports: Transactions, Datapoints, Monitors, … No page breakdown (web based) or other items which are protocol specific
Analysis: Standard bottleneck analysis of system capacity constraints applies
General issues: Make sure you pick the correct terminal type for what you are trying to do. If it’s standard VT100/telnet unencrypted then you can also do Winsock. Standard development models apply: Check to see if the page you expect to have returned has returned, manage your data properly, document your tests initial conditions and your controlled and uncontrolled elements of your test bed.
James Pulley, http://www.loadrunnerbythehour.com/PricingMatrix
--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en
· [F1]
· Online Docs for LoadRunner (PDF Form) which are installed with every copy of LoadRunner
· Printed Docs for VUGEN
Be curious,