Skip to main content

Tools

Do you ever examine what you carry around with you every day, and wonder if you actually use it? For example, in my pockets I've got a 'smart' phone, wallet (credit & debit cards, cash and ID), keys, Travelcard (Oyster) and some coins. Every now and then something gets added, if its unlucky it stays. Over the years, I've noticed, that the criteria for being kept is usually convenience or enablement. That is, the items that don't get chucked or deposited somewhere about my home are usually 'tools' that make other 'things' easier like a smart-phone - I can just look up something or text someone at any time. I could just wait until I got back to my office, or see the person later but it can be easier to just act in the moment, and do it there and then.

Enablement items, are things that mean I -can- do things, that without, I'm stuck. For example: door keys. The smart phone fits into this category also, if I want to meet up with someone at short notice when I'm out, then a mobile phone is really the only practical option. Cash is another enablement device. In the same theme, I wear a watch. It enabled me to know the time, with the added convenience of a date function. The watch allows me to be less tardy, as it's a much better timekeeper than my brain.

The great inventions of our and recent times have tended to be enablement devices also. Aviation, antibiotics, motor car, personal computers, MRI, the Internet/telecommunications etc are all enablers. We can do things our ancestors couldn't, and we can do them affordably. These are all tools. They extend our reach and our capabilities.

We use tools everyday in software development. Some, like the things in my pockets, are junk, and I soon ditch them. Some I keep and reuse. But in the long run, it's the convenience and enabling tools that stick. It often seems to take me (at least) a while to notice which tools are helping, which are not helping or even hindering. Part of the problem is that some tools look like they work or at least -should- help but don't. But still I've noticed some tools or groups of tools that usually help, and in one form or another these have survived.

These include the following:

Randomness: - I have several scripts and tools that help me produce randomness in either text, numerical or event form. For example I have a script that produces a random series of UTF-8 codes, another that randomly clicks on parts of the user's graphical interface. This is an enabler. I noticed that I am not random, even when I think I am being random - I'm not. So these tools fill that gap and let me see what normally I couldn't: how a piece of software behaves with a variety of inputs [that are more diverse than I can dream up at the time]

Accurate - Record keeping: I use Blueberry TestAssistant to record everything I do on Windows. This screen recorder records the screen as well as logging all key presses. This enables me to keep accurate records of my work and findings, without much effort. This frees me to spend more time finding new issues, rather than being bogged down in manual note keeping. It also allows me to go back in time and search for issues I might have missed first time around.

Comments

Popular posts from this blog

A h̶i̶t̶c̶h̶h̶i̶k̶e̶r̶'s̶ software tester's guide to randomised testing - Part 1

Mostly Harmless, I've talked and written about randomisation as a technique in software testing several times over the last few years. It's great to see people's eyes light up when they grok the concept and its potential. 
The idea that they can create random test data on the fly and pour this into the app step back and see what happens is exciting to people looking to find new blockers on their apps path to reliability.
But it's not long before a cloud appears in their sunny demeanour and they start to conceive of the possible pitfalls. Here are a few tips on how to avert the common apparent blockers. (Part 1) Problem: I've created loads of random numbers as input data, but how will I know the answer the software returns, is correct? - Do I have to re-implement the whole app logic in my test code?
Do you remember going to the fun-fair as a kid? Or maybe you recall taking your kids now as an adult? If so then you no doubt are familiar with the height restriction -…

Software development is in the Doldrums

"Don't get off the boat."

"Seriously, never get off the boat," The instructor said, leaning forward and looking at each of us in turn.

"But surely if it's sinking..." We reply, somewhat confused and slightly incredulous. We've seen Titanic, we think to ourselves, we know how this sea survival stuff works...

"OK" He concedes, If things get really bad, "Get on the life raft if you can step-up from the boat to the life raft".

"But, But... the yacht is like 37ft long, Do we want to wait until that whole boat is lower than the life-raft? When less than 1ft of the yacht is above the surface? Meanwhile all the time the life raft is just there... floating happily alongside."

"Pretty much, yes," he said nodding.


That was about 15 years ago. Not much has changed since. The reasons are manifold. Firstly, the yacht is a decent shelter. The thin plastic of a legal minimum life-raft isn't going to protect you fro…

Betting in Testing

“I’ve completed my testing of this feature, and I think it's ready to ship”
“Are you willing to bet on that?”
No, Don't worry, I’m not going to list various ways you could test the feature better or things you might have forgotten.
Instead, I recommend you to ask yourself that question next time you believe you are finished. 
Why? It might cause you to analyse your belief more critically. We arrive at a decision usually by means of a mixture of emotion, convention and reason. Considering the question of whether the feature and the app are good enough as a bet is likely to make you use a more evidence-based approach.

Why do I think I am done here? Would I bet money/reputation on it? I have a checklist stuck to one of my screens, that I read and contemplate when I get to this point. When you have considered the options, you may decide to check some more things or ship the app. Either could be the right decision.
Then the app fails…
The next day you log on and find that the feature is b…