Get started
Testlie documentation
Testlie is a testing toolkit for the parts of your app that talk to the outside world:
- Email sandbox. Point the SMTP settings of your development, staging and CI environments at Testlie. Every message is captured and shown in a web UI, and nothing is ever delivered to the real recipients. Your team previews the HTML, reads headers and attachments, checks spam scores and email-client support, and asserts on messages from automated tests.
- SMS sandbox. Capture text messages through a Twilio-compatible API and simulate delivery or failure without sending a real SMS. Get started with SMS.
- HTTP request bins. Inspect outgoing HTTP calls, configure responses and test webhooks. Create a request bin.
- Mock identity providers. Fake OIDC and SAML 2.0 identity providers for testing your app's single sign-on. Define test users with groups and custom claims, pick one on the login screen (or sign in automatically in CI), and inspect every request and token in an activity log.
Testlie is a hosted service at https://testlie.com: there is nothing to install. It also has sandboxes for WhatsApp, push notifications and voice calls, inbound deliveries to your app, mock social login and failure scenarios.
How it fits together
| Piece | What it does |
|---|---|
| Inbox | A mailbox with its own SMTP username and password. Anything your app sends with those credentials lands here, whatever the recipient address. |
| Project | An optional group of inboxes, for example one project per app with an inbox per environment. |
| Team | Owns inboxes, identity providers, API keys and webhooks. Members are owners, admins or members. |
| API key | Lets your tests and scripts call the REST API, for example to wait for an email. |
| Webhook | An HTTP endpoint that is notified when mail arrives. |
| Mock IdP | An OIDC and SAML identity provider with test users, at https://testlie.com/idp/<slug>. |
Where to go next
- Getting started: create an account and capture your first email.
- Sending email from your app: SMTP settings for Node, Python, Ruby, PHP, Java, .NET and Go.
- Testing in CI: wait for a message from your test suite and assert on it.
- Mock identity providers: test OIDC and SAML sign-in without a real IdP.
- API reference: every endpoint.