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 checklist

This topic describes the steps you should take to QA your experiment before launching in Optimizely Full Stack.

Here is a QA checklist for launching an experiment:

  1. Start your test in a non-production environment.
  2. Force yourself into each experience using a QA tool. See Choose QA tests.
  3. Trigger any conversion events being tracked by the test AND are on the same page as a variation change. Testing pre-existing or down-funnel events may not be necessary unless those events also change.
  4. If you cannot see your testing activity affect the Results page, this may be due to how Optimizely counts conversions. Conversions are attributed to the first variation assignment.
    It may be necessary to reset results in between testing your variations.
  5. If step 4 does not produce the results you expected, troubleshoot by increasing the log level and consulting your error handler to debug.
  6. Repeat steps 2 through 5 for each variation of your test.
  7. Confirm your results. There is a 5-minute interval on results page updates, so you might have to wait up to 5 minutes for it to update. The time of the last update is shown on the results page.
  8. Reset the results of the experiment so that your QA activity does not skew the Results page.
  9. Launch in your production environment.