TesterHQ - The Evil Tester Blog Aggregator

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].

Feb 10, 2008 - 1 minute read - Evil Tester Rants

If a demand for testing certification exists then why don'tUniversities meet that demand?

Should ISEB even run a certification scheme? If Industry really does have a demand for it then perhaps ISEB’s role should involve collating the Industry needs and passing them on to the Universities to provide the necessary certification mechanism. Academia generally seems to ‘get’ certification. The Games industry has managed to get “Games Development” recognised as a degree level subject. If industry wants a certification then should academia meet that need?

Feb 8, 2008 - 4 minute read - Evil Tester Rants

ISEB, and the train that won't stop going

What an easy target ISEB makes, it comes in for a lot of criticism. And I think it should. To an outsider like myself the certification train looks like a money spinning exercise, why else keep cranking out certification levels? I wonder what they could do to change my perception… ISEB currently promotes 4 testing certification levels - the Foundation, Intermediate, Practitioner Test Manager and Practitioner Test Analyst. I find it too easy to believe that ISEB has money making intentions rather than the ‘profession’s best intentions to hand.

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

My notes on how to study for ISEB foundation

While trawling through my hard drive on a deletion frenzy, I found my old notes on what I did to pass the ISEB foundation exam. Bear in mind that I made these notes in 2003 and the ISEB syllabus has moved on since. But I have updated all the links and someone might find my updated notes useful. Original Notes - with up to date links. Hints and tips The questions get written from the syllabus - know the syllabus The definitions come from the glossary - forget what you think you know if you want to pass - learn the definitions in the glossary The techniques come from the BS7925, read and understand this At the end of your study, if you feel like doing something adventurous then read the practitioner syllabus for extra depth Mandatory Study the syllabus in conjunction with the Glossary of terms used in software testing and the BS7925 standard Build a mind map or set of study notes for the syllabus to summarise what you think important Check your understanding and notes against the definitions in the glossary and the standards Learn some memory techniques and general exam techniques.

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

Book Review: Testing Computer Software by Kaner, Falk, Nguyen

I thought I’d read this again for review purposes. I didn’t expect it to surprise me, but it did, massively. One of the most realistic testing books available, starting almost immediately in the preface discussion “Its not done by the book”. The book sets out its target audience as simply “the person doing the testing” [amazon.com][amazon.co.uk] ”…find and flag problems in a product, in the service of improving its quality. your reports of unreliability in the human-computer system are appropriate and important…You are one of few who will examine the full product in detail before it is shipped.