PoC: GitLab A/B testing
What does this MR do?
How Unleash Variant works
VariantDefinition:
- name: String
weight: Int # This weight is controlled by the Unleash Context (e.g. 'userId')
payload: String
overrides:
- context_name: String (Enum: 'userId', 'sessionId', 'remoteAddress', etc)
values: Array<String>
Process:
- Evaluates
overrides
. If matches, returns thename
. - Evaluates
weight
. - If it doesn't match, it falls back to a default.
Example:
- name: 'blue'
weight: 50
payload:
color: blue
overrides:
- context_name: String (Enum: 'userId', 'sessionId', 'remoteAddress', etc)
values: Array<String>
- name: 'red'
weight: 50
payload:
color: red
overrides:
- context_name: String (Enum: 'userId', 'sessionId', 'remoteAddress', etc)
values: Array<String>
References
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Shinya Maeda