Test and Verify
Use this page after installation and provider setup.
Check extension loading
In Chromium, open chrome://extensions and confirm:
- Swan is enabled.
- Developer Mode remains on.
- If you loaded a local dashboard build, the extension path points at
output/chrome-mv3-dev. - No manifest or runtime errors are visible on the extension card.
Send a test alert
- Open Swan settings.
- Confirm monitoring and the voice-call toggle are enabled.
- Confirm the recipient number is saved.
- Confirm ElevenLabs credentials are saved.
- Click Send test alert.
Expected result:
- The call arrives from the ElevenLabs-connected phone number.
- A new log entry appears in Swan.
Verify logs
Open Logs and inspect the latest event:
| Status | Meaning |
|---|---|
success | The provider accepted the request and returned an identifier when available. |
failed | The provider request failed. Check the error and provider console logs. |
skipped | Swan intentionally did not call, usually because calls are disabled or configuration is incomplete. |
pending | The event was created before the provider status finished updating. |
Test domain detection
- Add a safe test domain in Domain Tracking.
- Visit the domain in the same browser profile.
- Confirm Swan redirects to the intervention page.
- Confirm a log entry appears.
Validate source changes
If you changed the code or pulled a new version:
bash
npm run dashboardKeep WXT running while you work. Source changes hot reload into the local extension; reload Swan from chrome://extensions only if Chrome reports that it is needed.