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_name | fill |
| Group | Input |
| Target | Required |
| Value | Required (text) |
| expected_value | Unused |
| TEST_ACCOUNT | Allowed |
| Do not confuse with | type, press |
Target/Value facts match the source-of-truth catalog and Autotest step.
Prerequisites
- The input is visible and enabled.
- For
TEST_ACCOUNT, the queued CASE must have a bound test account.
Steps
- Add a
fillstep. - Set the field Target.
- Choose Value source:
INLINEorTEST_ACCOUNT. - For
INLINE, put the text in Value. - For
TEST_ACCOUNT, set Value to fieldloginorpassword(not the secret itself). - Save.
The step is stored on the autotest. Next - neighbouring steps or autotest run creation.
Examples
Email as plain text
Fields in the UI:
| Field | Value |
|---|---|
action_name | fill |
| Target | kind LABEL, value Email |
| Value | qa@example.com |
| value_source_type | INLINE |
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:
| Field | Value |
|---|---|
action_name | fill |
| Target | kind LABEL, value Password |
| Value | password |
| value_source_type | TEST_ACCOUNT |
| value_source_field | password |
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_ACCOUNTwith a repository page Target on the same step. typeis 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.
Did this page help?