Android QA Automation on Real Device + API Trigger (Staging/Test Environment)

IMPORTANT — READ BEFORE REVIEWING
This is a fixed-price "turnkey" project. An experienced QA Automation / Mobile Integrator is needed to establish a stable automated UI testing system on a physical Android device and integrate it with my backend via a simple HTTP API.

1) Project Goal

To build a system where my server sends an HTTP request, and a physical Android phone runs a pre-agreed test scenario in the mobile application (or in our test application/demo).

Workflow (example):

• API Trigger: POST /run_test {scenario_id, params}

• Environment Preparation: check that the application is open and the user is logged in (in the test account/staging)

• UI Automation: navigating through screens, entering data, pressing “Confirm/Next”

• Reporting: returning the result success/error, logs, and screenshot of the final screen (or error)

Important: the project is intended for QA/staging environment and controlled scenarios, without bypassing security mechanisms and without unauthorized actions.

2) Technical Requirements (stack)

I expect experience with one or more solutions:

• Android UI automation: Appium (real device), UIAutomator2, Espresso (if needed), or Tasker/AutoInput (if this is a QA stand and you guarantee stability)

• API bridge: a small service (locally/on the server) that accepts HTTP commands and runs the scenario on the device

• Logs/screenshots: automatic collection of run artifacts (screenshot + logs)

3) Handling confirmation codes (if needed)

If the test scenario requires confirmation codes (2FA), the solution must be legal and testable, for example:

• test OTP/seed in staging environment

• receiving the code through official test channel (sandbox/QA inbox/test provider)

• or a manual step if 2FA automation is not available under the service rules

4) Deliverables

• Configured physical Android device / or instructions for deployment on my device

• API endpoint for running scenarios

• Stable scenarios + recovery from failures (restart app, return to the desired state)

• Documentation: how to reproduce the setup on another phone

5) Timeline and Budget

• MVP: 1–2 weeks (or your realistic plan)

• Fixed price for a fully ready solution

6) How to apply (3 questions)

1. Which tool will you choose for UI automation on real Android and why?

2. How will you organize the API trigger and reports (logs/screenshots)?

3. Have you built similar systems for QA/staging scenarios before? Provide examples.