Subscribe to the full blog feed using RSS
I state no “MUST”s in here, you don’t “HAVE” to know how to program to work effectively as a tester but…when you do know how to program, then you have more options. How many more? Well… “Reasons to be cheerful - one, two, three…” Reasons why I have found it useful to have programming knowledge: Speak to the developers in their own language – build relationships with the development team Different languages have their own problems and idioms – useful to know these Different languages have to make different physical decisions when implementing logical designs Implement custom test tool utilities – metric collating, defect management, data generation Use existing test tool APIs and customise your test tools e.
This review actually covers the 1st edition, and not the current 2nd edition.
I read this a long time ago - made my notes and have subsequently lost them. So I start again.
What happens when Panicky tester meets Evil Tester ? Find out in the latest episode of the exciting cartoon adventures of Evil Tester.
jWorkSheet is one of the secret tools that form part of my productivity armoury. What does it do? Why do I use it?…. Well, I work across multiple projects and if I like to be able to see which projects are taking most of my time. If I don’t track my time I get to the end of the day and go “so what did I do all day?”. If you face a similar issue then…jWorkSheet might help you.
Some notes and links on Agile Acceptance Testing. First the links. Read the online Acceptance Testing chapter from “Test Driven - Practical TDD and Acceptance TDD for Java Developers” by Lasse Koskela. Read Brian Marick’s article Series Agile Testing Directions. And now the notes: I haven’t yet read “Test Driven - Practical TDD and Acceptance TDD for Java Developers” [amazon.com][amazon.co.uk]. I have, however, read the free online chapters and I have already sent the urls of those chapters to people that I work with to introduce them to TDD and Acceptance Testing principles.
I have an unhealthy dislike of the current trend towards “fictional” example ‘based’ essays. You know the type… It was Monday and I struggled into the office out of the pouring rain and before I’d even sat down, let alone think about getting a cup of coffee and reading the latest Dilbert gag, Jane walked up to me and said “We have been looking for you for half an hour, there has been a new release, we only have 20 minutes to test all the software and we have 27000 tests to run manually - what are we going to do?
While at Stockholm for the EuroSTAR 2007 conference I managed to conduct testing on a public booth and have collated some simple lessons on Exploratory Test Documentation. I read James Bach’s post on Amateur Penetration Testing a few weeks before going off to Stockholm for the EuroSTAR 2007 conference. While there I managed to recall some of his techniques while using a few of the free test training booths provided by the Stockholm authorities in their fair city.
I’m going to introduce you to the Win32 testing tool that I use for looking at application resources, and which I used to find Mercury Screen Recorder secrets. My first tool of choice for viewing the resources in applications is called… Resource Hacker. Resource Hacker ™ is a freeware tool for viewing the resources embedded in a Win32 executable. I find this to be a handy tool for checking what hidden secrets await me if I test the application hard enough:
I made some notes when watching the Dave Allen’s Google Tech Talk on Getting Things Done. In order to help remember them I have mapped them on to Software Testing, with a few additional notes. If you haven’t watched the Google Tech Talk by Dave Allen then this post may not make as much sense now, but I think it will after you come back from watching the talk. And if you have watched it, then this post may act as a small reminder for you to.