Item logo image for Proxy Mail QA for Chrome

Proxy Mail QA for Chrome

5.0(

1 rating

)
ExtensionDeveloper Tools7 users
Item media 5 (screenshot) for Proxy Mail QA for Chrome
Item media 1 (screenshot) for Proxy Mail QA for Chrome
Item media 2 (screenshot) for Proxy Mail QA for Chrome
Item media 3 (screenshot) for Proxy Mail QA for Chrome
Item media 4 (screenshot) for Proxy Mail QA for Chrome
Item media 5 (screenshot) for Proxy Mail QA for Chrome
Item media 1 (screenshot) for Proxy Mail QA for Chrome
Item media 1 (screenshot) for Proxy Mail QA for Chrome
Item media 2 (screenshot) for Proxy Mail QA for Chrome
Item media 3 (screenshot) for Proxy Mail QA for Chrome
Item media 4 (screenshot) for Proxy Mail QA for Chrome
Item media 5 (screenshot) for Proxy Mail QA for Chrome

Overview

Fill sign-up and sign-in forms with test accounts, then get the verification code or link in the page. On test sites you choose.

Testing your app's sign-up flow? Proxy Mail QA for Chrome fills the form with a disposable test account and shows the verification code or link right in the page, so you never leave the tab. HOW IT WORKS 1. Turn it on for your test site: open your app's sign-up page, click the extension and choose Turn on for this site. Chrome asks for access to that one site. Local dev servers are one click, on any port. A site can also be added in the Proxy Mail QA app, under Project settings → Sites; then Give Chrome access in the popup on that site starts it there. 2. Fill the whole form in one click: the button in the email field creates a Proxy Mail QA test address with a fictional name, a username, a date of birth and a strong password, and fills the form. 3. Save the password you used: after you sign up, or set a new password after a reset, it asks whether to save the password to the test address, encrypted, so you or a teammate can sign in as that account later. 4. Sign in again as any test account: on a sign-in form, pick one of your project's test accounts and it fills the email or username and its saved password, screen by screen when the sign-in has several; a screen that asks only for a password offers them too. The ones you used on that site come first. 5. Get the code or link in the page: when the email lands, Fill puts the code in the code field (even a row of single-digit boxes), and Open opens a verify or sign-in link in a new tab. A link meant for a mobile app (such as myapp://) gets Copy, to open on a phone or simulator. WHAT ELSE • Fills your project's custom fields too, such as company size, and marks what it guessed. Teach saves what goes in a field for everyone on the project • The card after a fill sits beside the form rather than over it, and lists what it guessed and what it left empty. Minimise it to a small pill in the corner, or close it: each field it guessed or left empty keeps a small mark, so you can teach that field from the field itself • On a sign-up over several screens, Fill this step (Alt+Shift+F, or Option+Shift+F on a Mac) fills each one with the same test account, and so does Fill this page in the popup • After you press Next or Continue (the button words are read in nine languages), it asks whether the new screen is part of the sign-up. Keep this screen fills each later screen on that site by itself, or asks your project's leads first where only they change sites • Passwords made on your device to fit each field's length and character rules • Dates of birth filled into date pickers, typed date fields, and day, month and year drop-downs • Countries filled into drop-downs, radio buttons, text boxes and boxes with suggestions, found by their code or their name in English or the page's language • Works with React and Vue apps, forms built from web components (such as Shoelace), forms in frames, and forms built without a form tag, as many app builders make them • The toolbar popup makes a new test address with a name, username, date of birth and password, each with its own Copy button, and fills the page with it in one click • It also lists your project's recent test addresses with their newest code or link, ready to copy on any tab, plus a password generator, and opens on the project linked to the site you're on • Each site belongs to a project and an environment, such as staging, QA or local, so every address is labelled with where it was used OFFERS AND MARKETING (IN LABS) Switch on Marketing and offer emails in your Proxy Mail QA account under Labs, then choose what to test on each site: • Offers: when a welcome offer's coupon arrives, a card shows it with its discount and end date. Fill promo code puts it in the promo field only, and "Did it work?" records whether checkout accepted it • Marketing: notes whether the sign-up form's marketing box was ticked when the page loaded and when you submitted, saved with the test account • "I unsubscribed" in the popup: after you unsubscribe with the email's own link, any later marketing from that sender is flagged • Pause it on a tab with one switch; the badge shows ON wherever it's active, and 1 when a sign-up's save question waits for you in the popup PRIVATE BY DESIGN • Off everywhere until you turn it on for a site, and Chrome asks for access to that one site • Never all sites: it refuses patterns like *.com and warns before turning on for a site that looks live • On those sites it reads the email, name, username, company, date-of-birth, country and password fields of the form you fill, the language the page says it's in, and the words in and around that form to tell a sign-in from a sign-up, plus the promo code field and the marketing box when you turn on Offers or Marketing there • For the form's other fields it reads only their labels, names, IDs, test IDs, placeholders, types, rules and options, and whether each is empty, never what's in them, to fill your project's custom fields and guesses. One exception: when a fill leaves a question's tick boxes, or a drop-down that takes several answers, under Not filled with no custom field, it reads which are ticked or selected, to start Teach's list for it. That stays on the page unless you press Save and fill or Ask a lead in Teach, which sends the answers still ticked in the list to your project, as that custom field's answers • To tell the next screen of a sign-up from its end, it reads the words of the button you press and a step line such as "Step 2 of 3", on the page only. To tell when a sign-up has ended, it looks at the words of the page's buttons and links and whether its tick boxes are ticked, on the page only. It never presses a button or submits a form • When it fills a later screen of a sign-up on a site you turned it on for, it adds the paths of that page and the sign-up's first page to your project as suggested sign-up screens (never a query, and never a path made for one person), and keeps what custom fields and guesses filled on the test account with each field's label • To leave payment screens alone, it checks whether the page has a card payment frame, such as Stripe's, from the frame's address, name or title • A new password stays on your device until you choose to save it; a saved one is fetched only when you pick that account to sign in, and every reveal is logged • It never opens links itself, so single-use links stay valid You need a free Proxy Mail QA account (https://proxymail.qa). The extension is free on every plan and signs in through the Proxy Mail QA app, with no separate password.

Details

  • Version
    0.9.0
  • Updated
    November 13, 2026
  • Size
    726KiB
  • Languages
    English (United States)
  • Developer
    Sidequest Explorers Inc
    1111B S Governors Ave STE 25303 Dover, DE 19904-6903 US
    Website
    Email
    aaquib@sidequestexplorers.com
    Phone
    +44 7858 350510
  • Trader
    This developer has identified itself as a trader per the definition from the European Union and committed to only offer products or services that comply with EU laws.
  • D-U-N-S
    145131795

Privacy

Manage extensions and learn how they're being used in your organization

Proxy Mail QA for Chrome has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.

Proxy Mail QA for Chrome handles the following:

Personally identifiable information
Authentication information
Personal communications
Web history
Website content

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, please open this page on your desktop browser

Search
Clear search
Close search
Google apps
Main menu