Export and import tests

You can take your tests out of Marriska — as runnable Playwright code, as YAML, or as a .marriska bundle you can import again later.

Export formats

Format	What you get	Good for
`.marriska`	A JSON bundle of the test (steps, metadata)	Re-importing into Marriska
YAML	The step list in YAML	Reading, diffing, version control
Python	A runnable Playwright Python script	Handing to an engineer, running outside Marriska

Export a test

Open a test (or select tests on the Tests page) and use the Export dropdown. Pick .marriska, YAML, or Python.

You can also export in bulk — Marriska zips up multiple tests for:

A whole project
A whole test set
Everything carrying a tag
A hand-picked set of tests

Each ZIP holds one file per test in the format you chose.

Import a test

Import accepts the .marriska format — the same bundle the exporter produces. In the test editor, choose Import and pick a .marriska file; its steps load into the editor, ready to review and save.

This round-trip is also the closest thing to moving a test between projects: export the .marriska file from one project, then import it while the destination project is active. (There’s no direct move-between-projects action — see Organize tests with projects and folders.)

Plan and access

Export and import aren’t plan-gated — they work on every tier. The only gate is the usual one: you can export tests in your own organization.

Share a test run report — exporting a finished run
YAML schema reference — the shape of an exported test
Step actions reference — what each exported step does