2nd day of Ally(Accessibility) Testing

Today’s task – Use a tool like WAVE to scan a web page for accessibility problems.

I have used Accessibility scanner for Android to scan for the accessibility issues for each and every screen and these are the links which I found interesting today.

  1. A11ycasts with Rob Dodson – A youtube playlist which has a lot of info on Accessibility
  2. A few speaker deck links – a) Accessibility @ scale  b) Accessibility is more than just supporting screenreaders
  3. Thanks to Big Nerd Ranch for this – Making Accessibility More Accessible, Part 1 and Making Accessibility More Accessible, Part 2

30 Days of Accessibility testing – I will be concentrating on Mobile accessibility.

Starting today I will be concentrating on this https://dojo.ministryoftesting.com/lessons/30-days-of-accessibility-testing and keeping mobile in mind. 🙂

Anybody doing the same?

Learnings for First day: Learn about the diversity of disabilities and the effects of aging.

  1. The diversity of web users – Auditory, Cognitive and neurological, Physical, Speech and Visual. Hmm, so many to look for. For aging follow the WAI’s Web Content Accessibility Guidelines which covers all.
  2. Thanks to Ministry of testing DOJO for this curated list of accessibility tools – https://dojo.ministryoftesting.com/lessons/accessibility-apps
  3. Accessibility scanner for Android, a tool that suggests accessibility improvements for Android apps without requiring technical skills. Just open the app you want to scan, then tap the Accessibility Scanner button to find items in the app that might benefit from accessibility improvements. You can use this app to suggest changes to developers or to make changes yourself.


Muir is a mobile browser testing app without all the strings of cloud based suites. Simply download the desktop app, install the client on your mobile devices, and get to work.

Download link: http://labs.iqfoundry.com/muir/release/Muir.exe


A Brief….

Top 20 Software Testing Tweeps

According to Twitter co-founder Biz Stone, Twitter now has 105,779,710 registered users—and is adding 300,000 new users a day. Attempting to weed through all of the fluff can be daunting! So, if you’re interested in jumping into the Twittersphere or are just looking to follow the leading journalists and thinkers in software testing today, check out our “Top 20 Software Testing Tweeps” list below (in no particular order)!

  1. James Bach – @jamesmarcusbach
  2. Michael Bolton – @michaelbolton
  3. Testing At The Edge Of Chaos (Matt Heusser) — @mheusser
  4. Tester Tested! (Pradeep Soundararajan) – @testertested
  5. StickyMinds.com (Better Software Mag) — @StickyMinds
  6. SearchSoftwareQuality.com (Yvette Francino) — @yvettef or @SoftwareTestTT
  7. Google Testing Blog (Copeland/Whittaker) – @copelandpatrick or @googletesting
  8. Testy Redhead (Lanette  Creamer) – @lanettecream
  9. Test Obsessed (Elizabeth Hendrickson) — @testobsessed
  10. SD Times — @sdtimes
  11. Jon Bach – @jbtestpilot
  12. Software Test & Performance Mag –- @STPCollab
  13. Software Testing Club (Rosie Sherry) — @rosiesherry or @testingclub
  14. Lisa Crispin — @lisacrispin
  15. Fred Beringer — @fredberinger
  16. uTest (shameless plug! ;-) ) — @uTest
  17. Weekend Testing (Santhosh/Parimala/Ajay) – @weekendtesting or
  18. Santhosh Tuppad — @santhoshst
  19. Ajay Balamurugadas — @ajay184f
  20. Parimala Shankariah — @curioustester

Update! Thanks for everyone’s recommendations. Here are a few we missed: @sbarber@QualityFrog,@dailytestingtip@sdelesie@Rob_Lambert@chris_mcmahon@hexawise@marlenac@shrinik,@sbharath1012@sellib@TestingNews.

Please feel free to add any active Tweeps you think we may have missed in the comments! We welcome your recommendations.

Courtesy: Utest


In this article I want to tell you about my first experience with Android WebDriver.

And so begin ….

Here is a step-by-step instruction for using Android WebDriver. Well let’s follow it.

Steps to successful using of Android WebDriver :

1)      Download  Android SDK.

2)      Create emulator using AVD Manager or via console (whatever you like)

3)      Start emulator

Now it’s time to write our first test, but it not so simple as would like. We have two ways to run the tests:

1)      Using the remote server

2)      Using the Android test framework

We can read more about those methods in our instruction.

For myself, I chose first method (Using the remote server), because tests will be run in different browsers, not just on Android. And so begin the implementation:

1)      First download Android Server apk from here

2)      Get the serial ID of device

adb devices

3)      Install the application(Android Server) on device

adb -s <serialId> -e install -r  android-server.apk

4)      Start the Android WebDriver

adb -s <serialId> shell am start -a android.intent.action.MAIN -n org.openqa.selenium.android.app/.MainActivity

5)      Setup the port forwarding in order to forward traffic from the host machine to the emulator.

adb -s <serialId> forward tcp:8080 tcp:8080

It seems to be simply and smoothly. It’s time to our test. I decided not to reinvent the wheel to check the success of the setup and again follows to instructions (see here)

When I clicked button Run, I saw google.com main page on a virtual device, and then nothing, our test hangs. For fun, tried to run through FirefoxDriver, as expected, everything works.

I decided to change version of the Android emulator, after that I again found some nasty surprises:

1)  As we being warned in our instructions, emulator has a bug in the Gingerbread. So there I was not able to try anything, because apk always crashed, when I running tests (despite the fact, that this is the most popular version of Android for the moment)

2)  Honeycomb (3.x), I used at the beginning and I not able run my test with success

3)  To try Froyo (2.2) need to download an older version apk, because it is simply not supported in latest versions. And it again a bit annoying, because need to spent time to configure ant to run tests on all versions. So I decided not to touch Froyo for now

4)  There is Ice Cream Sandwich (4.0.x) in the end. There was a problem too. I was unable to communicate with the virtual device using adb (received error message:” error: protocol fault”).


Of course the ability to automate testing of Web applications through the Android tempting. But my first experience is not let me seriously perceive Android WebDriver. I’ll hope for the best.

PS. If someone has an idea why I did not succeed, accomplish your goal in the comments 🙂

Courtesy: http://www.intexsoft.com/blog/item/144-android-webdriver-one-history.html