Best practice use of
TrueLog Explorer involves the following steps.
Most likely you will not perform these steps in a simple one-time-through sequence. These tasks are to be performed iteratively.
For example, you may make a customization, check the outcome, then make another customization, and check the outcome of that
customization.
Note: To enable the insertion of timers and other script-modification features, your TrueLog must be up-to-date (in sync). If your
TrueLog is not up-to-date, execute a Try Script run to synchronize it.
- Analyzing a Test
- This process involves examining the outcome of a previous test run, reviewing a Virtual User Summary Report, locating replay
errors, and comparing a replay session alongside an original record session. This process allows for the error checking of
script customizations.
- Customizing Session Handling
- Session-handling errors occur when outdated session data that is embedded in a
load-test script is rerun in a subsequent test run.
TrueLog Explorer automates the process of identifying such static data and replacing it with dynamic data to facilitate successful test runs.
No manual editing of code is required.
Note: Because the
Silk Performer script recording techniques generate context-full scripts that do not contain static session information, session handling
customization is generally not required.
- Customizing User Data
- To better simulate real-world conditions during
load
testing, the actions that virtual users take against servers should vary with each simulated transaction. User input data
customization allows the specification of data files (for example, lists of names/addresses, numbers, and products) from which
data is to be pulled when the test script simulates such user tasks as form-field data entry. With random functions, randomized
data can also be generated for input fields.
- Customizing User Data
- To better simulate real-world conditions during
load
testing, the actions that virtual users take against servers should vary with each simulated transaction. User input data
customization allows the specification of data files (for example, lists of names/addresses, numbers, and products) from which
data is to be pulled when the test script simulates such user tasks as form-field data entry. With random functions, randomized
data can also be generated for input fields.
- Adding Verification Functions
- After the completion of customizing how a test script handles session information and virtual user data input, functions can
be built into scripts to automatically check if the application under test returns accurate data. Such content verifications
confirm whether or not elements, such as graphics and data, are actually received by clients under real-world conditions.
When such elements are not received, verifications raise errors.
- Extending Customization via
Silk Performer
- Although
TrueLog Explorer automates most BDL scripting automatically, more sophisticated verifications and customizations can be coded into scripts
manually via
Silk Performer.
- Analyzing TrueLog On Error
- After a test has been run, TrueLog On Error files provide complete histories of all erroneous transactions that are encountered
during testing. TrueLog On Error enables you to drill down through real content to perform root-cause analysis on system and
application faults.