# AI use cases for Artemis (google/artemis) Repo: [google/artemis](https://github.com/google/artemis) | Use cases: 4 | Page: https://dedupedai.com/use-cases/google-artemis/ ARTEMIS is an open source Python tool that turns natural-language instructions into automated tests and tasks on real Android phones and emulators. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run a phone test from your AI IDE chat: https://dedupedai.com/use-cases/google-artemis/drive-android-test-from-ai-ide/ - Check a phone setting from the terminal: https://dedupedai.com/use-cases/google-artemis/run-device-check-from-terminal/ - Assert phone flows inside a pytest suite: https://dedupedai.com/use-cases/google-artemis/add-artemis-to-pytest-suite/ - Install and check the ARTEMIS helper on a phone: https://dedupedai.com/use-cases/google-artemis/prepare-device-for-artemis-runs/ ## How to run a phone test from your AI IDE chat with Artemis Repo: [google/artemis](https://github.com/google/artemis) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Describe a test in your AI IDE and have ARTEMIS run it on a connected Android device. **Who it is for:** A developer or QA engineer who wants to check a build on a real phone without leaving the AI IDE they already use. **The problem:** Checking a build by hand on a phone is slow, and writing scripted UI tests for each new flow takes time. **The outcome:** The AI assistant runs the described flow on the device and returns screenshots and a report of any unexpected popups or failures. ### Steps 1. Run `git clone https://github.com/google/artemis.git && cd artemis` 2. Connect an Android device with USB Debugging enabled, or start an emulator. 3. Run `./start.sh` on macOS or Linux, or `.\start.bat` in Windows PowerShell, and accept the prompt to install the MCP configuration. 4. (Optional) Run `uv run artemis mcp --install all` to install the MCP server and global rules for all supported AI IDEs. 5. Open your AI IDE chat and describe the test scenario in plain language, including the account to use and what to check on the final page. ### Prompt to paste into your agent ```text In the google/artemis repo, use the ARTEMIS MCP tools to run this test on the connected Android device: . Expected output: a pass or fail status, screenshots of the final screen, and a list of any unexpected popups. Verify that the report states which device ran the test. ``` ### Caveat The README lists Antigravity, Claude Code, and Windsurf as the main MCP clients, and the rules file must be added to each IDE by hand for Cursor and Windsurf. Risk, credentials: If the test logs in, use a dedicated test account rather than a personal account, because the agent will type the credentials on the device. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/google-artemis/drive-android-test-from-ai-ide/ ## How to check a phone setting from the terminal with Artemis Repo: [google/artemis](https://github.com/google/artemis) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README Give ARTEMIS a plain-language instruction and read the result in your terminal. **Who it is for:** A developer who wants a quick check of app behavior on a phone without writing test code. **The problem:** Confirming one small screen detail, such as a battery level, means tapping through menus by hand every time. **The outcome:** A structured result in the terminal that says whether the task succeeded and what the device showed. ### Steps 1. Run `git clone https://github.com/google/artemis.git && cd artemis` 2. Connect an Android device with USB Debugging enabled, or start an emulator. 3. Run `./start.sh` on macOS or Linux, or `.\start.bat` in Windows PowerShell, to install the toolchain. 4. Run `uv run artemis run "Open Settings, find Battery and tell me current level" --profile flash` 5. Read the structured terminal output and confirm the reported battery level matches the device screen. ### Prompt to paste into your agent ```text In the google/artemis repo, run `uv run artemis run "" --profile flash` against the connected device. Expected output: a structured terminal result with a success or failure status and the value the device showed. Verify the reported value matches the on-screen value. ``` ### Caveat The README describes the flash profile as best for routine, deterministic UI tasks, so open-ended exploration is better handled with the pro profile. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/google-artemis/run-device-check-from-terminal/ ## How to assert phone flows inside a pytest suite with Artemis Repo: [google/artemis](https://github.com/google/artemis) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Call ARTEMIS from Python and assert on the result in an existing test suite. **Who it is for:** A test engineer with an existing Python test suite who needs to cover a mobile flow in CI. **The problem:** Mobile flows often sit outside the automated test suite because scripted UI tests are costly to write and maintain. **The outcome:** A pytest test that sends a natural-language task to a device and fails the build if the task does not succeed. ### Steps 1. Run `git clone https://github.com/google/artemis.git && cd artemis` and start the host with `uv run artemis ui`. 2. In your test project, run `uv add "artemis-client @ git+https://github.com/google/artemis.git#subdirectory=packages/artemis-client"` 3. Create a pytest file that instantiates `ArtemisClient("http://artemis-host:8000", device_serial="emulator-5554", default_profile="flash")` and awaits `client.run(...)` with your instruction. (inferred, check the README) 4. Add `assert result.succeeded` to the test, using `result.error` or `result.status` in the failure message. 5. Run your pytest suite and confirm the test passes on a known-good build and fails on a known-bad one. ### Prompt to paste into your agent ```text In the google/artemis repo, write a pytest test that uses artemis_client.ArtemisClient to run the instruction: on device . Expected output: a passing pytest result when the task succeeds and a failure message containing result.error or result.status when it does not. Verify the test calls client.run and asserts result.succeeded. ``` ### Caveat The SDK client only talks to a running ARTEMIS host, so the host and the device must be reachable from your CI runner before the test can pass. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/google-artemis/add-artemis-to-pytest-suite/ ## How to install and check the ARTEMIS helper on a phone with Artemis Repo: [google/artemis](https://github.com/google/artemis) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Pre-install the accessibility helper and run diagnostics before a test session. **Who it is for:** A QA engineer preparing a shared test phone before a batch of automated runs. **The problem:** The first task on a device waits about 3 seconds while the helper installs, and a failing helper can disrupt a run mid-task. **The outcome:** A device with the helper installed and a diagnostic report showing whether ARTEMIS can drive it. ### Steps 1. Connect the Android device with USB Debugging enabled, or start an emulator. 2. Run `uv run artemis helper install` to pre-install the helper. 3. Run `uv run artemis helper status` to confirm the helper is installed. 4. Run `uv run artemis doctor` and review the report for any problems. 5. If you do not want the helper, set `ARTEMIS_HELPER_AUTO_INSTALL=false` in `.env` or use `ARTEMIS_HIERARCHY_BACKEND=uiautomator`. ### Prompt to paste into your agent ```text In the google/artemis repo, run `uv run artemis helper install`, then `uv run artemis helper status`, then `uv run artemis doctor` against the connected device. Expected output: the helper status and the doctor report. Verify that the helper is listed as installed before any test task is started. ``` ### Caveat The helper is an accessibility service that reads the screen layout, so a user should review the notice and Settings > Accessibility entry on the phone before installing it. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/google-artemis/prepare-device-for-artemis-runs/