Optimizely will be sunsetting Full Stack Experimentation on July 29, 2024. See the recommended Feature Experimentation migration timeline and documentation.

Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

QA and troubleshoot

This topic describes simple QA and troubleshooting techniques for Optimizely Full Stack.

Before you publish a test or rollout a feature live to your visitors, it is important to make sure it works the way you expect.


Optimizely gives you several tools for:

  • Testing experiment variations as a developer
  • Automating testing of flags and rollouts in a QA role

These tools all share in common one thing: they let you force a given user (or, in QA test automation context, test runner), into a given feature flag state or given experiment variation.

For more information see Choose QA tests


For more information about troubleshooting, see Troubleshoot