Skip to main content

The Obscure One

Heraclitus wrote these words 2500 years ago: "Ever-newer waters flow on those who step into the same rivers." or paraphrased in more colloquial English: You never stand in the same river twice.


Known as the "The obscure one" to some of his contemporaries, he was known to make statements that were considered paradoxical and sometimes unhelpfully contradictory. I don't know about you  - but sometimes when discussing testing feedback - I feel like I am channeling the ghost of Heraclitus.

His comments regarding walking through rivers are an apt description of our work with software and its versioning. Do we ever play with the same app twice? On a trivial level, we do. When we widen our view we can see that the waters have moved on.

For example, 

  • The time has changed. It may even have gone back to a previous date and time. 
  • The code is probably located in a different memory location. 
  • The app and operating system are probably facing different types of automated attack from various pieces of malware on the same device and across the network
  • Your typing / swiping speed has changed
  • Libraries used by the app may have been patched
  • The OS has probably been patched
  • Your training/test datasets' random split is slightly different
  • Other programs or apps have probably been patched.

Etc.

Add to this the changes in your test tools and test data, then an application some might naively see as the 'same version', can behave quite differently. 

So when someone says a test is flaky or the app is flaky, think about the river of change that's running through your app. Smile to yourself, and know that people have been explaining what you are about to explain for at least 2500 years. 

Comments

Popular posts from this blog

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. Testing is gambling with your time to find information about the app. 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

The gamification of Software Testing

A while back, I sat in on a planning meeting. Many planning meetings slide awkwardly into a sort of ad-hoc technical analysis discussion, and this was no exception. With a little prompting, the team started to draw up what they wanted to build on a whiteboard. The picture spoke its thousand words, and I could feel that the team now understood what needed to be done. The right questions were being asked, and initial development guesstimates were approaching common sense levels. The discussion came around to testing, skipping over how they might test the feature, the team focused immediately on how long testing would take. When probed as to how the testing would be performed? How we might find out what the team did wrong? Confused faces stared back at me. During our ensuing chat, I realised that they had been using BDD scenarios [only] as a metric of what testing needs to be done and when they are ready to ship. (Now I knew why I was hired to help) There is nothing wrong with c

DevOps and Software Testing.

Most of my recent work has been with DevOps teams. While in one sense DevOps is another evolution in software development. It also introduces some new skill requirements and responsibilities into the daily routine of a tester. These diagrams tend to confuse people, hence the video... I've created a short video to highlight some of these changes and the opportunities they bring. It's not an exhaustive view of DevOps but it gives a highlight of what you could be working with. While DevOps isn't a panacea to our software development problems, I have found that empowering teams with the ability to build and use the tools they need, can rapidly improve team morale and productivity.