Rich-text Reply

Workarounds for QA automation machines

lissastreegan 12-08-15

Workarounds for QA automation machines

We have QA automation machines on our internal networks and I was wondering if there's a scalable way to exclude those machines from being served with experiments? Our team is concerned that the scripts will break when experiments are launched. Does anyone have a good way of handling this?

Brett 12-08-15
 

Re: Workarounds for QA automation machines

There are a few ways around this and it comes down to how your automated QA machines function.

Typically most of these automated QA methods have a unique user agent. I would find out what the user agent is and then write a custom javascript condition in our Audiences to prevent that user agent from being added to the experiment.

Alternatively, if no user agent is present but they share a common set of static of IP addresses, you could use IP targeting(if available to you)to prevent them from being added to the experiment that way as well.

The main idea is to find something unique about the automated QA machines that you can use to target off of. Once you identify what is unique you can use that in our Audience conditions to prevent them from being added to your experiments.
Optimizely