TestingBot Certification Program

TestingBot Mobile App Testing Certification

A resume-worthy credential for the Mobile App Testing: From First Test to CI 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 an Appium test on two device configurations

    2 passing Appium app tests in the build certificate-mobile-app-testing on 2 different device configurations, in the last 30 days.

    How to run it

    Run an Appium test against a mobile app on TestingBot on at least two different device configurations, with at least two passed sessions in the build certificate-mobile-app-testing. A configuration is the device, platform and OS version: a real Pixel 8 and an emulated Pixel 8 on the same Android version count as one, so mix platforms or versions (for example an Android emulator and an iOS simulator). Real devices, emulators and simulators all count.

    1. Export TB_KEY and TB_SECRET and install WebdriverIO, as in Your first Appium test on a real device.

    2. Use the matrix script from Device matrix, parallel runs and CI, which sets the build from the BUILD variable in tb:options:

      BUILD=certificate-mobile-app-testing node matrix.mjs
      

      Or set it yourself in tb:options of every capability:

      'tb:options': { realDevice: false, build: 'certificate-mobile-app-testing' }
      
    3. Use the calculator sample apps (https://testingbot.com/appium/sample.apk, sample.zip for the iOS Simulator, sample.ipa for real iPhones) or your own app uploaded to TestingBot Storage.

    4. Report each session's result with tb:test-result (as the course's scripts do) or a test runner service that reports it. Sessions without a passed state do not count.

    5. Check in the dashboard that the sessions are listed under the build and marked passed.

    See Group Tests for the build option.

  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.