ab-testing

I'm interested in good strategies for A/B or split testing with the Play Framework. The obvious choice would be to use Google Website Optimizer, however I'd prefer not to for several reasons: Only allows you to test stuff in the presentation layer Difficult to test based on things like revenue (rather than binary events like clicks or conversions) Have to mess up templates with Javascript code Tests must be discrete, whereas I like to be constantly testing new variations Any ideas? If you want the controller to decide which version to use, you can do this (in Scala at least) by selecting

I have a complex appengine service that was written in PHP, now I want to migrate it to Python part by part. Let's say that my service has 2 parts: /signIn/.... and /data/... . I just want to migrate /signIn/ part first, then /data/ later. However, since my service is big, so I want to build new /signIn/ part in Python, then use Traffic Splitting to make some A/B Testing on this part. My problem is that Traffic Splitting can be applied on versions only, so my old and new versions have to be in same module, and same module means that they have to written in same language (I was wrong here, see

I do A/B Testing on our site and I do most of my work is in a JS file that is loaded at the top of the page before anything else is rendered but after jQuery has loaded which comes in handy at times. Taking a very simple example of changing an H1 tag, I would normally inject a style in the head to set the H1 opacity to 0 and then on DOMContentLoaded, I would manipulate the H1 contents and then set the opacity to 1. The reason for this is to avoid a flash of the old content before the change takes place - hiding the whole object is more graceful on the eye. I've started to look at the