{"id":16431,"date":"2019-11-13T17:32:01","date_gmt":"2019-11-13T17:32:01","guid":{"rendered":"https:\/\/applitools.com\/blog\/?p=6431"},"modified":"2023-01-26T12:14:09","modified_gmt":"2023-01-26T20:14:09","slug":"validating-multiple-variations","status":"publish","type":"post","link":"https:\/\/applitools.com\/blog\/validating-multiple-variations\/","title":{"rendered":"A\/B Testing: Validating Multiple Variations"},"content":{"rendered":"

When you have multiple variations of your app, how do you automate the process to validate each variation?<\/p>\n

A\/B testing is a technique used to compare multiple experimental variations of the same application to determine which one is more effective with users. You typically run A\/B tests to get statistically valid measures of effectiveness. But, do you know why one version is better than the other? It could be that one contains a defect.<\/p>\n

Let’s say we have two variations \u2013 Variation A and Variation B; and Variation B did much better than Variation A. We’d assume that’s because our users really liked Variation B.<\/p>\n

\"\"<\/p>\n

But what if Variation A had a serious bug that prevented many users from converting?<\/p>\n

The problem is that many teams don’t automate tests to validate multiple variations because it’s “throw away” code. You’re not entirely sure which variation you’ll get each time the test runs.<\/p>\n

And if you did write test automation, you may need a bunch of conditional logic in your test code to handle both variations.<\/p>\n

What if instead of writing and maintaining all of this code, you used visual testing instead? Would that make things easier?<\/p>\n

Yes, it certainly would! You could write a single test, and instead of coding all of the differences between the two variations, you could simply do the visual check and provide photos of both variations.  That way, if either one of the variations comes up and there are no bugs, the test will pass. Visual testing simplifies the task of validating multiple variations of your application.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Let’s try this on a real site.<\/h3>\n

Here’s a website that has two variations.<\/a><\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

There are differences in color as well as structure. If we wanted to automate this using visual testing, we could do so and cover both variations. Let’s look at the code.<\/p>\n