Push Tests to Portal

Once your tests are generated, imported, or fixed locally using Maeris MCP, you can push them to the Maeris Portal. This syncs your test cases, steps, and run results to the cloud, enabling team collaboration, scheduled runs, and CI/CD integration.

Pushing All Tests

To push all local tests to the Maeris Portal:

maeris push tests

This uploads every test case and its steps to your Maeris application on the portal. Tests are matched by name — existing tests with the same name are updated, and new tests are created.

Pushing a Specific Folder

To push only the tests within a particular folder:

maeris push tests --folder Authentication maeris push tests --folder "Checkout Flow"

This is useful when you want to share a specific feature's tests without overwriting other tests that may be managed separately.

What Gets Synced

The push command syncs the following to the Maeris Portal:

Test Cases

All test case metadata including name, description, folder assignment, tags (smoke/regression), and the base URL used during generation.

Test Steps

Every action step within each test: navigation, clicks, form fills, waits, assertions. Steps are displayed in a visual timeline on the portal and can be reviewed or edited by teammates.

Run Results

If you ran tests before pushing, the latest pass/fail result for each test is also synced. This gives your team an immediate view of the current test health without needing to re-run everything.

Team Collaboration After Push

Once tests are on the portal, your whole team can:

Browse and search tests by name, folder, or tag
View detailed step breakdowns and selector information
Schedule tests to run on a recurring basis (hourly, daily, on deploy)
Trigger runs from CI/CD pipelines using the Maeris API or GitHub Actions integration
Review historical run results and trend charts
Comment on failing tests and assign fixes to team members

Sync Behavior

Merge, not overwrite

The push command performs a smart merge. Tests that exist on the portal but are not in your local session are left untouched. Only tests present in your current local context are upserted. This means teammates working on different features won't overwrite each other's tests.

Verifying the Push

After pushing, you can confirm how many tests are now on the portal:

maeris test list --remote

This lists all tests currently stored in the Maeris Portal for your application.

Next Steps

Looking to generate a new test suite from scratch? See the Generate Playwright Tests guide for the full generation workflow.