Tools

The Triangle Problem is a ‘classic’ from Software Testing, described in many books and training courses. This post describes the problem, links to some applications you can use to practice on and describes some nuances around the testing.

What happens if you combine a table editor with test table generation? You get a tabular random table generation tool.

This is a collation of edited older posts on Fiddler, explaining how I usee it to bypass restrictive proxy settings for tool configuration, remove headers, change browser verbs when accessing pages.

Some recommended tools from over the years.

I use a variety of screenshot tools in my work and for sharing the images, animated gifs, movies and pretty much any file, I use CloudApp.

TLDR; When you learn to manipulate the DOM with JavaScript you can create simple tools and automate from within the browser and use bookmarklets to make the code easy to execute and sync across different machines.

TLDR; Frameworks implement an abstraction layer so we don’t have to bother about it. But, what if the implementation is doing stuff you don’t want? How do you know? Find tools that let you observe inside. WebPageTest.org does that for web pages.

TLDR; Bookmarklets are an easy way to have custom javascript to support your testing that sync across browsers.

TLDR; As a simple rule, “I might not automate, if I have to create”. But I have done the opposite. I have automated when others would not. And I have waded in when others would have automated. To answer we need to question our situation and build a deeper model of our actual aims, options and capabilities.

TLDR; Even simple changes can use step by step risk based development to allow multiple releases, and will require multiple levels of testing.