Cara Setup — Testclo | QA Testing Android Pra-Rilis

1

Place Your Order

Choose your preferred platform

Start by placing an order on one of our supported platforms. Both offer the same service, same 12 testers, and same 14-day sprint.

Fastwork Fiverr

💡

After placing your order, you'll receive an invoice number (e.g., TST-2025-001) via the platform's messaging system. Keep this — you'll need it to track progress.

2

Prepare Your APK / AAB File

Get your app build ready for testing

We need your Android app build file to start testing. You can provide either:

APK file — Standard Android Package (universal or split APKs)
AAB file (App Bundle) — Google's recommended format for Play Store

Make sure your build is a release build (not debug) that represents what you plan to submit to Google Play Store.

⚠️

If your app requires backend services, API keys, or login credentials for testing, please provide test accounts along with your build. This ensures our testers can access all app features during the sprint.

3

Share Your Build With Us

Two ways to submit your app

Please invite our tester group email to your Closed Testing track in Google Play Console, then send us the app link once approved.

Tester Group Email — Invite This

safe-testing@googlegroups.com

Need a visual walkthrough? Follow the step-by-step guide below for adding testers in Play Console:

🔗

After approval: Once the group email has been accepted as a tester, please send us the opt-in / app link via the platform chat (Fastwork or Fiverr). This is required before testing can begin.

ℹ️

You do NOT need to give us Play Console ownership. We only need tester-level access (read-only, via testing tracks) to install and test the app.

4

Testing Begins — 14-Day Sprint

12 testers, 40+ devices, full coverage

Once we receive your build, our testing squad kicks off the 14-day sprint. Here's what happens:

Day 1–2: Test plan setup, device allocation, environment preparation
Day 3–10: Core testing — functional tests, UI/UX checks, device compatibility, Android version testing (8.0–14), crash monitoring
Day 11–12: Regression testing, edge cases, Play Store policy review
Day 13–14: Report compilation, final review, delivery

Each tester covers specific modules and device profiles to ensure comprehensive coverage across 40+ Android device configurations.

5

Track Your Progress

Real-time dashboard with your invoice number

You can monitor your testing progress at any time using our live dashboard:

Go to testclo.com and click "Check Progress"
Enter your invoice number (e.g., TST-2025-001)
View real-time metrics: sprint day, scenarios executed, pass rate, issues found, device coverage
See tester assignments, activity logs, and release track status

💡

The dashboard updates in real-time as our testers log their findings. You can check back anytime during the 14-day sprint for the latest status.

6

Receive Your Full Report

Comprehensive QA report delivered

At the end of the 14-day sprint, you'll receive a Production Readiness Assessment report that includes:

Test Summary — Total scenarios, pass/fail counts, coverage metrics
Bug Reports — Detailed issue descriptions with severity levels, screenshots, and reproduction steps
Device Compatibility Matrix — Results across all tested devices and Android versions
Play Store Policy Review — Data safety form, permissions, content rating, and metadata checks
Recommendations — Prioritized action items for your development team before Play Store submission

📄

The report is delivered as a PDF document via the platform messaging system (Fastwork/Fiverr). If your team pushes a new build during the sprint, one structured retest round is included.

How To Setup Your Testing

Ready to get started?