Edge Cases

Unusual scenarios, error handling, and special field types

What These Tests Cover

Edge cases that can cause unexpected behavior: rapid submissions, form resets, network errors, honeypot fields, multiple email fields, and more. These test the SDK's robustness and deduplication logic.

1. Double Submit Dedup Test

Rapid double-click on submit button. Should only capture once.

Submit count: 0
Expected: SHOULD capture only once despite multiple submits

2. Form Reset Empty Submit

Fill email, click reset, then submit empty form.

Expected: SHOULD NOT capture empty email after reset

3. Abandoned Form No Submit

Fill email, but don't submit. Type then leave field.

Expected: SHOULD NOT capture on blur/typing alone

4. Network Failure Error

Simulated fetch that throws a network error.

Expected: SDK should handle gracefully - may or may not capture

5. CORS Error Cross-Origin

Request to cross-origin without CORS headers.

Expected: SDK should not throw - graceful handling

6. Honeypot Field Bot Trap

Hidden _hp_email field. Should be ignored by SDK.

Expected: SHOULD capture real email, ignore _hp_email

7. Referral Email Exclude

Fields named friend_email or referral_email should be excluded.

Expected: SHOULD capture sender@, ignore friend_email/referral_email

8. Multiple Emails Priority

Primary email + CC email fields. Test priority selection.

Expected: SHOULD capture primary email over CC/BCC

9. Encoded Email Base64

Base64 encoded email in hidden field.

Hidden field contains:
Expected: SHOULD capture visible email (encoded field is edge case)

10. Very Long Form 20+ fields

Long form with email near the bottom. Performance test.

Expected: SHOULD capture email even in long form
[Ready] Edge Case Tests Loaded