+test_failure "--condition event-rule-matches --capture: missing argument (end of arg list)" \
+ 'Error: While parsing argument #7 (`--capture`): Missing required argument for option `--capture`' \
+ --action notify \
+ --condition event-rule-matches --type=user --capture
+
+test_failure "--condition event-rule-matches --capture: missing argument (before another option)" \
+ 'Error: While parsing expression `--action`: Unary operators are not allowed in capture expressions.' \
+ --condition event-rule-matches --type=user --capture \
+ --action notify \
+
+test_failure "--condition event-rule-matches --capture: binary operator" \
+ 'Error: While parsing expression `foo == 2`: Binary operators are not allowed in capture expressions.' \
+ --condition event-rule-matches --type=user \
+ --capture 'foo == 2' --action notify
+
+test_failure "--condition event-rule-matches --capture: unary operator" \
+ 'Error: While parsing expression `!foo`: Unary operators are not allowed in capture expressions.' \
+ --condition event-rule-matches --type=user \
+ --capture '!foo' --action notify
+
+test_failure "--condition event-rule-matches --capture: logical operator" \
+ 'Error: While parsing expression `foo || bar`: Logical operators are not allowed in capture expressions.' \
+ --condition event-rule-matches --type=user \
+ --capture 'foo || bar' --action notify
+
+test_failure "--condition event-rule-matches --capture: accessing a sub-field" \
+ 'Error: While parsing expression `foo.bar`: Capturing subfields is not supported.' \
+ --condition event-rule-matches --type=user \
+ --capture 'foo.bar' --action notify
+
+test_failure "--condition event-rule-matches --capture: accessing the sub-field of an array element" \
+ 'Error: While parsing expression `foo[3].bar`: Capturing subfields is not supported.' \
+ --condition event-rule-matches --type=user \
+ --capture 'foo[3].bar' --action notify
+
+test_failure "--condition event-rule-matches --capture: missing colon in app-specific context field" \
+ 'Error: Invalid app-specific context field name: missing colon in `foo`.' \
+ --condition event-rule-matches --type=user \
+ --capture '$app.foo' --action notify
+
+test_failure "--condition event-rule-matches --capture: missing colon in app-specific context field" \
+ 'Error: Invalid app-specific context field name: missing type name after colon in `foo:`.' \
+ --condition event-rule-matches --type=user \
+ --capture '$app.foo:' --action notify