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

Can Gen-AI understand Payments?

When it comes to rolling out updates to large complex banking systems, things can get messy quickly. Of course, the holy grail is to have each subsystem work well independently and to do some form of Pact or contract testing – reducing the complex and painful integration work. But nonetheless – at some point you are going to need to see if the dog and the pony can do their show together – and its generally better to do that in a way that doesn’t make millions of pounds of transactions fail – in a highly public manner, in production.  (This post is based on my recent lightning talk at  PyData London ) For the last few years, I’ve worked in the world of high value, real time and cross border payments, And one of the sticking points in bank [software] integration is message generation. A lot of time is spent dreaming up and creating those messages, then maintaining what you have just built. The world of payments runs on messages, these days they are often XML messages – and they ...

Don't be a Vogon, make it easy to access your test data!

 The beginning of the hitch-hikers guide to the galaxy leads with an alien ship about to destroy the Earth, and the aliens saying we (mankind) should have been more prepared – as a notice had been on display quite clearly – on Alpha Centauri the nearby star system, for 50 years. Seriously, people - what are you moaning about – get with the program?  The book then continues with the theme of bureaucratic rigidity and shallow interpretations of limited data. E.g. The titular guide’s description of the entire Earth is one word: “Harmless”, but after extensive review the new edition will state: “Mostly harmless”. Arthur Dent argues with the Vogons about poor data access This rings true for many software testing work, especially those with externally developed software, be that external to the team or external to the company. The same approaches that teams use to develop their locally developed usually don’t work well. This leads to a large suite of shallow tests that are usually h...

Can 'reasoning' LLMs help with recs data creation?

  A nervous tourist, glances back and forth between their phone and the street sign. They then rotate their phone 180 degrees, pauses, blink and frown. The lost traveller, flags a nearby ‘local’ (the passer-by has a dog on a lead.   “Excuse me…” she squeaks, “How may I get to Tower Hill?” “Well, that’ s a good one” ponders the dog walker, “You know…” “Yes?” queries the tourist hopefully. “Yeah…” A long pause ensues then, “Well I wouldn’t start from here” He states confidently. The tourist almost visibly deflates and starts looking for an exit. That’s often how we start off in software testing. Despite the flood of methodologies, tips on pairing, power of three-ing, backlog grooming, automating, refining and all the other … ings ) We often find ourselves having to figure out and therefore ‘test’ a piece of software by us ing it. And that’s good. Its powerful, and effective if done right. But, like our dog walker, we can sometimes find ourselves somewhere unfamiliar...