From target to recovery.
Start with one real customer journey. Run it once, understand the result, then schedule it. Only test systems you own or are explicitly authorized to test.
Nine steps
- 01
Add a website
Create a project with the address of a website you own or are authorized to test.
- 02
Name a journey
Create a monitor for one important path, such as signing in or placing an order.
- 03
Build the steps
Open a page, then select buttons and fields visually. No selector code is required.
- 04
Run once
Confirm authorization, choose Manual, and use Run now to check your journey.
- 05
Read the result
See the outcome, the exact step that stopped, and evidence when available.
- 06
Schedule checks
Choose an automatic interval after your first manual run succeeds.
- 07
Get alerted
A confirmed failure opens an incident. Configure who receives email in the monitor.
- 08
Repair the target
If a page element changes, use Update target to select the correct one again.
- 09
Watch recovery
A later successful check resolves the incident and records the recovery.
Available actions
Enter a page on your project website, such as /login. Checks stay on that website.
Choose a button or link visually. You can change the selected target later.
Choose a field visually, then enter its value. Mark passwords and tokens as secret; they will not be shown again.
Choose an element and enter the words that should appear there.
A complete login monitor
- 01 · Open /login
- 02 · Fill the Email field with a dedicated test-account email
- 03 · Fill the Password field and mark its value secret
- 04 · Click the Sign in button
- 05 · Check that the welcome message appears
Prefer a non-privileged test account with synthetic data. CAPTCHA, MFA, passkeys, aggressive anti-bot controls and federated login may prevent unattended checks. Internal/private network targets are intentionally blocked. SHEMANE does not execute customer JavaScript.
Confirm authorization on the project page, select Manual, verify one Run now result, then choose a schedule. Failure screenshots remain private and are suppressed for sensitive scenarios to avoid capturing credentials. See the Acceptable Use Policy and security overview.