Skip to main content

The Fallacy of Omniscience by Proximity



I was reading about President Hollande's apparently complex love life, and a journalist who used to live in France was asked his opinion on the issue. He responded that although he used to live there, those who wanted his opinion assumed that this meant he knew all about the issue and had a groundbreaking insight into the story. 

Turns out, he hadn't lived in France for years, so was about as wise as the rest of us. Those seeking his opinion had fallen for the wonderfully named:


'The Fallacy of Omniscience by Proximity'

It means (in a general sense) you are/used to be in close proximity to subject, so it stands to reason you must know all about it right?

After pondering this lovely phrase for a while, I realised it has a relevance for us testers. 

Firstly, often, testers are a respected oracle for a domain and/or an application. You know that person who 'has been here forever and knows everything about X.' That is literally not true, and reinforces that all oracles for testing (even our fellow testers) are fallible. I still see (and participate in) this behaviour often.

Secondly, when you have tested an application I have found that it is assumed you have knowledge of every major and minor path through the functionality. As a tester, consider this statement, perhaps by another product stakeholder:


'Well, you tested it! Why didn't you know that when I do Y it triggers behaviour Z?!?'

We know of the impossibility of complete testing (our stakeholders may not) but there can be an assumption that testing brings 'complete knowledge' of an application. This is a classic example of the fallacy in question, and has its roots in a fundamental misunderstanding about the purpose of testing that still permeates today.

For now, I'm delighted to find a new way to describe a problem I ponder often.

Comments

Popular posts from this blog

Testers Guide to Myths of Unit Testing

One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively.

Also, I want to do a talk about it, so I figured I would test the premise, see if potential audiences were into it. I put this on Twitter:
Working on a talk about what testers might believe about unit #testing & how we interact with developers creating unit tests. Any challenges/additions for my list below? #development#agilepic.twitter.com/4oT5HE4qs3 — Ash Winter (@northern_tester) December 19, 201730 replies with ideas tends to indicate that people might be into it. 
The ListI thought, as my final blog of 2017, I would provide a super useful list of the myths and legends we as testers might believe about unit testing:
That developer…

Wheel of Testing Part 3 - Applications

I've only had to quit two jobs to finally find the time to finish this blog series. Winning at life. If you need reminders (like I did) check out Part 1 and Part 2 before reading on...

After the first two blogs regarding the Wheel of Testing, I was delighted to receive a few requests for the wheel itself, which got me thinking about applications of it, beyond what its original intent was, which I've explored in detail in part 1 of this series of intermittent blogs. Most models need a little air time to show their value, in software development we crank out models all the time, but I'm not sure how many get used. I am inspired by models such as the "Heuristic Test Strategy Model" by James Marcus Bach, as I have used it and seen the benefits it has brought for my clients, particularly the ability to ask questions. So, I wanted to create a model which has a number of use cases, both real and imagined:

Helping to unlocking a career in testing which may be stuck

It is no…

Why do Testers become Scrum Masters?

It was late and I was stuck on a train, so I pondered on the question of why do testers often (in my experience) become Scrum Masters. Its a very dear question to me, as its been a big part of my career journey In fact, I've been there and back again. Tester to supposed-to-be-testing-but-being-a-Scrum-Master to Scrum Master, back to Tester and very happy thank you.

I encapsulated my reasoning in the following:
Long train delay, decided to think about a thing. :) Why do testers (in my world anyway) often become Scrum Masters? #testing#agile#scrumpic.twitter.com/FGGXFiBGz1 — Ash Winter (@northern_tester) February 13, 2018The tweet got a lot of traction, and generated a couple of interesting threads which made me think.
Great list. Personally I think that as a scrum master I can add even more towards the goal of quality. — Christian Kram (@chr_kram) February 13, 2018 Perhaps part of the reason for the transition is a growing appreciation of where quality has its roots? If testing i…