test condition

[balloob]

Breaking change

Proposed change

Allow testing conditions.

CleanShot.2022-03-03.at.21.39.55.mp4

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[frenck]

Nice!

I do wonder if the color of the button is clear enough though. It feels like it almost provided no feedback on the result (as in it might be confused with the feedback on the click itself, not the click result).

[matthiasdebaat]

We can use the same pattern as we have for Configuration validation:
Valid prototype
Invalid prototype

[balloob]

The test button is not about if the condition is valid but if it tests true right now (side effect is validating it or else we can't test it, but most things made via UI will be valid)

[bdr99]

This is a great feature, but those affected by color blindness might have a hard time distinguishing between those two colors, considering that red-green color blindness is the most common form of color blindness. It might be helpful to add some kind of additional visual feedback, such as a ✅ or ❌ to indicate whether the condition tested true.

[balloob]

Added icons to the progress button

CleanShot.2022-03-08.at.11.36.24.mp4

[zsarnett]

Why not use the X if we are using the check?

[balloob]

because I felt like X could also indicate bad config.