- Courses
- Certifications
- Playwright API Testing
TestingBot Certification Program
TestingBot Playwright API Testing Certification
A resume-worthy credential for the Playwright API 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
- 3 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 API-backed UI suite on TestingBot
3 passing browser tests in the build
certificate-playwright-api-testingon 2 different browser configurations, in the last 30 days.How to run it
Run the course suite (or your own Playwright Test suite whose UI tests create their data through the API) on the TestingBot grid in at least two browser and platform combinations, with every session in one build named
certificate-playwright-api-testingand its pass/fail status reported.- Build the fixtures from Test data setup and teardown through the API:
your UI tests should create what they need through an
APIRequestContextand clean it up afteruse(). - Create
testingbot.tsandplaywright.testingbot.config.tsfrom Running API and UI tests in CI and on a cloud grid, with at least two remote projects, for examplechrome-windows(enginechromium) andfirefox-linux(enginefirefox). - Set the build name:
export TB_BUILD=certificate-playwright-api-testing(the helper passes it asbuildintb:options; see the Playwright options reference). - Make sure the UI tests use the
browserTestoruiTestfixtures, so each session sendssetSessionNameandsetSessionStatusthroughpage.evaluate. Without them, sessions finish with no pass or fail and do not count. API-only tests open no session and do not count either. - Export
TB_KEYandTB_SECRETand runnpx playwright test -c playwright.testingbot.config.ts --workers=2. A TestingBot session follows a Playwright worker, not a test: with one worker each remote project is a single session, so use at least two workers (or run the suite twice) to get three or more passing sessions. - Open the
certificate-playwright-api-testingbuild in the TestingBot dashboard and check that at least three sessions are marked passed across at least two configurations.
- Build the fixtures from Test data setup and teardown through the API:
your UI tests should create what they need through an
-
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.