You can edit text inputs to replace a sequence of keyboard
events with text strings that are easier to handle as datapool variables
or references.
Before you begin
Text inputs describe a series of low-level keyboard events
as a single text string. Text inputs can be added only inside window
events.
In most cases, you will rely on the text inputs that
were recorded with the test. The recording attempts to factor multiple
key presses into text input events. However, in some cases, you might
need to manually factor keyboard events that are redundant or poorly
recorded. For example, in some cases, a text input string Hello can
be recorded as a press on the Shift key, a
stroke of the H key, a release of the Shift key,
a stroke of the E key, and finally a text input
of llo. By manually factoring keyboard actions
into text inputs, you can handle text from datapool variables and
references.
Note: Because Citrix tests contain
low level user input and synchronizations, minor changes can prevent
the test from working. When editing these tests, you must ensure that
they are functionally identical.
Procedure
- Open the test in the test editor
- Expand a window event.
- To edit a text input, select the action in the Test
Contents area.
- To create a new text input at a specific location, select
an action and click Insert and Citrix
Text.
- In the Test Element Details area,
edit the text string that will be entered during the test.
- You can specify the think time for the keyboard event.
This emulates the time spent by a user before initiating the current
event.