Introducing connected previews

We’ve introduced a new way to streamline testing when your app or service relies on separate repositories. This update empowers you to test end-to-end workflows in preview environments, eliminating the guesswork and enabling faster iteration.

🚀 What’s new?

You can now manage environment variables for previews, allowing your previews to communicate seamlessly. For example, a frontend preview can use a BACKEND_URL variable to point to the backend preview specific to your feature. This ensures you can test the entire workflow in a cohesive preview environment.

🤔 Why did we make this change?

Before this change, testing features that required changes in separate repositories was a challenge. Developers couldn’t fully test workflows without a manual workaround, leading to slower development and potential issues slipping through the cracks. This update simplifies the process, letting you focus on building and refining your features.

🛠️ How it works

• Define environment variables in your preview settings.
• These variables can be set at runtime to link your related previews.

✨ Key benefits

• Streamlined testing: Test end-to-end workflows effortlessly.
• Faster iteration: Focus on feature development with a simpler setup.

⚠️ Important notes

When environment variables change, a re-deployment of the preview is necessary.