Introduction

When working on the josedantearroyo/dyad project, we encountered a classic testing challenge: environment variable leakage. As our suite grew, global test configurations began interfering with one another, leading to brittle end-to-end (e2e) tests that were difficult to debug, particularly when working with Azure service integrations.

The Problem: Shared State in E2E Tests

Managing multiple AI providers in a single application often leads to configuration friction. In our work on the Dyad project, we recently tackled the complexity of our Azure OpenAI integration, moving away from fragmented settings toward a robust, UI-driven configuration workflow.

The Problem: Configuration Guesswork

Previously, Azure configuration relied heavily on a mix of environment