Here's how: Playwright finishes an E2E run → a small script reads the steps → one POST request to VibeTest's External API → the test case appears in the right project directory with all steps attached. No copy-pasting. No tab-switching.
The integration is surprisingly clean:
- One endpoint:
POST /api/external/cases - One header:
X-API-Key - Three required fields:
title,project_id,directory_path - Steps are just an array of
{ action, expected_result }
What I love about it: the directory gets created automatically if it doesn't exist. So your /Web/Auth or /Mobile/Login folder just appears — no setup needed.
The full CI flow
- Run Playwright tests
- Script parses
test.step()annotations - Calls VibeTest API → case created with
201 Created - Test management system stays up to date after every push
For teams where test documentation always falls behind the actual code — this is the fix. The source of truth lives in your test file. The TMS just reflects it.
VibeTest has a solid External API built exactly for this kind of CI/CD integration. API keys live in org settings, docs are clear, error messages are actionable.
If you're maintaining a test suite in Playwright (or any framework with structured steps), this pattern is worth an evening of setup.