#Casperjs benchmark testing code

So instead, let's teach CasperJS to just skip those external files altogether when running tests. In fact, it's unlikely that you want your test suite mucking up your analytics data or your customer insights information. That, when you're running tests, you probably really don't need. This requires that your browser make and extra HTTP request to retrieve that file. Generally, when your browser encounters one of those JavaScript tracking codes the embedded JavaScript either directly references, or ultimately ends up including, a. Those milliseconds start to add up, and can increase the amount of time it takes for your test suite to run.

#Casperjs benchmark testing code

But, when you're using a tool like CasperJS to perform testing on your site, it's not uncommon for a single test run to visit tens, or even hundreds of pages-and have to load that JS tracking code on every one. We're usually talking about milliseconds.

If used correctly, the performance hit seen by the end-user should be pretty minimal. In most cases it's probably not that big of a deal. You know all those JavaScript tracking codes that get added to the footer of every page on your site? Google Analytics is the classical example, but there are tons of others out there.