# Test Interface

In no-code or browser automation tools use [https://test.mailslurp.com](https://test.mailslurp.com) to control email accounts and emails using a no-code test interface.

<figure data-component="DocsVideoEmbed" class="docs-video-embed">
<iframe src="https://www.youtube-nocookie.com/embed/O7MigYoB3r4?modestbranding=1&rel=0&controls=1" title="MailSlurp documentation video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
<figcaption><a href="https://www.youtube.com/watch?v=O7MigYoB3r4">Open video on YouTube</a></figcaption>
</figure>

## When to use the test interface
- Browser automation suites where direct SDK usage is difficult.
- No-code test tools that need disposable inboxes and message assertions.
- Manual QA verification of signup, password reset, and OTP flows.

## Typical workflow
1. Open the interface in your test environment.
2. Authenticate with your MailSlurp API key.
3. Create inboxes or phone numbers for the scenario.
4. Use generated addresses/numbers in the app under test.
5. Return to the interface to inspect received content and extract values.

## Security and reliability notes
- Use scoped test API keys for non-production environments.
- Avoid reusing the same inbox across many parallel runs.
- Prefer API/SDK-based automation for fully deterministic CI pipelines.

## Related docs
- [Testing overview](/docs/testing/)
- [BrowserStack guide](/docs/browserstack/)
- [Wait for methods](/docs/wait-for/)