Test Referral Signup Flow With Two Fake Identities

To properly test referral signup flows, you need two distinct identities and two separate inboxes. Using a single shared Gmail account for both referrer and referred user, or relying on simple Gmail plus addressing, often fails to capture the nuances of how your system handles unique user enrollments and referral attribution. This approach simulates real-world user acquisition where each participant has their own email and registration process.

Simulating the Referral Flow

The core of testing a referral signup flow involves two parties: the referrer and the referred user. The referrer invites a new user, and the referred user signs up using a unique referral link. Your system should then recognize this new signup as originating from the referral, often triggering rewards or specific user states for both individuals. Testing this requires you to act as both. You'll need to generate a referral link from one "identity" and then use that link to create an account with a second "identity." Without two distinct email addresses and associated accounts, you can't verify that the referral mechanism correctly tracks and attributes the new user to the original referrer.

Setting Up Your Test Environment

Before you can test the referral signup flow, you need to establish your two test identities. This means acquiring two distinct email addresses that can receive verification emails and OTPs. For ease of management and to avoid cluttering your primary inbox, using temporary email addresses is highly recommended. The FakeSignup Chrome extension is ideal for this. It provides disposable email addresses and an inbox directly within your browser, eliminating the need to constantly switch tabs or manage multiple email clients.

Here's a basic setup procedure:

1. Install the FakeSignup Extension: Add the extension to your Chrome browser. You can find it here: FakeSignup on the Chrome Web Store.
2. Generate First Email (Referrer): Open the FakeSignup extension. Generate a new, temporary email address. This will be your "referrer" identity. Note down this email address.
3. Generate Second Email (Referred User): Open the FakeSignup extension again (or use its side panel feature). Generate a second, distinct temporary email address. This will be your "referred user" identity. Note this email address as well. Each email generated by FakeSignup comes with its own isolated inbox accessible via the extension.

Executing the Referral Signup

With your two identities and their respective inboxes ready, you can now proceed with the actual test. This involves a sequence of actions to simulate the referral process from start to finish.

1. Initiate Referral from Identity 1:

   • Go to your application's signup or user profile page.
   • Register the "referrer" email address (the first one you generated).
   • Complete any necessary email verification or OTP steps for this account.
   • Navigate to the section where a user can find or generate their referral link.
   • Copy the unique referral link.

2. Use Referral Link with Identity 2:

   • Open a new incognito window or a different browser profile to ensure no cookies or session data interfere.
   • Paste the referral link into the browser's address bar and press Enter.
   • You should now be on your application's signup page, but with the referral code or parameter pre-filled.
   • Enter the "referred user" email address (the second one you generated).
   • Fill in any other required fields for the new user.

3. Complete Signup for Referred User:

   • Submit the signup form for the "referred user."
   • Check the inbox associated with the "referred user" email address (using the FakeSignup extension's inbox view). You should receive a verification email or an OTP.
   • Retrieve the code from the FakeSignup inbox.
   • Enter the code on your application's verification page to complete the signup for the referred user.

Verifying Referral Attribution

After both accounts are successfully registered, the critical step is to verify that the referral was correctly tracked. This involves checking the backend or user interface for evidence of the referral.

• Check Referrer Account: Log back into the "referrer" account. Navigate to their referral dashboard or user profile. You should see the "referred user" listed as a successful referral. Any associated rewards, points, or status changes for the referrer should be reflected.
• Check Referred User Account: Log into the "referred user" account. Examine their profile or any onboarding messages. They might have received a welcome bonus or a specific tag indicating they joined via a referral.
• Backend Data: If you have access to your database or logs, inspect the records for both users. Verify that the referrer_id or equivalent field is correctly populated for the "referred user," linking them to the "referrer" account.

This end-to-end test confirms that your referral mechanism functions as expected, correctly attributing new signups and managing any associated incentives. Relying on single email addresses or basic plus addressing won't provide this level of assurance.

Handling OTPs and Verification Codes

A common bottleneck in testing signup flows is managing the One-Time Passwords (OTPs) or verification codes sent via email. Manually switching between your application and your email client is time-consuming and error-prone. The FakeSignup extension's built-in inbox feature streamlines this process. When an email containing a verification code is sent to one of your generated temporary addresses, the code will appear directly in the FakeSignup side panel for that specific inbox. This allows you to copy the code and paste it back into your application's verification form without leaving the context of your testing session. For premium users, FakeSignup's Full Auto feature can even help automate the retrieval of these codes.