TestingBot Certification Program

TestingBot Locator Strategies Certification

A resume-worthy credential for the Selenium Locators and Locator Strategies 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
4 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 locator suite on TestingBot

    4 passing browser tests in the build certificate-locator-strategies on 2 different browser configurations, in the last 30 days.

    How to run it

    Run the course's Selenium or Playwright suite (or your own suite that uses the locator strategies from the course) on the TestingBot grid in at least two browser configurations, with every session in one build named certificate-locator-strategies.

    1. Set up the suite from the chapters. For Selenium, the conftest.py in Why Tests Break on Locators connects to TestingBot when TB_KEY is set and reads the build name from TB_BUILD. For Playwright, use the testingbot.ts helper and config from A Locator Review Checklist.
    2. Set the build name: both setups pass TB_BUILD as the build option in tb:options (described under "Group Tests" in the Selenium options reference). Export TB_KEY, TB_SECRET and TB_BUILD=certificate-locator-strategies.
    3. Run on two configurations. Selenium: pytest -s tests/ and then BROWSER=firefox pytest -s tests/ (one session per test). Playwright: npx playwright test runs the chrome-win11 and firefox-win11 projects, with one session per project and worker, so run it twice to reach four sessions.
    4. Make sure each session reports its result: the Selenium fixture sends tb:test-result, and the Playwright fixture calls setSessionStatus. Sessions without a result do not count.
    5. Open the certificate-locator-strategies build in the TestingBot dashboard and check that at least four sessions are marked passed across at least two browser and platform combinations.
  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.