TesterHQ - The Evil Tester Blog Aggregator

Mar 9, 2008 - 3 minute read - Evil Tester UAT

A generalised model for User Acceptance Testing (UAT)

In a previous post I discussed how I managed to do UAT badly in the past. Now I will discuss a generalised model formed from those (and other) experiences, which should allow me to make fewer UAT mistakes in the future. The problem was, I looked at the wrong words I think my fundamental problem occurred because I read “USER acceptance TESTING” when I should have read “user ACCEPTANCE testing”.

Mar 7, 2008 - 4 minute read - Evil Tester UAT

How to do software User Acceptance Testing (UAT) really badly

I’ve made a lot of mistakes over the years when testing. I try not to make each mistake more than once - which usually means any future mistakes require more creativity or stupidity on my part. So I will describe some of the mistakes I (and other people I have known) have made when doing UAT so you can use more creativity (or more stupidity - you get to choose) when approaching UAT in the future.

Mar 5, 2008 - 2 minute read - Agile Evil Tester

Eclipse plugins to ease Test Driven Development Mistakes

Previously I described how I made some TDD mistakes and fixed them by tracking them. And now to help me maintain my good behaviour and reduce my recidivism rate, I install some eclipse plugins: Emma, FindBugs, PMD and mousefeed. The open source Emma code coverage tool provides a pretty good job of identifying my code coverage. I have had incidents where Emma and I disagreed on the extent of code coverage, but I find the Emma view of my code absolutely vital to double check that I haven’t relapsed into “Rewrite instead of Refactor” mode and allows me to engage in my preferred “Check code coverage after refactor” behaviour.

Mar 4, 2008 - 2 minute read - Agile Evil Tester

A simple explanation of dependency injection

For the longest time I didn’t know what dependency injection meant - anytime I looked it up I glazed over thinking it really complicated. I only recently found out while learning TDD that I can describe dependency injection in terms of - pass an object in as a parameter instead of instantiating it in the class or method. But as soon as I learn this, I encounter a presentation that would have taught me this anyway - so I pass it on now in case you don’t know what dependency injection refers to.

Mar 1, 2008 - 2 minute read - Agile Evil Tester

Tracking TDD mistakes so I can fix them

Previously I made some TDD mistakes. So to fix them. I tracked them. I tracked the mistakes by creating an index card that listed the ‘bad’ things on one side, and the ‘good’ things on the other side. Then noted when I did the bad things, and when I did the good things. The writing of these statements seems important. So if we have a look at the card…

Feb 28, 2008 - 3 minute read - Agile Evil Tester

My Novice Mistakes in Test Driven Development

Since I generally present myself as a tester, coupled with my relatively novice status when coding in Java using TDD. I don’t mind writing up my TDD mistakes here. My basic set of mistakes The basic set of mistakes I have made recently consists of: Class Names start with an upper case letter Doing refactoring when I don’t Not checking my code coverage Not doing a review step Not doing an update after a commit So those mistakes in more detail:

Feb 20, 2008 - 4 minute read - Evil Tester Lean

Some Notes on Software Testing Waste - my lean perspective

One key ‘lean’, or ‘TPS’, concept covers ‘muda’, or waste. Over my years in Software Testing I have tried to make my testing processes more ‘Agile’ or ‘Lean’, but when I started I didn’t have the concept of ‘muda’, I just had the knowledge that things weren’t working, so I changed them and got rid of the things that I thought added no, or little value. Now that I know a little about Agile and a little about Lean, I can try to apply the concepts of ‘muda’ to testing.

Feb 18, 2008 - 5 minute read - Book Reviews CompendiumDev

Book Review: Software Testing Fundamentals by Marnie L. Hutcheson

Driven to provide ways of providing better information to her customers, Marnie Hutcheson has identified techniques for identifying and structuring her test scope to allow her to provide estimates, negotiate and agree a prioritised scope, and report progress against that. All of which sounds like the makings of a great book. [amazon.com][amazon.co.uk] But I have to say that it ended up as a strange little book. Unfortunately a lot of the book read like padding so I ended up skipping useful information and backtracking, and I did get confused by the book at times.

Feb 17, 2008 - 1 minute read - CompendiumDev Education

5 acronyms that software testers should learn from

I count Google video as one of, if not the, best self-training resources currently available to me. So on Google video here are 5 acronyms that you can use for your self education as a tester: AAFTT, BBST, GTAC, SHMOOCON, OWASP. AAFTT Agile Alliance Functional Testing Tools visioning workshop BBST Black Box Software Testing Course GTAC Google Test Automation Conference SHMOOCON The Shmoo Group’s Software Hacking Conference

Feb 11, 2008 - 3 minute read - Evil Tester Techniques

Notes on 'abstraction' and 'equivalence classes' in Software Testing

Abstractions can put your testing in danger if you don’t handle them correctly. So some hints and tips on handling the abstraction known as an ‘equivalence class’ may help. I use the word ‘abstraction’ (wikipedia definition) a lot when I discuss Software Testing. ‘Abstraction’ underpins so much of my modelling approach. I recently read Glanville Williams’ concise description of abstraction, as quoted in Hayakawa’s “Symbol, Status and Personality” [amazon.com][amazon.co.uk][books.google].