Thursday, February 28, 2019

Disabling JavaScript using Selenium


Contents:

1) Introduction
2) Why is Javascript-disabled page worth testing?
3) Chrome
4) Firefox

1. Introduction


Some days ago I was looking for an easy way to disable JavaScript using chromedriver. It turned out to be surprisingly hard and once again I had to find proper Chrome preference in the Chromium source code.  If you ever wonder how to do something with your Chrome using Selenium I recommend my own Browser Capabilities explained post which has a lot of examples and links where to look for.  

2) Why is Javascript-disabled page worth testing?

Before we move on to Java demo let's wonder for a while: why do people disable JavaScript?

a) Speed & Bandwidth

Using Internet with an old computer and a slow connection is incredibly frustrating these days. You can try to throttle bandwidth in your Chrome via Developer tools and try it yourself... For your responsibility.

b) Usability & Accessibility

Relying on javascript does not automatically mean the page is not accessible, although it makes it significantly harder for disabled people. Imagine that content blind person wants to find is hidden behind three JS-invoked actions. Would it be possible to access? Yes. Would it be usable? No.

c) Security & Privacy

Any website can use JavaScript to gather information about things you do (or did) during your browsing session and upload them to an external server. That's enough reason for privacy-concerned people to disable it. JavaScript can also be used for XSS attacks.

So, from the company perspective: why should we care and test our website with JavaScript disabled?

a) SEO

Perhaps the most important reason. If large chunks of your website rely on pure JavaScript chances are search-engines will be ignoring it.

b) Clients who disable JavaScript

The number of people who disable JS is small... but is it negligent? Even if it's only 1% of our business can we ignore that?

c) Testing for graceful degradation of JavaScript

Even if we decide that we don't support our site with JS disabled we should gracefully handle it. We can't leave our users with a forever loading blank site. We have to present information that we don't support JS.

3) Chrome

As I mentioned above I wasn't able to disable JavaScript in Chrome using any obvious methods (like setters etc.). I had to pass a map of preferences with magic profile.managed_default_content_settings.javascript key. I assume that the code is easy to understand. For details please take a look at my Desired Capabilities explained post

The test is pretty straightforward. We go to main Facebook page and wait until URL is updated with ?_fb_noscript=1. This is how FB detects users who have disabled JS.

I'm using FluentLenium syntax. 

4) Firefox

Firefox setup is much easier. Only one flag has to be set to false: javascript.enabled.

The complete code can be found on my GitHub project.

Image credit: tomthedev

No comments:

Post a Comment