Our approach

@uuv (User centric Usecases Validator) is an ecosystem that simplifies End to End test writing and execution using BDD (Behaviour Driven Development) and a user-centric approaches. Written E2E tests are therefore understandable by any human being.

This approach is very web-centric. But we wanted to experiment with mobile.

We were surprised at the number of ways to build a mobile application, just by looking at Android.

Approaches aren't the same, and there doesn't seem to be a standard way of including useful information for digital accessibility.
We're offering this beta version, which implements some user-centric sentences to check the relevance of the approach in the mobile context.

Available sentences

I see {'text'} text

Checks that the specified text is present

I should see a button named {'My button'}

Checks that a button exists with the specified accessible name

I should not see a button named {'My button'}

Checks that a button does not exist with the specified accessible name

I tap on a button named {'My button'}

Tap on a button with the specified accessible name

I should see a text field named {'a TextField'}

Checks that a text field exists with the specified accessible name

I should see a title named {'First title'}

Checks that a title exists with the specified accessible name

Source