KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#developer-tools #typescript #claude-code #codex #dsh #dsh-plugin #ai-agent #ai-agents #deepseek-harness #agent-skills #macos #cli

noqa

★ 162 Open GitHub ↗

Automated mobile testing tool with device CLI for apps and games - real devices iOS & Android. Supports native (swift, kotlin), react native, flutter, KMP, unity and any mobile apps and games.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

### Automated mobile testing tool for apps and games

[![Download for macOS](https://img.shields.io/badge/Download_for_macOS-111111?style=for-the-badge&logo=apple&logoColor=white)](https://noqa.ai/download/)

[![Website](https://img.shields.io/badge/website-noqa.ai-111111?style=flat-square)](https://noqa.ai)
[![Docs](https://img.shields.io/badge/docs-docs.noqa.ai-111111?style=flat-square)](https://docs.noqa.ai)
[![Stars](https://img.shields.io/github/stars/noqa-ai/noqa?style=flat-square&logo=github&label=stars&color=111111)](https://github.com/noqa-ai/noqa/stargazers)

<sub>Apple Silicon and Intel · Windows is on the way</sub>

</div>

noqa is an automated mobile testing tool for apps and games. Write tests in plain English and run them on a real device. noqa works from screenshots, so there are no locators, no code and no SDK. As teams ship more code with AI, noqa automates slow manual testing.

- **Any framework, even games — no locators** — native, React Native, Flutter, Unity, Unreal, and non-native UI (maps, canvases, WebViews, ads) all test the same, with no locators or scripts.
- **CLI with automatic grounding** — your coding agent runs the whole testing cycle from the terminal: it reads the screen, drives a real device, writes the test cases, and runs them until they pass. Where the screen exposes no usable element tree — a game, a canvas, a WebView — it targets by plain-language description and noqa grounds it.

`noqa action tap -d "Blue login button at the bottom"`
- **Runs on real devices** — plus simulators, emulators, and cloud devices.

</div>

## Purely vision-based test automation

noqa works from screenshots, unlike locator-based tools (Appium · Maestro · XCUITest).

| | Locator-based | noqa |
|---|:---:|:---:|
| **Native apps** <br/><sub>iOS & Android</sub> | ✅ | ✅ |
| **Cross-platform apps** <br/><sub>React Native, Flutter</sub> | Partial | ✅ |
| **Non-native UI** <br/><sub>webviews, canvases, ads, maps</sub> | ❌ | ✅ |
| **Games** <br/><sub>Unity, Unreal, Godot</sub> | ❌ | ✅ |
| **Alerts & pop-ups** <br/><sub>permissions, system dialogs</sub> | Flaky | ✅ |
| **Natural-language tests** <br/><sub>no code</sub> | ❌ | ✅ |
| **Real devices** <br/><sub>physical phones, not just simulators</sub> | Partial | ✅ |

## Quick start

**1. Install the app.** [Download noqa](https://noqa.ai/download) and keep it running — the CLI talks to it locally.

**2. Create a free account.**

**3. Install the CLI and skill.** In the app, open **Settings → CLI & Agents** and click **Install** on **CLI Tool** (adds `noqa` to your `PATH`) — then **Install globally** on **Mobile Testing Skill**, so your coding agent knows the commands out of the box. Restart your terminal afterward. The skill also lives here in [`skills/noqa-testing`](skills/noqa-testing) if you'd rather add it manually.

**4. Connect a device.** List devices, pick one, and connect:

```bash
noqa devices ios                       # list iOS devices & simulators (or: noqa devices android)
noqa devices connect <device-id>       # connect to one from the list
```

**5. Get your app on the device.** Install your build (Xcode, Expo, Android Studio) and bring it to the foreground:

```bash
noqa action activate-app --bundle-id com.example.app
```

**6. Debug it in an inspect → act → verify loop.**

```bash
noqa screen                                    # inspect: read the current UI as a structured element tree
noqa action tap --x 500 --y 320                # act: one step, on relative coordinates (0–1000) from the tree
noqa action tap -d "Login button"              # …or by description — grounding, when the tree has no usable target
noqa screen                                    # verify: confirm the state changed as expected
```

## CLI

Point your coding agent at the CLI and it drives the device in a tight **inspect → act → verify** loop — read the screen, take one action, check the result, repeat. Two command groups make up the loop.

### Reading the screen

```bash
noqa screen                 # cleaned element tree — meaningful elements with relative coordinates (0–1000)
noqa screen --full          # raw Appium accessibility tree, unfiltered
noqa screenshot ./shot.png  # save a screenshot for a visual check
```

Your agent reads the screen on *every* step, so read cost dominates. The cleaned tree keeps the meaningful elements with exact positions — far lighter than the raw tree, cheaper than a screenshot. Measured on one paywall screen:

| Screen read | Tokens | vs `noqa screen` |
|---|---:|---:|
| `noqa screen` | ~800 | 1× |
| `noqa screenshot` | ~1,500 | ~2× |
| `noqa screen --full` | ~5,600 | ~7× |

### Actions

Every gesture targets an element two ways. `noqa screen` already returns each element's box, so on a screen the tree describes well you act straight on those coordinates (0–1000) — nothing to resolve, nothing to pay for:

```bash
noqa action tap --x 500 --y 320                         # tap
noqa action swipe --x1 500 --y1 800 --x2 500 --y2 200   # swipe between two points
noqa action drag --x1 300 --y1 500 --x2 700 --y2 500    # drag between two points
noqa action input --x 500 --y 640 --text "hi@noqa.ai"   # tap a field and type
```

When the tree gives you nothing to act on — a game, a canvas, a WebView, an ad overlay, or coordinates that didn't work — describe the element in plain language instead and noqa **grounds** it, working from what's rendered rather than from the tree:

```bash
noqa action tap -d "Blue login button at the bottom"    # tap
noqa action tap -d "Login button" --double              # double tap
noqa action tap -d "Login button" --duration 2          # long-press, in seconds
noqa action swipe -d "photo carousel, swipe left"       # swipe
noqa action drag -d "card onto the drop zone"           # drag
noqa action input -d "email field" --text "hi@noqa.ai"  # type into a field
```

App and system controls take no target:

```bash
noqa action activate-app --bundle-id com.example.app    # bring an app to the foreground
noqa action terminate-app --bundle-id com.example.app   # force-quit an app
noqa action restart-app --bundle-id com.example.app     # terminate and relaunch
noqa action background-app                              # send the current app to the background
noqa action open-url --url "https://appium.io"          # open a deep link or URL
noqa action alert --action accept                       # accept a system alert (or --action dismiss)
```

Full command reference: [docs.noqa.ai/docs/cli](https://docs.noqa.ai/docs/cli).

If you want your agent to run the whole testing cycle — not just drive the device — see [Generate test cases with AI](https://docs.noqa.ai/guide/full-cycle-testing).

## Test cases

A test case is a title, optional tags, and one or more flows. Each flow is written in plain language — no code, no selectors.

</div>

- **Title** — a short name for the test.
- **Tags** — optional labels to group and filter cases (`smoke`, `regression`, …).
- **Instructions** — what the agent should do, step by step.
- **Expected result** — what it should verify after each step (optional).

Create and manage them in the app or from the CLI:

```bash
noqa cases create myapp '{"title": "Login", "tags": ["smoke"], "flows": [{"instructions": "tap Sign in, enter credentials", "result": "home screen shows"}]}'
noqa cases list myapp                       # list cases (ID, TITLE, TAGS)
noqa cases get myapp 42                      # show a case as JSON
noqa cases update myapp 42 '{"title": "…"}'  # edit fields of a case
```

See [Writing good test cases](https://docs.noqa.ai/guide/writing-test-cases).

## Production-ready testing

Beyond the free CLI, a subscription unlocks noqa's own agent and, for teams, the full platform.

### noqa agent

Our own agent, built specifically for mobile testing rather than a general-purpose model driving a device. Hand it your test cases and it runs them autonomously on the device, returning per-step pass/fail.

- **Fast** — 5–10s per action, dropping to 1–2s on screens it has already seen.
- **Cheaper per action than a frontier LLM API.**
- **Reports** — per-step pass/fail with video and screenshots.

### Agentic QA platform

Everything in the noqa agent, scaled for teams — run the whole suite in the cloud and wire it into your workflow.

- **1000+ cloud devices.**
- **Unlimited seats**, with shared test cases and builds.
- **Integrations** — Slack, Jira, CI/CD, Webhooks, API, MCP server.
- **Priority support.**

Full pricing → [noqa.ai/pricing](https://noqa.ai/pricing).

## Requirements

**The app**
- Mac with Apple Silicon or Intel — one universal build
- macOS 13 or later

**iOS testing** — real devices & simulators
- Xcode 16.0+ with Command Line Tools
- Apple Developer account (for signing and provisioning)
- A real device on iOS 15+ (trusted, visible in Finder), or an iOS Simulator

**Android testing** — real devices & emulators
- Android Studio 2023.1+ (Android SDK + `adb`)
- A real device on Android 6.0 (API 23)+ with USB debugging enabled, or an emulator with Google Play Services

## Learn more

New to agentic testing? The [guide](https://docs.noqa.ai/guide/introduction) covers it end to end:

- [Introduction](https://docs.noqa.ai/guide/introduction) — what agentic QA is and why vision-based testing is different
- [How the noqa agent works](https://docs.noqa.ai/guide/how-noqa-agent-works) — the perception–decision–action loop, actions, speed, and limits
- [Writing good test cases](https://docs.noqa.ai/guide/writing-test-cases) — phrasing cases the agent can run reliably
- [Local vs cloud](https://docs.noqa.ai/guide/local-vs-cloud) — when to use local devices and when to use the cloud
- [Device CLI](https://docs.noqa.ai/guide/device-cli) — let a coding agent drive a device
- [Generate test cases with AI](https://docs.noqa.ai/guide/full-cycle-testing) — your agent writes the cases, walks them on a device, and runs them
- [Best practices](https://docs.noqa.ai/guide/best-practices-games) — games, in-app purchases, cross-app flows, non-native UI, and more

## FAQ

**Which devices and platforms are supported?**
iOS and Android — real devices, simulators, and emulators locally, plus cloud devices. noqa drives them through Appium (XCUITest on iOS, UiAutomator2 on Android).

**Which frameworks and engines are supported?**
All of them. noqa works purely from screenshots, so it doesn't depend on how the app is built: native, React Native, Flutter, Unity, Unreal, and non-native UI like maps, canvases, WebViews, and ads.

**Do I need to integrate an SDK or change my app?**
No. Nothing to add or change in your app.

**Do I need an account, and do I have to pay?**
An account is required — grounding and test cases run through noqa's servers — but a free one is enough. You only pay to run the noqa agent and use cloud features.

**Does noqa work on Windows or Linux?**
Not yet — the app runs on macOS only, on both Apple Silicon and Intel. Windows is on the way.

**Can I use it with Claude Code / Cursor / Codex?**
Yes, through the CLI. Any coding agent that can run shell commands drives noqa; install the `noqa-testing` skill so it knows the commands.

## License

The contents of this repository — the [`noqa-testing`](skills/noqa-testing) skill and this documentation — are [MIT licensed](LICENSE): copy, adapt, and share them freely. The noqa app, CLI, and agent themselves are proprietary.

noqa

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README