Testing

Send Test lives in the more-actions menu beside Publish.

Use it when you want to verify the current compiled HTML without treating the current edit as the final saved version.

When to use testing

Testing is useful when you want to:

• spot-check the current version before publishing
• confirm a fix after editing a specific section
• give yourself or a teammate a quick delivery check
• validate the current compiled output without using publish as the save point

Testing versus preview

Use Preview when you want to inspect rendered output, code tabs, or diagnostics inside the builder.

Use testing when the next question is about how the compiled email behaves as an actual test send rather than just inside the editor UI.

Testing versus publish

Use Publish when you are ready to save the version back to the dashboard record.

Use testing when you still want a safety buffer before that final save step.

More-actions menu context

The same more-actions menu also includes file actions such as importing JSON and exporting the document as HTML, JSON, or MJML.

Those file-based flows are covered in Imports, Exports, and Drafts.

Best practices

• Use the Send Test action after meaningful content or styling changes that need a quick verification pass.
• Combine testing with preview rather than choosing only one of them.
• Do not use testing as a substitute for publish when the saved dashboard record actually needs to be updated.
• Review mobile preview first if the change affects stacking, width, or text density.