FakeSignup automates form filling, including email and password fields, by intelligently detecting ARIA attributes when standard HTML elements are ambiguous or missing. This approach allows it to reliably identify input fields and their intended purpose, even on complex single-page applications or sites with custom input components.
ARIA Autocomplete Form Fill for Unhelpful DOMs
When inspecting the Document Object Model (DOM) of a signup form, you might encounter input fields without clear type attributes or associated <label> elements. This is common in modern JavaScript-heavy applications. Standard form-filling tools might struggle to identify which field is for email and which is for a password. FakeSignup overcomes this by looking for ARIA (Accessible Rich Internet Applications) attributes. Specifically, it checks for attributes like aria-autocomplete, aria-label, aria-labelledby, and role on input elements. For instance, an input with role="textbox" and aria-autocomplete="list" might indicate a user-facing text field where an email address could be entered. Similarly, inputs associated with labels that mention "password" or "email" via aria-labelledby will be prioritized. This ARIA-based detection is crucial for accurate ARIA autocomplete form fill, ensuring the correct data populates the intended fields.
Identifying Email and Password Fields
The process begins with a scan of the current page’s DOM. FakeSignup looks for common patterns and explicit ARIA roles that signal input fields. For email fields, it prioritizes inputs that are programmatically associated with labels containing keywords like "email," "account," or "username," especially when those labels are referenced via aria-labelledby. If aria-label is present and contains similar keywords, that's another strong indicator. For password fields, it searches for inputs with type="password" as a primary signal. However, if that's absent or ambiguous, it will look for aria-label or aria-labelledby attributes that clearly indicate a password field, such as "password," "secret," or "PIN." The aria-autocomplete attribute, while not directly identifying email or password, can help pinpoint interactive text fields that might require such input.
Handling Custom Input Elements
Many modern web applications use custom components that don't rely on standard HTML <input type="email"> or <input type="password">. These custom elements might render as <div> or <span> tags but function as input fields. FakeSignup’s ARIA detection is particularly useful here. It can identify these custom elements if they have appropriate ARIA roles, such as role="textbox", and associated ARIA attributes like aria-label or aria-labelledby that describe their function. When these ARIA attributes accurately reflect the intended input (e.g., an ARIA label clearly stating "Email Address"), FakeSignup can correctly interpret the element's purpose and populate it with a generated email address from its temporary email service. This is a core part of its ARIA autocomplete form fill capability.
Generating and Filling Data
Once potential email and password fields are identified, FakeSignup generates the necessary data. For email, it uses its integrated temporary email service. This service provides a unique, disposable email address for each form submission. The extension automatically fills the identified email field with this generated address. For passwords, it generates a strong, random password. If the form has a password confirmation field, it will fill that with the same generated password. This entire process happens automatically as you navigate to a signup page, eliminating manual typing for these common fields.
Receiving Verification Codes
After submitting a form with a generated email address, you'll often need to verify it via an email link or code. FakeSignup’s side panel acts as your temporary inbox. When a verification email arrives for the address you used, the code or link will appear directly within the extension's inbox. You can then copy the OTP code or click the magic link without leaving your current tab or switching applications. This integration streamlines the entire signup and verification workflow, especially when testing multiple user accounts or performing automated checks. You can install the extension here: FakeSignup on the Chrome Web Store.
Saving and Reusing Test Accounts
For scenarios requiring repeated use of the same test account, FakeSignup offers a feature to save credentials. After a successful signup and verification, you can choose to save the generated email address and password. These saved accounts are stored locally in your browser's storage. When you revisit a login page for a previously tested service, FakeSignup can automatically detect and fill the saved credentials, allowing for quick and consistent access to your test accounts without needing to re-signup or regenerate new ones. This is particularly helpful for regression testing or when testing features that require logged-in users.