Changelog

New features and improvements in Testlie.

Atom feed
  1. Connect AI apps by signing in

    AI apps that support MCP with OAuth can now connect to Testlie without a token to copy. Add https://app.testlie.com/api/mcp as a connector, sign in, pick the team, optionally one project, and what the app may do.

    • Permissions follow your role on every request; leave the team and the app loses access at once.
    • Access tokens are short-lived and refresh themselves; an unused connection expires after 30 days.
    • See and disconnect your apps under My account → Connected AI apps; administrators see the team's under MCP → Connected apps.
    • The AI apps & MCP page now has a step-by-step connect guide for every member.

    MCP guide

  2. SDKs, CLI and GitHub Action on public registries

    Every client now installs from its registry:

    • Node.js SDK with Playwright and Cypress helpers: npm install --save-dev @testlie/sdk
    • CLI without a Node project: npx @testlie/cli
    • Python client and pytest plugin: pip install testlie
    • Go client: go get github.com/carriergrade/testlie-go
    • GitHub Action: uses: carriergrade/testlie-action@v1

    SDKs & CLI

  3. Projects for every system

    Projects now hold every kind of test system, not just inboxes. Pick a project and the Email, SMS, Voice, request bin, WhatsApp, Push and API mock pages all filter to it, and new systems land in the project you have open.

  4. Scoped MCP access for agents

    Give an agent a grant for one project or the whole team that expires in 7 to 90 days, instead of an API key.

    • captures:read lets it read email, SMS, voice calls, WhatsApp, push and request-bin captures. Credentials in headers and query strings are masked first.
    • The opt-in systems:write lets it create inboxes, SMS accounts, request bins and API mocks. Nothing can be deleted or rotated over MCP.
    • Also new: connections to external MCP servers with an explicit tool allowlist, and MCP sandboxes for testing your own MCP clients.

    MCP guide

  5. Telecom interfaces, ERP and CRM simulations

    • Telecom: subscriber and plan management, CPE management with TR-181 device fixtures, the NF Repository (TS 29.510), SM Policy Control (TS 29.512) and Converged Charging (TS 32.291) test subsets. Synthetic subscribers only.
    • ERP: NetSuite, Business Central, Odoo, SAP S/4HANA and ERPNext.
    • CRM and business tools: Salesforce, HubSpot, Baserow and Mixpanel.

    Telecom guide

  6. Mock payment gateways, KYC and more API mocks

    • Payments: Stripe-, Adyen- and PayPal-compatible APIs with test cards, hosted 3-D Secure and checkout pages, and signed webhooks. BlueSnap-compatible transactions and vaulted shoppers.
    • Identity verification: IDWise, Onfido, Sumsub, Veriff, Persona, Jumio, Shufti Pro, Trulioo and Stripe Identity mocks with a hosted capture page.
    • More APIs: Segment, OneSignal, DocuSign, Adobe Acrobat Sign, Airtable, Lean Technologies, and Mandrill- and Plaid-compatible APIs.

    Mocks accept test data only and never contact the provider they emulate.

    API mocks · Payment gateways · KYC

  7. WhatsApp, push, voice and failure scenarios

    • WhatsApp: a Cloud API sandbox that captures messages, templates and statuses.
    • Push: APNs- and FCM-compatible endpoints that capture notifications.
    • Voice and OTP calls: a Twilio Voice-compatible Calls API with TwiML and spoken codes.
    • Inbound to your app: send texts and email to your app the way Twilio, SMPP, SendGrid, Mailgun and Postmark deliver them.
    • Spam report: spam score, inbox placement and the Gmail/Yahoo sender checklist for every email.
    • Failure scenarios: one-click presets for an SMTP outage, slow SMTP, IdP outages, carrier failures and a dead webhook receiver.
    • Social login: Google, GitHub, Apple and Microsoft sign-in presets for mock identity providers.
  8. SMS over SMPP

    Bind any SMPP 3.4 client to an SMS inbox. Messages are captured with delivery receipts, GSM-7 and UCS-2 text and concatenated messages, on a plain and a TLS port. Connection details are on the SMS page.

    SMS over SMPP

  9. SMS, request bins and SDKs

    • Capture texts through a Twilio-compatible API and read one-time codes and magic links from them.
    • HTTP request bins with configurable responses.
    • Link, accessibility and authentication checks for email, plus Slack and Teams webhooks.
    • Mock identity providers gain failure modes, MFA step-up and SCIM provisioning.
    • The first Node.js, Python and Go clients, a CLI and a GitHub Action.