Sixpack: Language-Agnostic A/B Testing
sixpack.seatgeek.com
Sixpack: Language-Agnostic A/B Testing
1–10 of 19 posts
Re: Sixpack: Language-Agnostic A/B Testing
#2This is exactly what I've been looking for. Ever since Google Website Optimizer went away, I've been kinda floating in the wind when it comes to UI testing. Major props to SeatGeek for releasing this so that others can use it.
Re: Sixpack: Language-Agnostic A/B Testing
#3This is exactly what I've been looking for. Ever since Google Website Optimizer went away, I've been kinda floating in the wind when it comes to UI testing. Major props to SeatGeek for releasing this so that others can use it.
edit: Changed "GWO" to "Google Website Optimizer"
Re: Sixpack: Language-Agnostic A/B Testing
#4[deleted]
Re: Sixpack: Language-Agnostic A/B Testing
#5Looks very nice - should be pretty easy to fork for feature toggles too.
Re: Sixpack: Language-Agnostic A/B Testing
#6Heh, I get the joke in the name. Thing about it...ab testing...
Re: Sixpack: Language-Agnostic A/B Testing
#7Looks very nice - should be pretty easy to fork for feature toggles too.
It absolutely would.
Re: Sixpack: Language-Agnostic A/B Testing
#8Looks very nice - should be pretty easy to fork for feature toggles too.
What is a feature toggle?
Re: Sixpack: Language-Agnostic A/B Testing
#9It would be cool if you could divert only a fraction of traffic into a particular test. A future feature, perhaps?
Re: Sixpack: Language-Agnostic A/B Testing
#10It would be cool if you could divert only a fraction of traffic into a particular test. A future feature, perhaps?
You actually already can do that, and all of the clients support it. It's probably just not documented.
Passing ?traffic_dist=10 to the participate endpoint will only direct 10% of traffic to the test. The rest will get the control alternative.
I'll add this to the documentation.