A/B testing
Locked
 
Administrator
|
Hi,
I think we miss something like http://www.bingocardcreator.com/abingo I will work on one for a customer, and would like to contribute, not sure I will be able to... I will use/extend at least * org.ofbiz.marketing.tracking * TrackingCode * TrackingCodeType * TrackingCodeVisit * for org.ofbiz.webapp.visit * Visit * Visitor Just to share, in case you have already experimented in OFBiz... Jacques |
|
Thanks Jacques, Looking forward to have your contribution in this area.
-- Ashish On Thu, Feb 24, 2011 at 11:21 PM, Jacques Le Roux < [hidden email]> wrote: > Hi, > > I think we miss something like http://www.bingocardcreator.com/abingo > > I will work on one for a customer, and would like to contribute, not sure I > will be able to... > > I will use/extend at least > > * org.ofbiz.marketing.tracking > * TrackingCode > * TrackingCodeType > * TrackingCodeVisit > * for org.ofbiz.webapp.visit > * Visit > * Visitor > > Just to share, in case you have already experimented in OFBiz... > > Jacques > > |
|
|
In reply to this post by Jacques Le Roux
I have been using blackbox, whitebox, greybox testing for years.
you start at the low level routines and test them and then use risk analysis to evaluate the effect of changing that module. then when you use that module int he next level up you have confident your building on solid ground. so by the time you get to the top you have a confidence level that you have a solid application to present to the client. the other thing is generated automatic test building with reporting. the goal is to reduce man hours in maintaining code. ========================= BJ Freeman Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Jacques Le Roux sent the following on 2/24/2011 9:51 AM: Hi, > > I think we miss something like http://www.bingocardcreator.com/abingo > > I will work on one for a customer, and would like to contribute, not > sure I will be able to... > > I will use/extend at least > > * org.ofbiz.marketing.tracking > * TrackingCode > * TrackingCodeType > * TrackingCodeVisit > * for org.ofbiz.webapp.visit > * Visit > * Visitor > > Just to share, in case you have already experimented in OFBiz... > > Jacques > > |
|
|
A/B testing has nothing to do with proper functioning of software, it is about measuring the user response to it. In ecommerce this usually means testing different cart/checkout designs or product finding designs or whatever to see what results in larger and more frequent orders, or less abandoned carts, or whatever the objective is. Jacques: yes, the internal tracking code stuff is a good tool to measure what is happening with A/B UI routes, especially if the goal is to measure some sort of conversion rate since the TrackingCode and Visit are already automatically associated with orders when they are placed. For A/B routing the controller.xml file is a good tool if you have different sets of screens to test. If it is just a small part of one screen, it is easiest in the screen definition itself to call a randomizer and choose a different conditional section based on the result. OFBiz already has the basic tools you need to implement this sort of stuff, but there is no OOTB reporting. If you do end up writing anything that you think is sufficiently generic I'm sure it would be great to add to the project, but in what I've done in the past beyond these tools already in OFBiz there isn't a whole lot more that is generic (although some sort of generic report that can be customized would be a nice thing to have in the project). -David On Feb 24, 2011, at 12:27 PM, BJ Freeman wrote: > I have been using blackbox, whitebox, greybox testing for years. > you start at the low level routines and test them and then use risk analysis to evaluate the effect of changing that module. > then when you use that module int he next level up you have confident your building on solid ground. so by the time you get to the top you have a confidence level that you have a solid application to present to the client. > the other thing is generated automatic test building with reporting. > the goal is to reduce man hours in maintaining code. > > > ========================= > BJ Freeman > Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52> > Specialtymarket.com <http://www.specialtymarket.com/> > Systems Integrator-- Glad to Assist > > Chat Y! messenger: bjfr33man > > Jacques Le Roux sent the following on 2/24/2011 9:51 AM: > > Hi, >> >> I think we miss something like http://www.bingocardcreator.com/abingo >> >> I will work on one for a customer, and would like to contribute, not >> sure I will be able to... >> >> I will use/extend at least >> >> * org.ofbiz.marketing.tracking >> * TrackingCode >> * TrackingCodeType >> * TrackingCodeVisit >> * for org.ofbiz.webapp.visit >> * Visit >> * Visitor >> >> Just to share, in case you have already experimented in OFBiz... >> >> Jacques >> >> |
|
Administrator
|
From: "David E Jones" <[hidden email]>
> A/B testing has nothing to do with proper functioning of software, it is about measuring the user response to it. > > In ecommerce this usually means testing different cart/checkout designs or product finding designs or whatever to see what results > in larger and more frequent orders, or less abandoned carts, or whatever the objective is. > > Jacques: yes, the internal tracking code stuff is a good tool to measure what is happening with A/B UI routes, especially if the > goal is to measure some sort of conversion rate since the TrackingCode and Visit are already automatically associated with orders > when they are placed. > > For A/B routing the controller.xml file is a good tool if you have different sets of screens to test. If it is just a small part > of one screen, it is easiest in the screen definition itself to call a randomizer and choose a different conditional section based > on the result. David, For now it's only question of pages. I did not think about that, thanks for the track. > OFBiz already has the basic tools you need to implement this sort of stuff, but there is no OOTB reporting. If you do end up > writing anything that you think is sufficiently generic I'm sure it would be great to add to the project, but in what I've done in > the past beyond these tools already in OFBiz there isn't a whole lot more that is generic (although some sort of generic report > that can be customized would be a nice thing to have in the project). It will need to build something with the Content Manager: ie allowing analyst to create/set themself their tests putting start and end points, a bit like in GPO (Google Page Optimizer). Though for now, as I already said, the conversion will only be between a set of pages (alternatives) and another (target) using a next button. I will put an atc in the URL for now. I have still to think about how I will handle things in the Content Manager. I'm confident since I looked at Website, Webpage and WebSiteContent. Then analysts should be able to make changes and remove weaker page and create a new test from there. It's this part that I'd like to contribute, but unfortunately it seems that I will design but not coding ... It's a pleasure to see TrackingCodeEvents has already almost all what I need! I have question: I'm not quire sure about what Partner Managed Tracking Code is used for, in functional terms. Ha, also I had an idea that could be contributed: to not show alternatives to developers. A simple "bypassAtc=true" parameter in the URL should do the trick, **to be removed in production**. Actually "bypassAtc=true" to add in a (general?) properties file, could be contributed and documented in OFBiz Business Setup. Thanks Jacques > -David > > > On Feb 24, 2011, at 12:27 PM, BJ Freeman wrote: > >> I have been using blackbox, whitebox, greybox testing for years. >> you start at the low level routines and test them and then use risk analysis to evaluate the effect of changing that module. >> then when you use that module int he next level up you have confident your building on solid ground. so by the time you get to >> the top you have a confidence level that you have a solid application to present to the client. >> the other thing is generated automatic test building with reporting. >> the goal is to reduce man hours in maintaining code. >> >> >> ========================= >> BJ Freeman >> Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52> >> Specialtymarket.com <http://www.specialtymarket.com/> >> Systems Integrator-- Glad to Assist >> >> Chat Y! messenger: bjfr33man >> >> Jacques Le Roux sent the following on 2/24/2011 9:51 AM: >> >> Hi, >>> >>> I think we miss something like http://www.bingocardcreator.com/abingo >>> >>> I will work on one for a customer, and would like to contribute, not >>> sure I will be able to... >>> >>> I will use/extend at least >>> >>> * org.ofbiz.marketing.tracking >>> * TrackingCode >>> * TrackingCodeType >>> * TrackingCodeVisit >>> * for org.ofbiz.webapp.visit >>> * Visit >>> * Visitor >>> >>> Just to share, in case you have already experimented in OFBiz... >>> >>> Jacques >>> >>> > |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |