SilkPerformer Citrix Tutorial - Borland Technical Publications

More documents

Recommendations

Info

6 BEST PRACTICES Recording Use Cases Launching the application Using keyboard shortcuts Using the Alt key Maximizing windows Keeping the systemunder-test clean Try launching the application via the Windows Run command. Launching the application via a desktop icon or mouse click may also work, but consider if you will be moving the application to a different server, or if the GUI will vary between users, in which case a desktop icon might appear in a different location. It is therefore recommended that you type the path to the application’s .exe file in the Windows Run command window. Mouse clicks require x/y coordinates, a window reference, and the target window must have focus. While GUI load-testing technologies for tracking mouse clicks have become increasingly reliable, MS Windows remains a dynamically changing environment, so you must build scripts that can tolerate minor inconsistencies. One way to do this is to use keyboard shortcuts. For shortcuts, the only requirement is window focus. Note The Windows Logo key is not supported, as it moves the focus away from the Citrix Recorder. Almost all menu systems in Windows applications have Alt key combinations that can be used to initiate specific menu commands. To record use of an Alt key shortcut, first give your application focus, then press the Alt key—this gives the menu system focus. Notice that many of the menu items have one of their letters underlined. This indicates which Alt-key commands are available for specific menu items. Press appropriate letter keys to gain access to sub-menus until you reach the menu item that you want to initiate. In some cases, a menu item itself will have a key combination. For example, to open a document in Microsoft Word use the Ctrl+O combination. This shortcut does not require that the menu have focus. If keyboard shortcuts are not available and you must use the mouse, you can reduce the chance of triggering inaccurate mouse clicks by maximizing the window that you are working with. This places the window in a fixed position each time it is used and, in turn, makes mouse clicks more accurate. As a general rule, if a window allows for maximization, it is recommended that you take advantage of it. Note Alt-Space, X is the Windows keyboard combination for maximizing an active window When a window does not allow for maximization, during the recording session, move the window to the upper left-hand corner of the desktop before clicking. When recording, the recorder may not be able to pick up on the window handle that you have in the foreground, so having the coordinates relative to the desktop is a must. To eliminate unexpected detours during terminal services sessions, ensure that you keep your Windows desktop as uncluttered as possible. Imagine, for example, that while your script is replaying, a Windows network message appears—your script will break because the subsequent mouse click will go to 68 SilkPerformer Citrix Tutorial
6 BEST PRACTICES Recording Use Cases the Windows network message window instead of your intended application window. Ensuring correct Before clicking a window, ensure that the window you intend to click exists and focus has focus. Here is a sample BDL function that helps automate this process: function MyCitrixWaitForWindowCreationAndActivation(sCaption:string; nMatch : number optional; nStyle : number optional; nX : number optional; nY : number optional; nWidth : number optional; nHeight : number optional ) : number var hwndNewWindow : number; // hwnd of the new window created nRTT:number; begin // // Check if window exists // hwndNewWindow := CitrixSearchWindow(sCaption, nMatch); hwndNewWindow := 0; // // If window doesn’t exist, wait for creation // if (hwndNewWindow < 1) then hwndNewWindow := CitrixWaitForWindowCreation(sCaption, nMatch, nStyle, nX, nY, nWidth, nHeight); end; // // Check if window is already active, wait if it’s not active // MyCitrixWaitForWindowActivate(hwndNewWindow); MyCitrixWaitForWindowCreationAndActivation:=hwndNewWindow; end MyCitrixWaitForWindowCreationAndActivation; Using parameters Adding verifications If you input the same information more than once, the system under test caches the data in memory rather than repeating the same work. For this reason it is important that you vary input/request data so that the work is as realistic as possible. For example, use different user accounts that have different data ranges. This can be accomplished using a CSV (comma separated values) file as input for a load test (see the Parameter Wizard section in SilkPerformer’s Online Help for detailed information). Verifications are checks that are added to code to check if the responses that are received from the server are correct. When performing GUI based load testing, verifications are automatically added to your script via window SilkPerformer Citrix Tutorial 69
Page 1 and 2:
Citrix Tutorial SilkPerformer®2010
Page 3 and 4:
Contents Introduction 1 Overview .
Page 5 and 6:
Introduction About these tutorials
Page 7 and 8:
INTRODUCTION Support for Citrix Ter
Page 9 and 10:
INTRODUCTION Support for Citrix Ter
Page 11 and 12:
1 Defining 1Chapter Load Test Proje
Page 13 and 14:
1 DEFINING LOAD TEST PROJECTS Defin
Page 15 and 16:
2 Creating 2Chapter Test Scripts In
Page 17 and 18:
2 CREATING TEST SCRIPTS Creating a
Page 19 and 20:
2 CREATING TEST SCRIPTS Creating a
Page 21 and 22: 2 CREATING TEST SCRIPTS Creating a
Page 23 and 24: 2 CREATING TEST SCRIPTS Screen Sync
Page 25 and 26: 2 CREATING TEST SCRIPTS Screen Sync
Page 27 and 28: 2 CREATING TEST SCRIPTS Verificatio
Page 29 and 30: 2 CREATING TEST SCRIPTS Verificatio
Page 31 and 32: 2 CREATING TEST SCRIPTS Trying Out
Page 45 and 46: 3 Customizing 3Chapter User Data In
Page 47 and 48: 3 CUSTOMIZING USER DATA Customizing
Page 53 and 54: 4 Testing 4Chapter Citrix Web Inter
Page 55 and 56: 4 TESTING CITRIX WEB INTERFACE SESS
Page 57 and 58: 5 Citrix 5Chapter Project & System
Page 59 and 60: 5 CITRIX PROJECT & SYSTEM SETTINGS
Page 65 and 66: 6 Best 6Chapter Practices Introduct
Page 67 and 68: 6 BEST PRACTICES Test Preparation U
Page 69 and 70: 6 BEST PRACTICES Test Preparation I
Page 71: 6 BEST PRACTICES Recording Use Case
Page 75 and 76: 6 BEST PRACTICES Troubleshooting Sc
Page 77 and 78: 6 BEST PRACTICES Issues Specific to
Page 79 and 80: 6 BEST PRACTICES Issues Specific to
Page 81 and 82: Index A Adding timers 70 Adding ver
Page 83 and 84: SilkPerformer Citrix Tutorial 79
show all

SilkPerformer Citrix Tutorial - Borland Technical Publications

Create successful ePaper yourself

Delete template?

Save as template?