Set up the VS Code experimentation framework in Bicep Extension
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
To allow A/B testing of incremental changes, the VS Code experimentation framework helps us know the features/ideas we add or augment have the desired outcome towards our goals.
Once this is set up, we are able to test our features in a tested rollout 10% -> 50% before making the feature 100%. We are able to set up metrics before a feature is created to understand the impact of the changes we make (perf, increase in usage of specific features). We'd also be able to rollback any unintended regressions if they were to happen.
Contributor guide
Research direction
No file, test, or entry point is named. Start by locating the Bicep Extension's VS Code integration and reviewing how the VS Code experimentation framework is used. Done means experiments can support staged rollouts, preplanned metrics, and rollback of unintended regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100