Every feature, explained in plain language.
Search for any feature or term Rima uses. Get its definition, what it is for, a practical example, common use cases, where to find it, and product screenshots - plus complete step-by-step guides.
Reference · Build tests 10 definitions
Run Before
Run Before is a dependency setting that tells Rima to execute one or more setup tests before the test you selected.
Read definition and examplesEnvironment URL
An environment URL maps the domain used while recording to another domain used during a run.
Read definition and examplesTest group
A test group is a named, ordered, reusable selection of tests inside a project.
Read definition and examplesPreview Replay
Preview Replay plays a saved test inside your current browser tab so you can watch the actions before starting a full run.
Read definition and examplesSimple validation
A simple validation is a quick text or URL check that does not require you to build a selector-based rule.
Read definition and examplesAdvanced validation
An advanced validation targets an element with a selector and can require several properties to match at the same time.
Read definition and examplesExecution mode
Execution mode controls whether tests in a multi-test run share one browser session or each start in a fresh browser.
Read definition and examplesEnabled and disabled tests
An enabled test can be selected and executed; a disabled test stays saved but is skipped by normal runs and schedules.
Read definition and examplesWait step
A wait step pauses test execution before the next action.
Read definition and examplesAssign a step result to a variable
Assign to variable stores a value produced or used by one step under a project-variable name for later steps and tests.
Read definition and examplesRun tests and read the results
Run one test, a hand-picked selection, or a saved group. Every run produces a summary, screenshots, a full trace with video and network data, downloadable files, and a link you can share with anyone.
Read guideSchedules: let Rima run tests for you
Put a project on a schedule and Rima re-runs your chosen tests automatically - hourly, daily, weekly or monthly - and emails you the results. Start and stop the schedule any time.
Read guideReference · Run and inspect 5 definitions
Run summary
The run summary is the high-level result page for a run, showing status, duration, selected tests, validations, failures, and links to deeper evidence.
Read definition and examplesRun History and Run Trends
Run History lists past executions; Run Trends summarizes how results change over time.
Read definition and examplesSchedule
A schedule automatically starts selected tests or a test group at a recurring time.
Read definition and examplesDelay between tests
Delay between tests is an optional pause inserted after one selected test finishes and before the next begins.
Read definition and examplesTrace timeline
The trace timeline places notable run events in time, including navigation, console warnings or errors, and failed or slow network requests.
Read definition and examplesReference · Local and private testing 3 definitions
Local runner API key
A local runner API key is a long-lived credential the CLI can use for non-interactive authentication.
Read definition and examplesLocal runner and CLI
The local runner is Rima’s command-line tool for executing saved tests on your own computer while syncing results back to the web app.
Read definition and examplesCLI commands
The Rima CLI is the rima terminal command that lists your workspaces, projects, and tests, and runs saved tests on your own computer.
Read definition and examplesReference · Core concepts 2 definitions
Test
A test is a saved browser flow: an ordered set of actions plus optional validations that Rima can replay.
Read definition and examplesRecorded step
A recorded step is one saved interaction inside a test, such as navigating, clicking, typing, choosing an option, scrolling, waiting, or validating a result.
Read definition and examples