How-to

Field fill (fill)

Field fill (fill)

Clears the field and pastes the full text. For login and password use source TEST_ACCOUNT. Do not confuse with type (per-character input).

Step model

action_namefill
GroupInput
TargetRequired
ValueRequired (text)
expected_valueUnused
TEST_ACCOUNTAllowed
Do not confuse withtype, press

Target/Value facts match the source-of-truth catalog and Autotest step.

Prerequisites

  1. The input is visible and enabled.
  2. For TEST_ACCOUNT, the queued CASE must have a bound test account.

Steps

  1. Add a fill step.
  2. Set the field Target.
  3. Choose Value source: INLINE or TEST_ACCOUNT.
  4. For INLINE, put the text in Value.
  5. For TEST_ACCOUNT, set Value to field login or password (not the secret itself).
  6. Save.

The step is stored on the autotest. Next - neighbouring steps or autotest run creation.

Examples

Email as plain text

Fields in the UI:

FieldValue
action_namefill
Targetkind LABEL, value Email
Valueqa@example.com
value_source_typeINLINE

Step JSON fragment (copy-paste):

json
{
  "action_name": "fill",
  "target": {
    "kind": "LABEL",
    "value": "Email"
  },
  "value_text": "qa@example.com",
  "value_source_type": "INLINE"
}

Password from the test account

Fields in the UI:

FieldValue
action_namefill
Targetkind LABEL, value Password
Valuepassword
value_source_typeTEST_ACCOUNT
value_source_fieldpassword

Step JSON fragment (copy-paste):

json
{
  "action_name": "fill",
  "target": {
    "kind": "LABEL",
    "value": "Password"
  },
  "value_text": "password",
  "value_source_type": "TEST_ACCOUNT",
  "value_source_field": "password"
}

Common mistakes

  • Do not store passwords in INLINE for lasting scenarios - use TEST_ACCOUNT.
  • Do not combine TEST_ACCOUNT with a repository page Target on the same step.
  • type is slower and only needed when the product expects per-character input.

Screenshots

Screenshots of the step form for fill will be added here in a later pass.

Version 1.0.0 · Last updated 2026-09-11

Did this page help?