Back in 2004, Danny Faught and I collaborated on an article for Better Software, about how to use tools when you have no budget, or people will not let you install anything. The article was entitled “Being Resourceful when your hands are tied”.
I went through a process of self-evaluation to understand better how I test, how I think about testing and the tools I use. This paper discusses the tool strategies I use and is an introduction to the world of free and cheap tools available to help us do testing.
The tools in action The sessions in action A related stickyminds.com paper is Being Resourceful When Your Hands are Tied which was co-written with Danny Faught.
The January 2004 edition of Professional Tester contains an article about self education and practise. The article was entitled “Help Yourself”.
Requirements are a tricky business.
As testers, we know that a lot of the ‘finished’ requirements we see require investigation on our part to find out ‘how’ we can actually test them and to get to the core of what the requirement actually means.
We also know that the development process is notorious for claiming that users changed their requirements, and kept changing them as the development process continued. So structured processes prefer to avoid change, and extreme processes embrace change.
Wherein the TOTE (Test Operate Test Exit) model is used to explore the nature of feedback and abstraction of test phases
In 1960, George Miller proposed a model of Goal driven behavior which he titled T.O.T.E (Test operate test exit). This essay, maps the T.O.T.E model to Software Testing. Fig 1: The TOTE Model as a Graph
My understanding of TOTE is very simple. For this model to be valid we have to accept that the stimulus behind behavior is the achievement of a Goal.
Find it on [amazon.uk] [amazon.com]
Lessons Learned in Software Testing contains lots of short essays which are well worth reading and thinking about.
This is a fantastic phrase, it has been popular and it has worked; testing now starts earlier and testing has a higher profile than ever before, but despite all that, it isn’t what we meant or even what we really needed.
Back in the depths of despair that was the Software Crisis. Testers managed to bellow a rallying cry “Testing should start early!” Testers could be found picketing management and development meetings with ‘V-model’ placards and T-shirts with ‘cost of defect’ bar charts emblazoned.
…Meyerhold’s bio-mechanical actor said, “I make these movements because I know that when I make them what I want to do can most easily and directly be done.” 
All quotations in this article are from “The Actor’s Ways and Means”, Michael Redgrave, William Heinemann Ltd, 1953
More for amusement than a desire to educate myself further in the ways of testing, I picked up a copy of Michael Redgrave’s lectures on the actor’s craft “The Actor’s Ways and Means”.
There are many universal statements that a tester will come across in the course of their career, some true “Testing can only prove the presence of faults and not their absence”, and some false “Developers must not test their own code”
Such statements may well be paraphrased quotes, the original source may not be known or presented, and the quote may be taken out of its original context. But they will be one common form of the phrase that exists in the industry’s shared consciousness.
Test Conditions are statements of compliance which testing will demonstrate to be either true or false. These are (in effect) test requirements.
Conditions serve different purposes. Some conditions will act as the audit reason for a particular test case e.g. The user must be able to create a flight. The tester will create a test which creates a flight, obviously there are more attributes to this case than this - what type of flight, what type of user, fully booked, partially booked, etc.