Pre-Launch Checklist:- A check-list is a list of items/tasks/assignments that are recorded for tracking.This catalog/list could be either ordered in a sequence or could be random/unsystematic. Checklist is needful for tracking and judge/rate completion (or non-completion). To make a note of tasks, so that nothing is overlooked.
You have to make sure the different components are working as expected -- and prevent errors along the way.
Components of Checklist are mentioned below:
--->Source Code - Check whether your code is working correctly or not.
Verify all source code meets coding standard, run Check-style or other style-checker and do manual inspection. Your code should be 'Complete and effective', 'Accurate', 'Fast' (for competent reviewers). Your code should be bug/issue free.
--->Timing - Check whether your variation is showing up properly when it is required, without any error or bug?
Your original content should flash before the developed code takes effect. Make sure that the code developed by you executes very quick which is enough to avoid any flashing.
--->Targeting - Check whether your trial is appearing and is going on the right direction, to the right audience?
Targeting involves both the URL and viewers conditions and ensure that your test should run at front-end and people you intend to include.
--->Goals - Check the required goals are getting active when they should be and catch correct data?
Goals should fired with actual/real tracking calls when triggered. In other words, when it is triggered, it should report directly to optimize. If you dont analyses your goals properly, you may end up needing to throw out the results of your test/investigation because it isn't setup to capture accurate/correct data.