TesterHQ - The Evil Tester Blog Aggregator

Mar 30, 2008 - 2 minute read - Evil Tester Tools

RegexBuddy meets RegexGuru

Much as I appreciate the conciseness, usefulness and elegance of Regular Expressions; I just don’t use them enough to have mastered them or keep the rules in my memory. I used to rely on “Mastering Regular Expressions”, which I still find very useful. But I registered RegexBuddy about a year ago when I found myself struggling with a regular expression for about an hour. 2 minutes after I had bought and downloaded RegexBuddy I managed to create the desired regex.

Mar 28, 2008 - 3 minute read - Evil Tester Rants

We don't need no stinkin' passion!

“Me too. Me too. Me too.” That sums up my reaction to Antony Marcano’s TestingReflections post on interviewing testers that just don’t ‘come up to scratch’. Those testers we interview who claim to have a passion for testing but don’t exhibit said passion. I’ve gone through the same as Antony and have no words of advice to offer him, because he probably does the stuff I mention in this post already.

Mar 27, 2008 - 6 minute read - Book Reviews CompendiumDev

Book Review: The Craft of Software Testing by Brian Marick

When the author, Brian Marick, describes his own book as “somewhat dated…written in a less spritely manner than I’d use today… this is not how I do things today”, that doesn’t really add up to a particularly motivating sales pitch for the book. My copy has the appearance of “printed on demand” - which has resulted in a slightly wonky copy, but at least the book remains in print. I think it that anyone reading the book will see how Brian ended up as one of the signatories of the Agile Manifesto.

Mar 18, 2008 - 1 minute read - Books Evil Tester

Some Recent Software Testing Book Reviews

I put my Software Testing Book reviews directly on my Compendium Developments site. So if you only read Evil Tester then you missed out on Reviews of: Effective Software Testing by Elfriede Dustin, Software Testing Fundamentals by Marnie Hutcheson, Testing Computer Software by Kaner, Falk, Nguyen, Systematic Software Testing by Craig and Jaskeil, Software Testing by Ron Patton.

Mar 17, 2008 - 5 minute read - Books Evil Tester

Book Review: Beyond Bullet Points by Cliff Atkinson

I have done a lot of public talks over the years (but never enough to consider myself ‘good’ at it). Over the years I have adopted numerous approaches to constructing the presentation and of constructing the slides. You can see some of my worst slides. This slide pack seems better. But overall these slides seem far too wordy and unfocussed. I wanted to see what Beyond Bullet Points (BBP) could help me do.

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.