Chatta subito con l'assistenza
Chat con il supporto

Foglight Transaction Recorder 5.6.12 - Recorder User Guide

Overview of Foglight synthetic monitoring Use the Foglight Transaction Recorder Create and upload Foglight Transaction Recorder scripts View Foglight Transaction Recorder results Settings How Do I... Appendix: Best practices Appendix: Troubleshoot the Foglight Transaction Recorder Appendix: API for FTR Timer Usage

Captured images should be as small as possible

Use small unique images in your scripts. This reduces the impact of display changes to the script.
For example, the following image of the Dell Software logo is accurate, but much larger than needed.
Figure 63. Example of a large image
The example below provides a much smaller, unique image to use to identify the logo.
Figure 64. Example of a small image

Manually create the CitraTest scripts

While CitraTest® has a record feature, manual scripting using the “Capture image/Insert script function” method, results in scripts that are more reliable and easier to debug. After a short learning curve, manual scripts can be created almost as quickly as recorded scripts. When creating a new CitraTest script, use the following steps.
To manually create a CitraTest script:
1
Know precisely what each step in the script will be before starting.
2
Create a new folder for the script.
3
Create a new script in CitraTest.
4
Write comments and code that launch and then shut down the application and test by running the script. The topics below provide detailed procedures.
5
Write comments for each action needed in the script.
6
Code and test the actions commented in Step 5.
Besides creating easily readable code, this method forces the programmer to think about what the script needs to accomplish and how those actions will be performed.
In the following example, a script opens IE, launches Foglight, performs a few actions, and then closes IE.
Option Strict On
Option Explicit On
Module Script
Sub StartScript()
InitScript
'Launch IE to Foglight login page
'Maximize IE
'Login to Foglight
'Click on the End User Overview link
'Log out of Foglight
'Close IE
End Sub
End Module

Use the AppStart function to start applications

The first step to accomplish in many CitraTest® scripts is starting the application. While it is tempting to double-click desktop icons, or use the Start menu to launch an application, the AppStart function is easier and more reliable.
* 
NOTE: AppStart will not work when the application is launched inside a Citrix/Terminal Services Client.
To start an application using the AppStart Function:
1
Launch and maximize the application to be monitored. If the application uses a web browser, set the browser home page to About:Blank.
2
Use CitraTest’s Image Capture to grab a portion of the title bar. Save the image as Launch_TitleBar. For example, if scripting a Foglight login page, capture, and save as an image of the login screen.
3
Select AppStart from the CitraTest Scripting menu. Choose the executable that launches the application and the image of the title bar used to verify the application is running.
* 
NOTE: The path to the executable must be the same on all agent machines.
At the end of the AppStart wizard, a code snippet is inserted into the script. If the application takes a few seconds to load, it is advisable to add a delay argument to the function call. In the example script below, a two second delay has been added.
The script should look like the following.
Option Strict On
Option Explicit On
Module Script
Sub StartScript()
InitScript
'Launch IE to Foglight login page
returnStatus = AppStart ("""C:\Program Files\Internet Explorer\iexplore.exe"" http://stlvmta01:8080", "FglLoginPg.bmp")
If returnStatus <> SUCCESS Then
AbortScriptEx (SCRIPT_FAIL)
Exit Sub
End If
'Maximize IE
'Login to Foglight
'Click on the End User Overview link
'Log out of Foglight
'Close IE
End Sub
End Module
4
Compile and run this script.
* 
NOTE: Allow this script to run completely before doing other scripting.

Maximize applications after AppStart

Maximize the display of the application to ensure that the window matches the script development window size and displays all of the interface.
1
When the application is not maximized, capture, and save an image of the window buttons. Be sure to set the image click point on the maximize button.
2
Add a “click on image” command to the script.
The code should look like the following:
'Maximize IE
returnStatus = ClickOnImage("MaximizeButton.bmp", LEFT_BUTTON, 1, STANDARD_TIMEOUT, "NONE")
If returnStatus <> SUCCESS Then
AbortScriptEx (SCRIPT_FAIL)
Exit Sub
End If
Alternately, the application can be maximized using the window management key commands. This method eliminates the need for the ImageExists function, but does not confirm that the maximize was successful. An ImageExists function can be used to check and maximize if necessary.
KeystrokeVK ("VK_MENU", KEY_PRESS)
KeystrokeString (" ")
KeystrokeString ("x")
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione