Suggestion: Relay as a complementary Android testing MCP server
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- android
- Domain
- mobile-dev, testing-qa
Research direction
The issue names no AutoGenesis files, tests, or entry points. Start by clarifying whether Relay integration is wanted and which configuration, orchestration, and reporting surfaces would be affected; a concrete integration scope and acceptance criteria are needed before completion can be verified.
Written by the indexing model from the issue text.
Description
Hi AutoGenesis team! Really interesting approach — building an AI-powered testing framework on MCP that spans desktop and mobile is ambitious and well-timed. The VS Code BDD AI Toolkit integration is especially cool for lowering the barrier to test authoring.
I wanted to flag a tool that might complement AutoGenesis for your Android testing users: Relay (akashagg30/relay), an open-source MCP server (Apache 2.0) for AI-powered Android testing.
How it could complement AutoGenesis:
- MCP-native, ready to plug in: Since both AutoGenesis and Relay are MCP-based, Relay could be exposed as an additional MCP server in AutoGenesis's configuration, extending its Android testing capabilities without architectural changes.
- Appium 2 + AI test generation: Relay provides Appium 2-based Android device control with AI-driven test script generation. For AutoGenesis users working on Android, this could add automated test authoring that feeds into AutoGenesis's multi-platform test management.
- Different layer: AutoGenesis focuses on the broader test framework orchestration across platforms (desktop + mobile). Relay lives at the device interaction layer specifically for Android. They're complementary — AutoGenesis could orchestrate Relay as its Android backend for certain test types.
- Structured test reports: Relay generates structured test reports (pass/fail/duration/errors) that could be consumed by AutoGenesis for unified reporting across desktop and mobile test runs.
- Open source, Apache 2.0: Same permissive licensing philosophy as AutoGenesis, so no friction for integration.
I know AutoGenesis already has BrowserStack integration for mobile testing, but Relay could be a useful option for users who want to run tests on local Android devices/emulators via MCP without needing a cloud provider.
No expectation of integration — just thought your Android-focused users might find it useful. Happy to discuss if there's potential synergy!
Great work on the cross-platform testing vision. 🎯
- Dominant language
- TypeScript
- Stars
- 135
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/AutoGenesis
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoft/AutoGenesis#16 · 6 comments ·
All issues in microsoft/AutoGenesis
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·