# How to automate Auth0 for instrumented testing my App

**URL:** <https://community.auth0.com/t/how-to-automate-auth0-for-instrumented-testing-my-app/53877>\
**Category:** Get Help\
**Tags:** android\
**Created:** [November 25, 2020, 7:55pm UTC](https://community.auth0.com/t/how-to-automate-auth0-for-instrumented-testing-my-app/53877 "2020-11-25T19:55:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![szaske](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/szaske/32/25845_2.png) [@szaske](https://community.auth0.com/u/szaske)\
**Post date:** [November 25, 2020, 7:55pm UTC](https://community.auth0.com/t/how-to-automate-auth0-for-instrumented-testing-my-app/53877/1 "2020-11-25T19:55:29Z")

</div>

I have an existing Android app that use Auth0 for authentication using the Auth0 web UI. I’ve been asked to automate our UI testing for this app and I’ve decided to use Appium. To keep my tests consistent, I need each test to start by having a user login to my app, which means walking through various Auth0 web pages. I’m hoping Auth0 has created some sort of helper functions to make this sort of testing easier. Currently when I walk through the Auth0 using the Appium Inspector I see no Id’s or AccessibilityId’s on the various Auth0 views/controls within the web pages, making it even more difficult. Has anyone else tried to do this or have suggestions on how to do it? It’s not impossible, but I was hoping it would be easier. I can’t be the only person wanting to automate the Auth0 UI.

---

<div class="post-metadata">

**Author:** ![evgenia.rud](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/evgenia.rud/32/37679_2.png) [@evgenia.rud](https://community.auth0.com/u/evgenia.rud)\
**Post date:** [May 30, 2022, 6:41am UTC](https://community.auth0.com/t/how-to-automate-auth0-for-instrumented-testing-my-app/53877/2 "2022-05-30T06:41:56Z")

</div>

I faced the same problem. How is this resolved?