Requirements for django A/B testing tool

May 24, 2009 – 22:38

Thought recently about an A/B testing tool to use in our django projects

My requirements are:

  1. Survive model changes. That’s other version of the app under test may use a different schema or totally different db. I guess that automatically rules out plain middleware approach..
  2. May target specific category of visitors/users. Say, only staff or just those, who opted-in for a beta testing or just US visitors, et cetera.. That excludes simple nginx/fastcgi balancers.
  3. Calculate OEC (Overall Evaluation Criterion) and the level of statistical significance.

My links on the topic: