Enterprise & Mid-Market Account Manager

Cypress email testing tutorial with MailSlurp. Step-by-step Cypress email testing tutorial with MailSlurp: create inboxes, assert signup links and OTP codes, and stabilize CI runs. MailSlurp integrates with Cypress so you can test real email behavior in browser-driven end-to-end flows. This tutorial covers setup, test structure, and CI hardening. What you can validate. Use Cypress + MailSlurp for flows that break often in production: * Signup confirmation links * Password reset links * OTP passcodes * Invitation acceptance * Transactional email content assertions How the stack fits together. * Cypress drives browser actions. * MailSlurp creates and manages real test inboxes. * Your tests wait for and assert incoming messages. This avoids brittle mocks and gives stronger confidence in release pipelines. Setup links. Configure Cypress and mailslurp. Start with client configuration: const {defineConfig} = require('cypress') module.exports = defineConfig({ defaultCommandTimeout: 30000, requestTimeout: 30000, viewportHeight: 800, viewportWidth: 800, videoCompression: false, e2e: {setupNodeEvents(on, config),},}) Then implement login or signup helpers in your tests: Add inbox helpers. Create reusable commands for inbox provisioning and retrieval: const {MailSlurp} = require('mailslurp-client'); // set your api key with an environment variable `CYPRESS_API_KEY` or configure using `env` property in config file // (cypress prefixes environment variables with CYPRESS) const apiKey = Cypress.env('API_KEY') const mailslurp = new MailSlurp({ apiKey}); Cypress.Commands.add("createInbox", => {return mailslurp.createInbox;}); Cypress.Commands.add("waitForLatestEmail", (inboxId) => {// how long Mailslurp should hold connection waiting for an email to arrive const timeoutMillis = 30_000; return mailslurp.waitForLatestEmail(inboxId, timeoutMillis)}); Use generated inboxes in each test for isolation: const password = "test-password"; let inboxId; let emailAddress; it('can generate a new email address and sign up', => {// see commands.js custom commands cy.createInbox.then(inbox => { // verify a new inbox was created assert.isDefined(inbox) // save the inboxId for later checking the emails inboxId = inbox.id emailAddress = inbox.emailAddress; // sign up with inbox email address and the password cy.get('input[name=email]').type(emailAddress); cy.get('input[name=password]').type(password); cy.get('[data-test="sign-up-create-account-button"]').click;});}); Practical test blueprint. A robust Cypress email test usually follows this shape: * Create a fresh inbox. * Trigger the UI flow (signup/reset/login). * Wait for matching inbound email. * Parse and assert required fields. * Continue flow by visiting extracted link or entering OTP. CI stability checklist. * One inbox per test worker. * Explicit timeouts for asynchronous delivery. * Minimal assertions first; deep assertions second. * Retry carefully, not as blanket masking. * Log failing message payloads for triage. Related implementation routes. Next step. Create a free account and run one signup + confirmation test end-to-end before expanding to OTP and reset scenarios.

Cypress Cloud MCP is generally available. May 20, 2026 By Emily Wisniewski Today, Cypress Cloud MCP is generally available! When cypress.io launched Cloud MCP in beta two months ago, cypress.io had a hypothesis: developers shouldn't have to copy-paste stack traces into a chat window to get their AI assistant to help them debug. Cypress Cloud already had all the context their assistant needed. cypress.io just needed to close the gap. The response told cypress.io the hypothesis was right. In the 9 weeks since beta, over 500 organizations connected, and more than 1,000 developers have used it to query their Cypress Cloud data directly from AI assistants like Claude, Cursor, and GitHub Copilot. What's changed since beta. cypress.io used the beta period to listen, and three things came back to act on before GA. UI Coverage and Accessibility. The initial beta focused on test failures and flaky tests - what broke and why. But your AI assistant can now go further. With UI Coverage data available through MCP, you can ask your agent which parts of your application aren't covered by tests at all, not just which tests are failing. And with Cypress Accessibility integrated, your agent can triage violation reports, group issues by severity, and suggest fixes - the kind of work that used to mean a long morning in a separate tool. OAuth authentication. Setting up Cloud MCP in beta meant generating a personal access token, copying it, and managing rotation. cypress.io heard that it was friction, especially for teams rolling this out across multiple developers. OAuth is now the recommended authentication method. Add the server URL, sign in through your browser, and your client manages the session automatically for 30 days. No tokens to configure or to keep track of. Personal access tokens still work for clients that need them, but most won't. What you can do with it today. The honest pitch is this: instead of navigating to Cypress Cloud, finding the run, scanning the failures, building a mental model, and switching back to your editor. Your assistant does that work, and you stay in flow. Some prompts that reflect how people are actually using it: * "What failed in my last CI run on main and what's the root cause?" * "Which parts of the checkout page don't have UI Coverage?" * "Summarize the critical accessibility violations from my latest run and group them by what I can fix now versus what involves third-party components." * "Which tests were flaky in the last run?" These aren't impressive because the prompts are clever. They're impressive because the answers come back grounded in your actual run data, not a guess. What cypress.io is building toward. One piece of feedback from beta users has been consistent: they want their AI to see not just the error, but the full execution context - the DOM state, the network requests, the moment before the failure. That's what Test Replay captures, and cypress.io is running experiments to expose that data. Behind all of this, though, is the bigger question: how do cypress.io give developers the right testing context, in the right place, fast enough that AI assistance actually changes how the work feels? cypress.io is exploring more than one answer. The constant across all of them is the same goal - helping you act quickly, with confidence, so you can focus your time where it matters. Ready to close the context gap? Cloud MCP is free on all Cypress Cloud plans. Enable the integration from your organization's Integrations page, authenticate with OAuth or a personal access token, and add the server URL to your AI client: https://mcp.cypress.io/mcp. Full setup instructions are in the Cypress Cloud MCP documentation. If you set it up during beta, you don't need to do anything because you're already on GA.