Technical Testing

TLDR; Testing responsive web does not mean test it on lots of devices and browsers. Look at the risk associated with your technical implementation and test those. You might still have to use lots of devices and browsers. After reviewing various chrome extensions, I use the Chrome built in functionality for visualising media queries.

TLDR; We test based on risk. If we don’t identify risk we don’t test for it. Automated tools can reveal risk that our technical knowledge can not.

Who doesn’t like looking at the innards of a web page and fiddling with it?

This is a mix of ’testing notes’ and ’thoughts on how to test’ this type of app. I spent about an hour or so looking at the app, so the notes are a little scrappy. I spent about 40 mins or so tidying them up for publication, in the hope that they help someone.

I have yet to update my Windows Machine to Windows 10, and therefore haven’t experienced the joys of MS Edge. Until now. And crikey! I was surprised.

Lessons learned from Black Ops Testing - Testing a JavaScript library

On the Black Ops Testing Webinar of 11th May 2015 we tested QA Mail. You can find a write up and watch the webinar replay over on blackopstesting

You can find wireshark on line - it is a free tool.

Google Chrome continually changes, which usually means good news as new features appear. Unfortunately sometimes it means changes to our existing workflow.

This happened recently when Google released a new version of Chrome, but moved the Emulator settings.

This particular case study demonstrates how I think about testing and incorporate automation into my test approach.