You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can do this with the existing assertVisible command.
- assertVisible:
id: ViewA
text: ${output.viewA}
This would assert that an element is visible with both the ID and the expected text. It's not an explicit text matcher, but under the hood, it'd be the identical operation.
@Fishbowler yes but it is not as comprehensive. If I want to have assertion that the particular element in the screen should not have a particular text then I cannot do that with above approach. Some basic assertions we can do with above approach but not all.
I think you can do all the things, but like in your original post, they're all slightly long winded and indirect.
I wonder if this is something a community member would pick up? It's a nice full stack feature, but all of the mechanics are already present as prior art.
Use case
If we want to assert that an element has an expected test , currenlty we need to do below :
it does not make sense
Proposal
May be we can have
assertEquals
id:
expected:
assertNotEquals
id:
expected:
assertContains
id:
expected:
assertNotContains
id:
expected:
Anything else?
No response
The text was updated successfully, but these errors were encountered: