Back to Blog

Your first Monito check, from signup to a verdict

Sign up, describe one scenario in plain English, and read a Passed, Failed, or Error verdict with the evidence from that run.

first-verdictmonitono-code

A first check is one scenario, one run, and a verdict you can read. This is that path. There is no sample report below: the report URL, duration, and screenshots come from your run, and inventing them would be a lie.

In the app

Sign up. Onboarding asks for the URL of the app. The wizard says "Your first run is free." That first onboarding run is not charged. Later runs are.

The scenario it launches is fixed:

  • No login saved: "Open the home page. It loads without errors, and its main call to action works and leads somewhere sensible." The saved name is "Home page works."
  • A login saved during onboarding: "Log in, then confirm the first page after login loads and its main navigation works."

When the run finishes, open the report. The badge is Passed, Failed, or Error.

  • Passed means the scenario's checks were observed.
  • Failed means the app did not do what the scenario said.
  • Error means the check could not verify the scenario. The homepage calls that ending "cannot verify." An error is not a pass. What that ending means.

The report keeps screenshots, console messages, and network requests (method, URL, status). Runs without a login record a video. Runs that sign in keep masked screenshots instead. It does not record your visitors.

From the CLI

The same check, against a URL you choose:

monito check https://your-app.example/signup "The form rejects a malformed email and explains why" --json

Install and monito auth login are on the docs home. The command waits for the verdict. JSON includes checkId, projectId, runId, done, status, cause, causeLabel, durationMs, creditsCharged, reportUrl, and firstFailure. Human text goes to stderr. Exit 0 means passed. Exit 1 means failed or error. status is passed, failed, or error. reportUrl is the report. The field list is the check command; the values are whatever that run produced.

monito check save <checkId> --name "Signup validation" keeps it as a test. Saving does not create a schedule.

What to write

"Test signup" is not a check. "The form rejects a malformed email and explains why" is. You are stating an outcome the run can observe. When the product changes, you update the sentence. Monito does not rewrite it to stay green.

What this is not

Chromium only. Not Firefox, Safari, or a native app. Not a ticket filed in Jira. A failed or error run can be copied as issue markdown (monito run view <id> --issue-markdown, or "Copy as issue" on the report). You paste it. Prices are on /pricing. The published reliability numbers, and what they do not claim, are on /reliability.