Test mode

Projects created with a test key (pw_test_…) go through every step a live project does, with real statuses, real signed webhooks to your test endpoints, and a real delivery, but nothing reaches our studio and nothing is charged.

What happens

1. Validation is real: uploads and imports are checked and measured, and creditsSeconds shows what the project would cost live. No credits move.
2. queued for about 5 seconds, then processing for 30–60 seconds (fixed per project), with progress moving through the same steps as a live project.
3. completed. The delivery is your own files, laid out and named exactly like a live delivery (each output file, a zip with a folder, manifest.json), plus a placeholder transcript.

Forcing an outcome

Create the project with testOutcome (test keys only; a live key gets 400 test_outcome_live):

testOutcome
completed	The default.
failed	Fails 60 % of the way through processing, with failure.code: "processing_failed".
slow	Takes about 10 minutes, to test long waits and estimatedCompletionAt.

{ "name": "Failure drill", "testOutcome": "failed", "files": [{ "fileName": "ep.wav" }] }

Limits

Test mode protects the studio’s capacity:

• files up to 500 MB;
• 50 test projects created per account in any 24 hours (429 test_limit_reached);
• 5 GB of files submitted per account in any 24 hours (a rejected project with test_limit_reached).

Test projects, events and webhook endpoints are separate from live ones: a test key never sees live data, and a live key never sees test data.