Automated Checks

Automated Tests

Overview Features SSH Terminal Servers Tests FAQ Support

What a Test Does

A test runs a command over SSH on one of your servers, or checks a URL if you pick "Local (URLs only)", and compares the output against an expected output. The expected output is treated as a regular expression when it compiles, otherwise as an exact string match. If the output matches, the test Passes; otherwise it Fails.

Creating Tests

  • With the AI: use Create Test in the Code tab's + menu (or Create Your First Test), describe what to check in plain language, and the Agentic assistant drafts, verifies, and creates the test in one chat session.
  • From suggestions: add one of 13 built-in templates (website status, disk space, CPU usage, Nginx, SSL expiry, MySQL, load average, pending updates, backups, failed logins, network latency, and more) with a single tap.
  • By editing: duplicate and adapt an existing test, change the name, command, expected output, notes, or target server.

Running Tests

  • Manually: Run All, the per-test Run Test, or Run Test on the detail screen. Manual runs give haptic feedback, no notifications.
  • Shortcuts: the Test Servers and Run a single Test actions run tests in the background without opening the app.
  • Home-Screen Widget: the systemSmall Test Widget shows your most important test and re-runs it with one tap.
  • In the background: when iOS allows, ContainEye attempts background checks (roughly every few minutes via app refresh and silent push). Background runs are opportunistic, not guaranteed.

Results

Each test shows a status, Passed (green checkmark), Failed (red xmark), Running, or Not Run, plus the last run time and the Last Output (copyable). The detail screen also shows the configuration and a Delete Test action. The Code tab gives an overall Test Status with Passing / Failing / Running counts.

Notes

  • Tests have no per-test schedule or interval setting. Background checks happen when iOS permits, and Shortcuts automations let you trigger runs by time, location, or other triggers.
  • Only the last run is kept. There is no history of previous results or outputs.
  • Tests are stored on your device only; they are never uploaded to a server-side scheduler.
  • Disabled tests (Do not execute) never run and stay in the Suggested Tests pool.

Guides