|
Feature Rollout |
Feature Test |
|
It allows you to gradually launch a new feature. |
It allows you to test multiple variations of a feature. |
|
Deals with controlled release of a feature. No data is captured. |
Data from different variations are captured to identify which one is the best. |
|
A feature is turned on/off in different environments with a simple toggle option. No code change is needed. |
A product feature is tested by creating variations with a different set of variables. |
How Does it Work?
Consider a scenario where you have deployed a feature to your application and have created a feature rollout and feature test for it.
Here, there are two possible use cases:
- Feature Rollout is running with the specified set of audience and the allocated traffic
- Feature Test is running with the specified set of audience and the allocated traffic
Possible Outcomes
|
Is a Feature Test Audience? |
Is Feature Test Traffic Allocated? |
Is a Feature Rollout Audience? |
Is Feature Rollout Traffic Allocated? |
Outcome |
|
Yes |
Yes |
No |
No |
Feature Test |
|
Yes |
No |
Yes |
Yes |
Feature Rollout |
|
Yes |
Yes |
Yes |
Yes |
Feature Test |
|
No |
No |
Yes |
Yes |
Feature Rollout |