Split testing in Pyramid - any experiences?

[Benjamin Sims]

Hi,

I'm trying to implement split testing for a Pyramid / Chameleon application, and I'd appreciate anyone who has experience of this sharing any tips.

We always have a test_group attribute available on our requests. We'd like to arrange things such that we can specify that if the user is in group B, they get a template from a particular directory if it exists. If the template does not exist in that directory or the user is in group A, they get the standard template.

Our thinking at the moment is that this should be done using a custom renderer, based on the default Chameleon pt renderer. Essentially, this would check the request and alter the resource used as appropriate.

Does this sound sensible, and does anybody have any experience of doing this sort of thing?

Thanks,

Ben

[Jonathan Vanasco]

how are you invoking templates? with @view_config or
render_to_response ?

i was digging into the default renderers last week; they largely just
proxy + wrap a template lookup from the base library.