- Courses
- Certifications
- Locator Strategies
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
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
Step 2: Run your locator suite on TestingBot
4 passing browser tests in the build
certificate-locator-strategieson 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.- Set up the suite from the chapters. For Selenium, the
conftest.pyin Why Tests Break on Locators connects to TestingBot whenTB_KEYis set and reads the build name fromTB_BUILD. For Playwright, use thetestingbot.tshelper and config from A Locator Review Checklist. - Set the build name: both setups pass
TB_BUILDas thebuildoption intb:options(described under "Group Tests" in the Selenium options reference). ExportTB_KEY,TB_SECRETandTB_BUILD=certificate-locator-strategies. - Run on two configurations. Selenium:
pytest -s tests/and thenBROWSER=firefox pytest -s tests/(one session per test). Playwright:npx playwright testruns thechrome-win11andfirefox-win11projects, with one session per project and worker, so run it twice to reach four sessions. - Make sure each session reports its result: the Selenium fixture sends
tb:test-result, and the Playwright fixture callssetSessionStatus. Sessions without a result do not count. - Open the
certificate-locator-strategiesbuild in the TestingBot dashboard and check that at least four sessions are marked passed across at least two browser and platform combinations.
- Set up the suite from the chapters. For Selenium, the
-
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.