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.

Exporting a test vs. exporting a run

This page is about exporting the test definition (its steps). A run’s own record — the compiled steps it executed, and its metadata — is available from the API only; see Sharing reports.

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 the test’s ⋯ menu in the Tests explorer (or right-click it) and pick Export .marriska.

Several tests download as one ZIP, one file per test:

• Everything currently listed — the Export N shown button under the filters in the Tests sidebar. It exports exactly what the sidebar is showing, so it respects the project you are in, any tag filter, and the status filter. That is how you export a whole project, or everything carrying a tag. The files are .marriska.
• A hand-picked set of tests — tick them on the Tests page and use the Export action in the bar that appears. The files are .marriska; one ticked test downloads as a single file instead of a ZIP.
• A whole test set — open the set’s ⋯ menu on the Runner page (or right-click it) and pick Export .marriska, Export YAML or Export Python.

The app offers YAML and Python through a test set only. For one test, the API has all three — GET /api/v1/tests/{test_id}/export/{marriska|yaml|python} — with the same signed-in-only rule as a run’s exports: an API key is refused.

One hundred tests per export

A ZIP is assembled in memory, so an export is capped at 100 tests. Past that, the request is refused with a message rather than quietly returning the first hundred — an export that looks complete but is not would be worse than one that fails. Narrow the filters, or export by set, and run it again.

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.

Only .marriska imports

Import is round-trip only: it reads .marriska files. There’s no importer for raw Playwright scripts or YAML today — exporting to Python or YAML is a one-way door out, not a path back in.

To move a test to another project, you do not need the round-trip: the explorer’s row menu (the ⋯, or a right-click) has Move to project… — see Organize tests with projects and folders. Export and import is for a copy: the original stays where it is.

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.

Related

• 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