unable to connect to mozilla geckodriver watir

See Google Analytics official documentation's ' Exclude internal traffic' section for details. Some of these are just general approaches for excluding certain traffic from Google Analytics side, while some may involve updating Selenium test code explicitly.Ī custom filter on certain IP address/range or ISP can be created in order to filter out internal traffic. Another solution is to avoid executing Google Analytics snippet if the site is deployed on testing servers.Īnyway, if it is really necessary to use Selenium against production for some reason, Here are few solutions which might help exclude internal traffic from Google Analytics.

One approach would be using a different Google Analytics token from production, so the analytics data get separated out. In this case, when Selenium is used only against testing environment, it would be relatively easy to exclude its traffic. If such traffic is from site developers' own Selenium WebDriver tests, then the question becomes 'Why Selenium tests were run against production'? Normally production servers only require some manual exploratory/smoke testing, instead of intensive automated testing to mess around live databases and slow down the servers.

some people are running Selenium WebDriver against the website, then there isn't much can be done, unless the IP/ISP or User Agent can be uniquely identified. If such traffic comes from unknown sources, i.e.

However, first things first, before talking about how to exclude such traffic, the question would be 'why such traffic exists?'. For sites being tested by automated UI testing frameworks like Selenium WebDriver or Watir, developers may find it useful to exclude internal automated testing traffic from Google Analytics.

Unable to connect to mozilla geckodriver watir