DEV Community: Tester Exchange

Get Google Play's 12 testers from Cursor, Claude Code or VS Code (MCP)

Tester Exchange — Sun, 15 Nov 2026 12:14:47 +0000

You built the Android app with Cursor or Claude Code in a weekend. Then Google Play stops you: a new personal developer account needs a closed test with 12 testers opted in for 14 days before you can apply for production.

You can set that up without leaving your editor. Tester Exchange has a remote MCP server, so your coding agent can list the app, open the test and track progress for you.

1. Get an API key

Sign in at testerexchange.com and create a key at testerexchange.com/api. That page also has one-click Cursor and VS Code buttons with your key filled in. Without a key, only the public tools (about, pricing, platform stats) work.

2. Connect your agent

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "tester-exchange": {
      "url": "https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp",
      "headers": { "Authorization": "Bearer tx_YOUR_TOKEN" }
    }
  }
}

Claude Code:

claude mcp add --transport http tester-exchange \
  https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp \
  --header "Authorization: Bearer tx_YOUR_TOKEN"

VS Code (.vscode/mcp.json):

{
  "servers": {
    "tester-exchange": {
      "type": "http",
      "url": "https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp",
      "headers": { "Authorization": "Bearer tx_YOUR_TOKEN" }
    }
  }
}

Windsurf, Gemini CLI and other clients: snippets are on the agents page. Clients that only accept a URL can pass ?token=tx_YOUR_TOKEN.

3. Ask for testers

Then just tell your agent something like:

Get 12 testers for com.example.myapp

The agent calls get_testers, which adds the app, opens its test, applies your credits and returns what's left to do (for example, adding the testers' Google group to your closed-testing track in Play Console).

Useful follow-ups:

campaign_report: testers, daily activity, feedback, and data for the production-access questions
start_friends_test: free; friends join from your share link, and fill_from_exchange fills only the seats they leave open
my_apps / my_account: status and credits

Free or paid

The default is a free swap: you install other developers' apps from your phone, and the same number install yours. If you'd rather not test, the agent can return checkout links for credits (buy_credits_links); a human always completes the payment.

After 14 days

Once 12+ testers have stayed opted in for 14 days, apply for production access in Play Console. This guide covers when you can apply.

Questions or a client that doesn't work? Ask in the comments.

Moving Confluence Q&A to Cloud: export, migration and the Connect deadline

Tester Exchange — Sun, 15 Nov 2026 11:47:46 +0000

If your team uses a Q&A app inside Confluence, two dates are worth knowing about before you plan anything else:

Data Center: Atlassian stopped selling Data Center to new customers on March 30, 2026, and DC goes read-only on March 28, 2029. Most teams will move to Cloud before then.
Connect apps: Atlassian's older app framework (Connect) reaches end of support on January 31, 2027. Admins already see "This app might stop working soon" banners on apps that haven't moved to Forge.

Q&A content is easy to forget in a migration plan because it isn't pages. Here's what we learned while building a Q&A app for Confluence Cloud.

1. Questions for Confluence on Data Center: export before you switch off

Atlassian's own FAQ is clear that Questions for Confluence Cloud has no export. Data Center is different: it has a REST API and documented database queries.

REST: GET /rest/questions/1.0/question?limit=700, then GET /rest/questions/1.0/answer/{answerId} per answer
Database: the queries in Atlassian's KB article "How to export Confluence Questions data"

Turn that into a CSV with one row per question and one row per answer (linked by the question's id), and keep it, whatever tool you pick next. Once the DC instance is gone, so is the only export path.

2. Q&A apps still on Connect: check now

Open Manage apps in Confluence admin. If your Q&A app shows the "might stop working" banner, ask the vendor for their Forge plan and an export. Apps keep running after Jan 31, 2027, but only with critical security fixes, so "it still works" is not a plan.

We built a free checker that looks up any Marketplace app and tells you whether it is on Forge, moving, or at risk: https://surfaced-srzj.onrender.com/guides/connect-end-of-support?utm_source=devto&utm_campaign=askbase_launch

3. What to look for in a Cloud Q&A tool

From reading a few hundred reviews of Confluence Q&A apps, the complaints repeat:

Search only matches titles, so answers are hard to find
No import or export, so content is locked in
No way to stop duplicates, so the same question is asked five times
Everyone can answer, even for HR or legal questions where only experts should
No way to ask from the page people are actually reading

Whatever you pick, test those five.

Disclosure

I'm on the team that makes Askbase, a Forge-native Q&A app for Confluence Cloud. Version 2.5 (out this week) does CSV/JSON import and export, searches answers, suggests similar questions while you type, lets moderators merge duplicates, can limit who answers, and adds an "Ask a question" box to any page. It's free for up to 10 users.

Import guide (including the Data Center path above): https://surfaced-srzj.onrender.com/apps/askbase/import?utm_source=devto&utm_campaign=askbase_launch
Marketplace: https://marketplace.atlassian.com/apps/3507606829/askbase-q-a-for-confluence?utm_source=devto&utm_campaign=askbase_launch

Questions or migration stories welcome in the comments.

How to get 12 testers for Google Play closed testing (free)

Tester Exchange — Sun, 15 Nov 2026 03:36:08 +0000

If you created a personal Google Play developer account recently, you have probably hit this wall: before you can publish to production, your app must run a closed test with at least 12 testers who stay opted in for 14 days in a row. Only then does the "Apply for production" button unlock.

For a solo developer this is the hardest part of shipping an Android app. Here's how the rule works and how to get through it without paying anyone.

What Google actually counts

12 testers opted in to your closed testing track (not just invited).
14 continuous days with at least 12 of them still opted in. If people leave partway through, your count can drop below 12, so drop-outs are the real risk.
Then you answer a short questionnaire about your test and apply for production access.

Always check the current wording in the Play Console help, because Google updates it.

Why the usual tricks fail

Friends and family: most don't have Android phones, forget to opt in, or uninstall after two days.
Reddit / Discord swap threads: people promise to test, then disappear. Nobody tracks who actually stayed.
Random paid gigs: you pay, testers vanish on day 3, and you start over.

The common problem: nobody is accountable for staying opted in for 14 days.

The free method: swap tests with other developers

Every developer stuck on this rule needs the same thing you do. So test each other's apps:

You add your app's closed-testing link.
You opt in to and install other developers' apps from your phone.
The same number of developers opt in to yours.
Anyone who drops out gets replaced, so your count stays at 12+.

We built Tester Exchange to run exactly this swap:

Joining a test is one tap from your phone's browser.
Installs and opt-ins are tracked, and drop-outs are replaced automatically.
It's free on the test-for-test basis. If you'd rather not test other apps, there's a paid option.
It works in 55 languages.

Doing it from your AI coding agent

If you build with Cursor, Claude Code, Windsurf or another MCP client, you can set this up without leaving the editor. Tester Exchange has a remote MCP server: one get_testers call with your package name adds the app, opens the test and tells you what steps are left. Config snippets for each client are on the agents page.

After 14 days

Once you have had 12+ testers for 14 days, answer the production-access questions honestly: what you tested, what feedback you got, what you changed. This guide covers when you can apply.

Good luck shipping. If you have questions about closed testing, ask in the comments.