TestingBot Certification Program

TestingBot Maestro Certification

A resume-worthy credential for the Maestro Mobile Testing course. Prove you can do the work, not just that you read about it: pass a timed exam, then run the course suite on TestingBot. You get a certificate with a credential ID, a QR code and a public verification page.

Exam
20 questions, 30 min
Pass mark
80%
Practical
2 passing on 2 configs
Cost
Free, no expiry

The exam and the practical are tied to your TestingBot account, so sign in to start. A free account is enough.

How it works

  1. 1

    Step 1: The exam

    20 questions drawn from 30, 30 minutes, pass mark 80%. Not the knowledge-check questions. Explanations after grading; retake after 24 hours, up to 3 attempts in 7 days.

  2. 2

    Step 2: Run your Maestro flows on TestingBot

    2 passing Maestro flows in the build certificate-maestro on 2 different device configurations, in the last 30 days.

    How to run it

    Run your Maestro flows (the course's calculator flows are fine) on TestingBot on two different devices, for example one Android and one iOS target, or two Android versions. At least two flows must pass, and every run must carry the build name certificate-maestro.

    1. Install and authenticate the TestingBot CLI as shown in Run Maestro flows on TestingBot (npm install -g @testingbot/cli, then testingbot login, or TB_KEY and TB_SECRET on CI).

    2. Set the build name with --name. The TestingBot CLI groups Maestro runs by the --name you pass, and the API reports it as the run's build (build grouping).

    3. Cover two devices in one command with a device matrix:

      testingbot maestro sample.apk .maestro \
        --device-matrix "Pixel 9:15" --device-matrix "Pixel 8:14" \
        -e APP_ID=com.sampleapp \
        --name certificate-maestro
      

      or run the Android and iOS commands from that chapter separately, each with --name certificate-maestro (use sample.zip, --platform iOS and -e APP_ID=org.reactjs.native.example.SampleApp for the iOS Simulator).

    4. Pass/fail comes from the flows themselves; no extra reporting is needed. The CLI exits with 0 when every flow passed. Check the runs in the TestingBot dashboard.

  3. 3

    Step 3: Your certificate

    Unlocks when both steps are done. Choose the name to print, then share the public link or add it to LinkedIn.

Verify a TestingBot certificate

Hiring, or checking a claim on a CV? Enter the credential ID printed on the certificate to confirm it is genuine, see what TestingBot verified and whether it is still valid.