How-to
Enabled assert (toBeEnabled)
Enabled assert (toBeEnabled)
Expect assertion: Target is enabled.
Step model
action_name | toBeEnabled |
| Group | Expect |
| Target | Required |
| Value | Unused |
| expected_value | Unused |
| TEST_ACCOUNT | Forbidden |
| Do not confuse with | toBeDisabled, toBeEditable |
Target/Value facts match the source-of-truth catalog and Autotest step.
Prerequisites
- Target is a control with an enabled state.
Steps
- Add a
toBeEnabledstep. - Set Target.
- Leave Value empty.
- Save.
The step is stored on the autotest. Next - neighbouring steps or autotest run creation.
Examples
Save button
Fields in the UI:
| Field | Value |
|---|---|
action_name | toBeEnabled |
| Target | kind 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
toBeEditablewhen input matters.
Screenshots
Screenshots of the step form for toBeEnabled will be added here in a later pass.
Did this page help?