Run saved Rima tests against localhost.

The local runner lets a developer keep tests in the deployed Rima dashboard while executing them on a machine that can reach private URLs like http://localhost:3000.

It is useful when production is already live, but the next feature is still running locally or on a staging host.

Reaching a private URL is one of the questions worth asking of any web application testing tool, because a cloud-only runner cannot see localhost. See how the main tools compare on that point.

Install

Install the Rima CLI globally from npm:

npm install --global @rimatest/local-runner

Once installed, confirm the rima command is available:

rima --help

Connect

Run the login command, then sign in and approve the CLI in your browser:

rima login
The code expires in 10 minutes. The CLI exchanges it for a revocable device token.

Run Locally

  1. Start the app you are developing.
  2. Select the Rima project.
  3. Run all tests, or one particular test.
npm run dev rima use Example rima run --port 3000

Run one saved play/test by ID, name, or slug:

rima run login-flow --port 3000

URL Rewriting

If the recorded test starts with https://example.com, the runner uses the project primary domain or the recording itself to identify that origin and rewrites it to the target URL.

  • page.goto("https://example.com/login") becomes http://localhost:3000/login.
  • URL validations such as url_equals and url_contains are rewritten too.
  • Requests and redirects back to the deployed origin are continued against the local base URL when the runner can intercept them.

Use --target-url for staging or another private address. Pass --recorded-origin only when the project primary domain and automatic inference do not identify the correct original domain.

Logs and Files

CLI logs and local copies of run files are written on the developer machine:

~/.rima/logs/rima-cli-YYYY-MM-DD.log ~/.rima/runs/<run-id>/summary.json

The run summary, failure screenshots, trace zip, and optional videos are uploaded to Rima and appear in Recent Runs with local-cli as the source.

Test localhost without deploying first

Install the CLI, record a flow once, and run it against the build on your machine. Free plan, no card at signup.

Start free Local runner docs