Responsive Web Design Testing and Automation of Responsive Regression Testing


(mir saadat) #1

Thought of starting something which i did not find in CLUB.

Responsive Web Design Testing and Automation of Responsive Regression Testing.
How do you test a responsive website? What are the challenges involved in testing websites in different devices? How is testing a website on a desktop monitor different from testing on a handheld device such as a mobile phone? What tools can we use to test responsive websites?

Plus

Found this Test Framework which talks about the Layout (responsive web design Testing automation)
Galen is a test framework originally designed for testing layout of web applications but is also a great tool for functional testing. (http://galenframework.com)

Please share your experiences on these topics


(Matt) #2

Man. This is hard. I worked on a project where we had to do this. I’d say that the problem is closely related to cross browser testing, as you care about mobile / tablet browsers.

Doing this manually is not an option I would ever choose. Automation is going to really pay off, as these tests are very similar to one another but with a few tweaks, and your manual testers are going to get very bored doing them.

First off, you can use tools like Browserstack or Sauce Labs to simulate mobile phone/tablet browsers. It’ll be a lot cheaper using those than maintaining lots of different browsers yourself.

We defined our test cases into three different form factors - desktop, tablet, and phone. The responsive design changed at certain resolution boundaries. So we did functional tests at all three main resolutions. We changed the browser resolution, and ran our standard functional suite against them.

I’d use techniques like a browser matrix and identify your most important audiences that you want to target. If you currently have a live website, grab the details from Google Analytics (or similar) and work out what you care about. Perhaps few people visit your website on a tablet, so you care less about it…?

How often you want to do this is really up to you. I’d probably do a normal functional suite every deploy to QA, and then more irregularly (perhaps every release candidate) do a full cross browser & responsive test. As far as the testing pyramid is concerned, resolution & cross browser testing is higher up than the acceptance suite - it takes much longer and you’re not going to discover as many critical bugs.


(mir saadat) #3

Thanks for the reply Matt, we have used sauce labs and browser stacks for cross browser testing and different mobiles/tables etc. It really helped and even as you pointed out manual testers get bored doing it.

Thanks again for your valuable inputs and real time experience.


(rakesh ) #4

Hi Matt & Mir,
I hope you guys found success with RWD testing using sauce and other platforms. I would like to get your thoughts on testing RWD sites on real mobile devices?

Thanks