> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usekinetic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Email test checklist

> Best practices for testing your interactive email templates before sending

## Testing overview

Once you've created an email and added forms, proper testing ensures your recipients see exactly what you intended. While the preview feature inside the Kinetic template builder offers a quick way to check your template during development, the end result can differ from what you see in the preview panel, as we cannot simulate email inboxes perfectly.

<Warning>
  We highly recommend sending test emails to verify your emails look exactly as intended across different email clients.
</Warning>

## Best testing practices

### Send final tests through Klaviyo

To be 100% sure that users receive the email design you intended, send your final tests via Klaviyo to remove any platform-specific variables from your tests. This ensures your test environment matches your production environment exactly.

### Understanding email versions

Your interactive email contains multiple versions that display based on the recipient's email client:

* **AMP version** - Interactive version for Gmail
* **Apple Mail version** - Interactive version for Apple Mail
* **Fallback version** - Static version for non-interactive clients

<Info>
  **Important:** The sender address does not influence which email template you see, only which inbox you open the email in.

  For example:

  * If you send to `myname@gmail.com` but open it in Outlook, you will not see the AMP version
  * If you send to `myname@hotmail.com` but open it in Gmail, you will see the AMP version
</Info>

## Testing checklist

We recommend covering all mime types in your tests on both mobile and desktop devices.

### AMP version testing

**Where to test:** Gmail (desktop and mobile app)

* Open your test email in Gmail on desktop + an Android device. If possible, check via the Gmail app on iOS as well.
* Check that interactive elements display correctly.
* Test form functionality such as product recommendations and styling.

### Apple Mail testing

**Where to test:** Apple Mail (macOS and iOS)

* Open your test email in Apple Mail on Mac + iPhone/iPad.
* Check that interactive elements display correctly.
* Test form functionality such as product recommendations and styling.

### Fallback version testing

**Where to test:** Outlook, ProtonMail, web.de

* Open your test email in any of these clients to see the static fallback.
* Verify the fallback design.
* Test that click-through to web version works properly.

## Testing workflow

Follow this systematic approach to thoroughly test your templates:

1. **Preview in Kinetic** - Use the preview panel for quick checks while building your template. This gives you an immediate sense of layout and design.

2. **Send test from Kinetic** - Send initial test emails directly from the Kinetic builder to catch any immediate issues with interactivity.

3. **Test in Klaviyo** - Push your template to Klaviyo and send test emails from there to ensure platform compatibility.

4. **Test across clients** - Open the same test email in Gmail, Apple Mail, and Outlook to verify all versions display correctly.

5. **Test on mobile** - Verify responsive design on actual mobile devices, not just browser emulators.

6. **Final validation (optional)** - Send one final test through your Klaviyo flow or a test campaign to confirm everything works in your production environment.

<Tip>
  Create email accounts across different providers (Gmail, Outlook, Apple) specifically for testing to streamline your QA process.
</Tip>

## Next steps

<Card title="Creating an AB test" icon="flask-vial" href="/email-builder/ab-testing">
  Learn more about how to set up an AB test in Klaviyo to compare performance between interactive and static variations.
</Card>