Our HubSpot Sandbox is part of a wider test ecosystem with upstream and downstream platforms all sharing a common set of data and fully integrated. We are introducing automated testing which requires us to be able to run “realistic” end to end scenarios across multiple systems and using our integrations to move data between platforms.
We have two linked challenges with how Sandbox is set up:
- HubSpot email validation will only allow you to enter “valid” emails (which appears to be evaluated based on them having a routable domain). Although HubSpot itself blocks sending emails “outside” some of our other linked platforms do not, so we have a workflow that appends a suffix to all entered emails so that as they propagate through our test ecosystem they’re “safe” from accidental sending. The ask here is:
* Can the HubSpot native email domain check also permit RFC2606 domains (at least in Sandbox) to be added through the UI (.test, .example, .invalid) - There are times when we do want to send emails to test or demonstrate that automations or other features are working. The ask here is:
* Can Sandboxes offer a small number of selected domains that will pass emails (so not just linked to users who are themselves Sandbox users). What we’d want to do is create our own company test domain with a selection of test users so that we can run automated testing across the whole test ecosystem. This should be restricted enough that nobody’s tempted to run their business out of a Sandbox but still allows you to gain confidence before releasing features to Production.