How-to

Enabled assert (toBeEnabled)

Enabled assert (toBeEnabled) ​

Expect assertion: Target is enabled.

Step model ​

action_nametoBeEnabled
GroupExpect
TargetRequired
ValueUnused
expected_valueUnused
TEST_ACCOUNTForbidden
Do not confuse withtoBeDisabled, toBeEditable

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

Prerequisites ​

  1. Target is a control with an enabled state.

Steps ​

  1. Add a toBeEnabled step.
  2. Set Target.
  3. Leave Value empty.
  4. Save.

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

Examples ​

Save button ​

Fields in the UI:

FieldValue
action_nametoBeEnabled
Targetkind ROLE, value button, name Save

Step JSON fragment (copy-paste):

json
{
  "action_name": "toBeEnabled",
  "target": {
    "kind": "ROLE",
    "value": "button",
    "name": "Save"
  }
}

Common mistakes ​

  • Enabled and editable are different asserts. For a field, use toBeEditable when input matters.

Screenshots ​

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

Version 1.0.0 · Last updated 2026-10-03

Did this page help?