TestingBot Certification Program

TestingBot Cross-Browser Testing Certification

A resume-worthy credential for the Cross-Browser Testing Tutorial 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 3 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 a cross-browser suite on TestingBot

    4 passing browser tests in the build certificate-cross-browser-testing on 3 different browser configurations, in the last 30 days.

    How to run it

    Run your own test suite (or the course suite) on the TestingBot grid in at least three different browser and platform combinations, covering at least two rendering engines, with every session in one build named certificate-cross-browser-testing and its pass/fail status reported.

    Choose either tool:

    Selenium (Python). Use the parametrized driver fixture from Selenium across browsers with a matrix of at least three entries, for example Chrome on WIN11, Firefox on WIN11 and Safari on TAHOE. Run it with TB_BUILD=certificate-cross-browser-testing, which the fixture passes as build in tb:options (the build option). The fixture reports each result with tb:test-result.

    Playwright (TypeScript). Use playwright.testingbot.config.ts, the testingbotEndpoint helper and the status fixture from Playwright projects and branded browsers with at least three projects (for example chrome-win11, firefox-win11 and safari-tahoe). Set build: 'certificate-cross-browser-testing' in tb:options (the build option). A session follows a Playwright worker, so run with --workers=2 or more to get enough passing sessions.

    Then open the certificate-cross-browser-testing build in the TestingBot dashboard and check that at least four sessions are marked passed across at least three configurations. Sessions without a pass or fail status do not count.

  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.