Test account values in steps ​

Test account values in steps inject login or password into Value without storing the secret in step text. Source TEST_ACCOUNT reads an account field from the running CASE; source INLINE stores the string on the step itself.

Steps ​

1. Open the CASE card and bind a test account if it is not bound yet.
2. Open a step that has Value (fill, type, press, selectOption, toHaveText, toHaveAttribute, and other actions where the source is allowed).
3. Set Value source to TEST_ACCOUNT.
4. In Value, set the account field: login or password (not the secret itself).
5. Confirm Target is not a repository page on this step.
6. Save the step.

At run time the worker substitutes the field value from the bound CASE account. COMMON steps with TEST_ACCOUNT also use that CASE account.

INLINE and TEST_ACCOUNT ​

Rules ​

• Kind CASE must have an account if any step in the chain (including COMMON predecessors) requests TEST_ACCOUNT. Otherwise the run fails.
• Kind COMMON has no account of its own. When it runs as a predecessor, it uses fields from the queued CASE account.
• TEST_ACCOUNT is forbidden for goto, waitForURL, toHaveURL, and waitForTimeout.
• TEST_ACCOUNT cannot be combined with a repository page Target on the same step.

Examples ​

Fill login and password ​

[
  {
    "action_name": "fill",
    "target": { "kind": "LABEL", "value": "Email" },
    "value_text": "login",
    "value_source_type": "TEST_ACCOUNT",
    "value_source_field": "login"
  },
  {
    "action_name": "fill",
    "target": { "kind": "LABEL", "value": "Password" },
    "value_text": "password",
    "value_source_type": "TEST_ACCOUNT",
    "value_source_field": "password"
  }
]

INLINE for non-secret text ​

{
  "action_name": "fill",
  "target": { "kind": "LABEL", "value": "Search" },
  "value_text": "login form",
  "value_source_type": "INLINE"
}

Forbidden actions ​

Do not set TEST_ACCOUNT on steps like this:

{
  "action_name": "goto",
  "value_text": "/login",
  "value_source_type": "INLINE"
}

Paths and URLs always use INLINE.