Playwright
Test Data for Playwright That Doesn't Rot
Playwright suites get fast and stable when test data lives outside the repo. TestAssets is a hosted catalog of credentials, fixtures, IDs, and payloads — your Playwright suite reads them via REST API, your QA team pastes them from a browser extension. One source of truth.
Why teams choose this
No more hardcoded credentials
Staging logins, admin tokens, and test cards live in a hosted catalog, not in your fixture files. Rotate once, every test sees the new value.
Drop-in custom fixture
A 10-line custom Playwright fixture pulls your test data at runtime. No new dependency, no SDK, no DSL — just `fetch`.
Same data your QA team uses
Manual testers paste the same credentials from a browser extension or desktop app. Automation and humans never drift apart.
globalSetup and storageState ready
Pre-authenticate once in globalSetup using credentials pulled from TestAssets, save the session, run hundreds of tests instantly.
How it works
- 1
Create a list of test assets
Add staging credentials, test card numbers, sample payloads, and any other reusable test data to a TestAssets list.
- 2
Generate a free API key
From the Settings page, generate a read-only API key for your CI pipeline. Add it to GitHub Actions secrets.
- 3
Read from a Playwright fixture
Write a one-time custom fixture that fetches your list via REST API and exposes it to every test. Done.
Built for teams that...
- Centralizing staging credentials shared across QA, CI, and manual testers
- Rotating test data without touching fixture files in the repo
- Pre-authenticating Playwright via globalSetup using shared logins
- Sharing API payloads between Playwright API tests and Postman/Insomnia
- Keeping test data accessible to AI agents via the MCP server alongside the same Playwright suite
Frequently asked questions
Ready to try TestAssets?
Free to get started. No credit card required.
Create your account