Dan Caseley

I think it's a cool option to have available, but right now I'd rather maintain my baseline and retain my deterministic tests. Caveat: I've not played with the App Quality...

Given you've provided the flow, is the app also something publically available? I fancied trying to investigate this, but didn't want to try writing an app that exposed the enabled...

What would you expect to occur here? What might a solution look like?

Yep. Anything Selector-ish is allowed ``` - runFlow: when: visible: id: my_id ```

@bartekpacia This is awaiting the PR to move through - I think the automation has been a little aggressive 😁

Thought I'd check how this works with the new labels functionality. It's not better. ```yaml appId: com.example --- - assertTrue: condition: ${1==2} label: "1 is the same as 2" ```...

The text is being generated from here: https://github.com/mobile-dev-inc/maestro/blob/319e46626e97e85be04c81d6b095aa47e37dcab4/maestro-orchestra/src/main/java/maestro/orchestra/Orchestra.kt#L317-L320 with the second half coming from here: https://github.com/mobile-dev-inc/maestro/blob/a72aa5717c616009fdc3ef0c5bab05d83872f36d/maestro-orchestra-models/src/main/java/maestro/orchestra/Condition.kt#L42-L44 @denil-ct Would you replace both with a single message, or would it make sense...

I've not had use for the junit part yet. I've got no idea how it works there. Definitely feels like the label should be separate from the error text. e.g....

The label stuff was only merged very recently. Pulled latest? The docs for it describe a bit about why it exists: https://github.com/mobile-dev-inc/maestro-docs/pull/25 Some assertions and waits and taps can look...

@igorsmotto Before I go wading in, can I check that something like this is likely to be accepted? ``` - assertTrue: condition: ${output.result} errorText: "The feed API fetch failed" ```