Running Tests

Running Tests Manually

From the Code tab you can Run All tests, use the per-test Run Test action, or open a test and tap Run Test on its detail screen. Manual runs give haptic feedback on success or failure. They do not post notifications. Each card shows its status (Passed, Failed, Running, Not Run) and when it last ran.

Apple Shortcuts

ContainEye exposes two Shortcuts actions that run tests in the background without opening the app:

• Test Servers, run all tests across your servers ("Test all servers", "Test servers in …", "… test servers").
• Run a single Test, run one specific test ("Test ‹test› in …", "… test ‹test›", "Execute ‹test› in …").

After a run you get a result dialog, "Finished N tests successfully." or "Finished N tests. X failed.", with a Retry (in background) button. Combine these actions with Shortcuts automations to trigger tests by time of day, location, or other triggers.

Home-Screen Widget

The systemSmall Test Widget (kind "TestsWidget") shows your highest-priority active test. Failed before running before success before not-run, with its title, relative run time, and a color tint. The button on the widget re-runs that test via the Test Servers intent without opening the app; tapping the widget body opens the test's details.

Background Checks

ContainEye attempts background checks when iOS allows it, driven by app refresh and silent push, roughly every few minutes. Background runs are opportunistic, not guaranteed, and cover up to the 10 tests that haven't run most recently. There is no per-test schedule or interval setting.

Result Insights

Open a test to see its Configuration (server, command, expected output, notes) and Last Output, the actual output from the last run, monospaced and copyable. Only the last run is kept; there is no history of earlier results. On failure, the test shows a red Failed status in the app, and a local notification appears if you have granted notification permission.