The Full Stack Developer Guide Developer Hub

Welcome to the Full Stack Developer Guide developer hub. You'll find comprehensive guides and documentation to help you start working with the Full Stack Developer Guide as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

QA checklist

Here's 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 that are being tracked by the test AND are on the same page as a variation change. Testing pre-existing or downfunnel events may not be necessary, unless those events also change.
  4. If you're unable to 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 doesn’t 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 doesn't skew the Results page.
  9. Launch in your production environment.

Updated about a year ago


QA checklist


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.