Creating Test Scenario
Remote desktop connections need to be maintained 24/7 to all the ScenarioStations in order for the scenario images to be buffered and to prevent any errors in scenario playback. Keep the following in mind before you start creating your scenario(s):
No matter which installation method you choose, there are various approaches that let you create scenarios and monitor ScenarioStation(s). The sections below describe two of them.
>Monitor stations using the Console
There are several tools (i.e. VMware vSphere, Microsoft Hyper-V, VMware Workstations and etc.) that can be used to connect to a machine.
Tip: For information on how to do this, see the VM software documentation.
>Monitor stations using the ScenarioStation RDP Manager (SSrdpManager)
Besides using one of the consoles mentioned above, you can also use SSrdpManager to connect to stations. Using the ScenarioStation RDP Manager tool for RDP connections to ScenarioStations provides two distinct advantages. First, with the SSrdpManager, you can maintain an active RDP to multiple ScenarioStations with a single remote session tool. Second, the SSrdpManager can be minimized without interrupting scenario play back. It is ideal for monitoring one or more ScenarioStations from a single desktop, and it provides a non-intrusive way to keep a ScenarioStation session active while running in Standard mode.
It is a good practice to create your scenario(s) using SSrdpManager. The reason for doing this is that by creating the scenario in the environment that the test will run, the differences in scenario creation environment and test environment are minimized.
For this purpose, you need to install ScenarioBuilder on the same machine in which the ScenarioStation will be installed. Therefore, there will not be any differences between the scenario creation environment and the performance monitoring environment.
Please follow the next steps in order to learn how to create user scenario(s).
Important: If AppsWatch and ScenarioStation are both installed on the same PC, skip this step. SSrdpManager is not needed when running AppsWatch and a single instance of Scenariostation on a PC. In addition, the SSrdpManager.exe can be copied onto and ran from any machine.
The SSrdpManager is an option that is offered by AppsWatch to monitor ScenarioStations. SSrdpManager allows users to create RDP connections to one or all the ScenarioStations. Through these connections the user can create Scenarios and monitor the ScenarioStations.
Once you install AppsWatch, SSrdpManager will also be installed. You can find it in the AppsWatch’s folder in your machine.
The SSrdpManager will open.
Click “Create a connection file”
Enter a File Name and click “Save”.
A new connection form will open;
Click “Add” to create a new connection.
Once all the fields are filled out, click “Save” to complete the configuration and connect to the Station.
Upon connecting, the Station will open inside of a window within the SSrdpManager.
Note that the connection credentials should be correct. Otherwise, SSrdpManager will not be able to establish the connection. To test that connection credentials are correct, try to connect to the user using a Windows Remote Desktop Connection.
Create a Scenario using ScenarioBuilder
Scenarios are the action sequences which emulate real user interactivity with your application. Creating your first scenario is simple. If you know how to use your application, then you know how to create a scenario with ScenarioBuilder.
In order to start creating your scenario, Double-click the ScenarioBuilder shortcut to launch the splash screen.
When it launches for the first time, ScenarioBuilder will ask you to create a new project.
Enter a project name and click “Create”.
In this section, we want to create a simple scenario that opens Citrix Receiver in a web browser and logon to Citrix Web Interface with parameterized user name/password. You can see the steps below:
Click “New” from ScenarioBuilder toolbar or click the “New Scenario” from the Splash Screen to create a new scenario.
Name your scenario and click “Open web app:” button.
Next, enter the proper URL and click “OK”.
ScenarioBuilder will open the URL on the default web browser.
Then capture a proper image using ScenarioRecorder.
Enter an image name and click “Accept”.
After that, click on the textbox to start parameterization of login process using ScenarioRecorder.
Note: To genuinely replicate real world impact on an application, parameterizing data is critical. In ScenarioBuilder you can access unlimited rows of data values, stored in comma separated values (CSV) files, to make each playback of a Scenario a unique, real-user experience.
Press the key Tab to go to the next textbox;
Finally, click “Log On” button.
These are the recorded actions for our script:
In the edit mode, you can simply add, delete or modify actions wherever necessary.
Note: Add an “On Failure” series of actions to your scenario so that it recovers, re-sets and continues in your performance monitoring environment. The “On Failure” section determines what actions to take in the event your Scenario or component fails, and should always be located at the end of the scenario or component. A “Resume” action in conjunction with “On Failure” will allow your scenario to pick up where it left off prior to the failure. Note that “On Failure” is an excellent way to handle intermittent pop-ups like security warnings.
Tip: Increase image action Timeout values before sending your scenario to the Base. The default value of 10 seconds might be sufficient when playing back in ScenarioBuilder, but in your performance monitoring environment resources will be taxed and pages will load more slowly. Recommended Timeout value = 30 or 60.
Here is the final scenario:
Done and done! ScenarioBuilder offers a rich array of Actions to emulate virtually any user activity in your application. Start simple, there’s plenty of time to dig into ScenarioBuilder’s sophisticated feature set.
Important: Note that you can create different scenario(s) for any application (i.e. Notepad, Medical application, etc.)