Skip to main content

Get OTP from email

/**
* Retrieves an OTP from Gmail in a headless tab.
* @param {Object} options - The options for the function.
* @param {string} options.email - The Gmail email address.
* @param {string} options.password - The Gmail password.
* @returns {Promise<string | null>} The OTP retrieved from the email.
*/
export async function getOtpFromGmail({
email,
password,
}: {
email: string;
password: string;
}): Promise<string | null> {
const { chromium } = require("playwright");
// Launch a headless browser context for Gmail login
const browser = await chromium.launch({ headless: true });
const context = await browser.newContext();
const page = await context.newPage();
await page.goto("https://mail.google.com");
const emailInput = await page.waitForSelector("#identifierId");
await emailInput.fill(email);
const emailNextButton = await page.waitForSelector("#identifierNext button", { timeout: 2000 });
await emailNextButton.click();
const passwordInput = await page.waitForSelector("input[type='password']", { timeout: 4000 });
await passwordInput.fill(password);
const passwordNextButton = await page.waitForSelector("#passwordNext button", { timeout: 2000 });
await passwordNextButton.click();
await page.waitForURL("https://mail.google.com/mail/u/0/#inbox", { timeout: 25000 });
// Open the latest email from the OTP provider
const emails = await page.$$(`span[email='<provider email>']`);
if (emails.length > 1) {
await emails[1].click();
}

// Look for the OTP in the email content
const emailContent = await page.locator("span").allInnerTexts();
const otpRegex = /\b(\d{6})\b/;
for (const text of emailContent) {
const match = text.match(otpRegex);
if (match) {
await browser.close(); // Close the headless browser
return match[1];
}
}
await browser.close();
return null;
}

Comments

Popular posts from this blog

Mock server

 Using a mock server in end-to-end (E2E) testing is indeed common, and it can be used for more than just reading values. Mock servers simulate the behavior of real servers and can handle various HTTP methods, including POST , PUT , DELETE , and PATCH , in addition to GET . This means you can use a mock server to simulate interactions that involve writing data, such as filling out and submitting forms. Automating Form Interactions with Mock Servers Simulating Form Submissions : Mock servers can be set up to handle form submissions. When you submit a form in your E2E test, the mock server can capture the request and respond with a predefined response. Validating Data : You can use the mock server to validate the data sent by your application. The mock server can check if the request body matches the expected format and values. Response Handling : After submitting a form, your application typically processes the server's response. The mock server can provide specific responses to test...

Browser Context

 In the context of Playwright, understanding how pages and browser contexts work is crucial for managing test isolation and ensuring reliable test execution. Here’s an explanation: Browser Context in Playwright Definition : A browser context in Playwright is akin to a new browser profile. Each browser context provides a separate environment where cookies, local storage, and other session data are isolated from other contexts. Isolation Between Tests : When you run tests using Playwright, each test typically operates within its own browser context. This means that: Fresh Environment : Every test starts with a clean slate, ensuring that any changes made by one test (such as cookies or session data) do not affect subsequent tests. Consistent State : Tests are independent of each other in terms of state, which helps in avoiding interference between different test cases. Page Isolation : Within each browser context, individual pages (created using page objects in Playwright) are also i...