Dark Launching
Dark launching is where new features are released but remain hidden from the user, allowing for testing and monitoring of the feature in a live environment without affecting the user experience.
Goal
The primary goal of dark launching is to validate whether the new feature performs as expected under real conditions, without affecting the user experience.
Context
It can be very difficult to accurately test the load patterns and performance of a new feature in a test environment. Dark launching allows for the feature to be tested in a live environment, with real users, without affecting the user experience.
Inputs
| Artifact | Description |
|---|---|
| Live Product | The code changes deployed to the production environment. |
| Feature Toggles | Toggles that can be controlled at runtime. |
Outputs
| Artifact | Description | Benefits |
|---|---|---|
| Defects Log | A compilation of defects, usability issues, and observations made during exploratory testing. | Provides immediate feedback and insights into application quality. |
Anti-patterns
- Lack of Monitoring: There is a risk that the feature will cause a degradation in performance or stability, and without adequate monitoring this may take time to identify.