Promptium

Created By
sycophant21a year ago
This project is a Java-based UI automation framework that integrates with Appium and utilizes LLMs (like Claude) to drive intelligent test actions on mobile devices and simulators.
Overview

What is Promptium?

Promptium is a Java-based UI automation framework that integrates with Appium and utilizes large language models (LLMs) like Claude to drive intelligent test actions on mobile devices and simulators.

How to use Promptium?

To use Promptium, set up the required environment by installing Homebrew, Node, Appium, and XCode. Then, configure Claude Desktop to communicate with the Promptium MCP server for executing automated tests.

Key features of Promptium?

  • UI Automation with Appium: Supports device interactions such as tap, swipe, and screenshot capture on both simulators and real devices.
  • LLM Integration: Leverages LLMs to interpret natural-language instructions for UI behavior.
  • Model Context Protocol (MCP) Server: Enables context-aware, language-driven test flows.
  • Java-Based Architecture: Ensures reliability and performance in test automation.

Use cases of Promptium?

  1. Automating mobile app testing with natural language commands.
  2. Enhancing test scripts with intelligent decision-making capabilities.
  3. Streamlining UI testing processes for mobile applications.

FAQ from Promptium?

  • Can Promptium automate any mobile application?

Yes! Promptium can automate any mobile application that is compatible with Appium.

  • Is there a specific Java version required?

Yes, Promptium requires Java 17 or higher.

  • How does LLM integration improve testing?

LLM integration allows testers to write test instructions in natural language, making it easier to create and manage test cases.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sycophant21
Star
0
Language
Java
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago