Customer results · ClosedTest

Completed Android testing runs. Real records.

These results are generated from completed projects in the ClosedTest database. Customer identities and private information are intentionally not published here.

View testing results →Start closed testing
Verified public metrics

What the database actually contains.

We calculate these totals from completed project records instead of hard-coding marketing claims.

29
Completed runs
406
Tester assignments
2850
Recorded check-ins
6100
Reported issues
Completed runs

Real testing work, documented carefully.

We publish anonymized project results here. Customer names, emails, tester names, and private project details are not exposed.

RUN #001Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-09 → completed
Testers assigned: 12
Check-ins: 151
Devices represented: 12
Android versions: 7
Reported issues: 300

Customer identity and private project details are not published without explicit permission.

RUN #002Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-09 → completed
Testers assigned: 12
Check-ins: 152
Devices represented: 12
Android versions: 7
Reported issues: 240

Customer identity and private project details are not published without explicit permission.

RUN #003Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-09 → completed
Testers assigned: 12
Check-ins: 131
Devices represented: 12
Android versions: 8
Reported issues: 552

Customer identity and private project details are not published without explicit permission.

RUN #004Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-08 → completed
Testers assigned: 18
Check-ins: 182
Devices represented: 17
Android versions: 9
Reported issues: 360

Customer identity and private project details are not published without explicit permission.

RUN #005Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-08 → completed
Testers assigned: 13
Check-ins: 151
Devices represented: 13
Android versions: 8
Reported issues: 169

Customer identity and private project details are not published without explicit permission.

RUN #006Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-08 → completed
Testers assigned: 19
Check-ins: 177
Devices represented: 18
Android versions: 11
Reported issues: 247

Customer identity and private project details are not published without explicit permission.

RUN #007Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-06 → completed
Testers assigned: 13
Check-ins: 142
Devices represented: 13
Android versions: 9
Reported issues: 182

Customer identity and private project details are not published without explicit permission.

RUN #008Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-05 → completed
Testers assigned: 16
Check-ins: 124
Devices represented: 12
Android versions: 7
Reported issues: 224

Customer identity and private project details are not published without explicit permission.

RUN #009Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-04 → completed
Testers assigned: 16
Check-ins: 136
Devices represented: 15
Android versions: 8
Reported issues: 240

Customer identity and private project details are not published without explicit permission.

RUN #010Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-04 → completed
Testers assigned: 12
Check-ins: 113
Devices represented: 12
Android versions: 8
Reported issues: 156

Customer identity and private project details are not published without explicit permission.

RUN #011Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-04 → completed
Testers assigned: 12
Check-ins: 114
Devices represented: 12
Android versions: 8
Reported issues: 264

Customer identity and private project details are not published without explicit permission.

RUN #012Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-04 → completed
Testers assigned: 16
Check-ins: 132
Devices represented: 15
Android versions: 8
Reported issues: 368

Customer identity and private project details are not published without explicit permission.

RUN #013Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-04 → completed
Testers assigned: 16
Check-ins: 137
Devices represented: 14
Android versions: 9
Reported issues: 464

Customer identity and private project details are not published without explicit permission.

RUN #014Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-04 → completed
Testers assigned: 12
Check-ins: 113
Devices represented: 12
Android versions: 7
Reported issues: 216

Customer identity and private project details are not published without explicit permission.

RUN #015Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-04 → completed
Testers assigned: 12
Check-ins: 111
Devices represented: 12
Android versions: 8
Reported issues: 336

Customer identity and private project details are not published without explicit permission.

RUN #016Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-04 → completed
Testers assigned: 12
Check-ins: 111
Devices represented: 12
Android versions: 8
Reported issues: 96

Customer identity and private project details are not published without explicit permission.

RUN #017Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-02 → completed
Testers assigned: 16
Check-ins: 74
Devices represented: 9
Android versions: 5
Reported issues: 48

Customer identity and private project details are not published without explicit permission.

RUN #018Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-02 → completed
Testers assigned: 13
Check-ins: 87
Devices represented: 12
Android versions: 7
Reported issues: 247

Customer identity and private project details are not published without explicit permission.

RUN #019Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-01 → completed
Testers assigned: 16
Check-ins: 88
Devices represented: 14
Android versions: 8
Reported issues: 224

Customer identity and private project details are not published without explicit permission.

RUN #020Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-01 → completed
Testers assigned: 12
Check-ins: 69
Devices represented: 10
Android versions: 7
Reported issues: 84

Customer identity and private project details are not published without explicit permission.

RUN #021Android app · status: Completed

ClosedTest testing run

Testing period: 2026-08-01 → completed
Testers assigned: 16
Check-ins: 72
Devices represented: 13
Android versions: 8
Reported issues: 176

Customer identity and private project details are not published without explicit permission.

RUN #022Android app · status: Completed

ClosedTest testing run

Testing period: 2026-07-30 → completed
Testers assigned: 12
Check-ins: 58
Devices represented: 12
Android versions: 8
Reported issues: 108

Customer identity and private project details are not published without explicit permission.

RUN #023Android app · status: Completed

ClosedTest testing run

Testing period: 2026-07-30 → completed
Testers assigned: 16
Check-ins: 55
Devices represented: 12
Android versions: 7
Reported issues: 128

Customer identity and private project details are not published without explicit permission.

RUN #024Android app · status: Completed

ClosedTest testing run

Testing period: 2026-07-30 → completed
Testers assigned: 12
Check-ins: 56
Devices represented: 12
Android versions: 7
Reported issues: 96

Customer identity and private project details are not published without explicit permission.

RUN #025Android app · status: Completed

ClosedTest testing run

Testing period: 2026-07-28 → completed
Testers assigned: 13
Check-ins: 37
Devices represented: 12
Android versions: 7
Reported issues: 130

Customer identity and private project details are not published without explicit permission.

RUN #026Android app · status: Completed

ClosedTest testing run

Testing period: 2026-07-28 → completed
Testers assigned: 13
Check-ins: 40
Devices represented: 12
Android versions: 7
Reported issues: 169

Customer identity and private project details are not published without explicit permission.

RUN #027Android app · status: Completed

ClosedTest testing run

Testing period: 2026-07-23 → completed
Testers assigned: 16
Check-ins: 12
Devices represented: 11
Android versions: 7
Reported issues: 80

Customer identity and private project details are not published without explicit permission.

RUN #028Android app · status: Completed

ClosedTest testing run

Testing period: 2026-07-23 → completed
Testers assigned: 12
Check-ins: 13
Devices represented: 10
Android versions: 7
Reported issues: 84

Customer identity and private project details are not published without explicit permission.

RUN #029Android app · status: Completed

ClosedTest testing run

Testing period: 2026-07-23 → completed
Testers assigned: 16
Check-ins: 12
Devices represented: 11
Android versions: 7
Reported issues: 112

Customer identity and private project details are not published without explicit permission.

Why this matters

Transparent results beat invented claims.

The public record grows directly from completed testing runs. As the network grows, the evidence grows with it.

  • Real completed-project counts
  • Real tester and check-in records
  • Real device and Android-version coverage
  • Private customer identities protected
Start a test

Want your app tested next?

We coordinate real Android testers, daily participation, and structured testing evidence for your closed test.

Start closed testing →