Some Thoughts on Models and Definitions of Testing• Alan Richardson

• www.compendiumdev.co.uk

• blog.eviltester.com

• seleniumsimplified.com

• blog.javafortesters.com

Is Testing all about bugs?

Is Testing all about bugs?

No. Testing is all about testing.

Only nothing is all about anything else

Nothing is all about the absence of anything else.

The only thing that a thing is all about is

the thing.Testing is not all about bugs because testing is all about

testing.

Testing is all about testing.

But do we know what that means?

Do we know what testing actually is?

Create a definitionbut definitions are hard.

One thing I did...come up with a list,

because Testing is what Testers do

Model your every day testing life

Generalise that into a definition or model of testing

There were a couple of things that

stopped me creating definitions

1 - I found it hard

2- I had a limiting belief about definitions

Limiting Belief: I would be constrained

by that definition

If something doesn't fit into my definition then I'm not going to do it because its not

testing.

The way I got round that was by realising• definitions are just models,

• we can have multiple models,

• we can use multiple definitions,

• our models can be wrong,

• our models change over time

If you're worried that "I have to only do

THIS because that's what TESTING IS"

"I have to only do THIS because that's what TESTING IS"

That's just a model and a belief which

can be changed.

Have you defined testing for yourself

yet?

Here's my current working model

definition...

"Testing is building and comparing a

model of a system to the system."

"Testing is building and comparing

models of a system to the system."

What does that not cover, in what you

do?That might hint at what you value

as important for testing.

And if it does sit well for you then see

where you can take it

Definitions are supposed to

empower us and help us to think about

testing, rather than limit us

In reality it was "process", rather than "definition" that held

us back

Processes can be a direct result of

someone's strong definition or model

Sometimes they are a result of people not

having a model

So they don't know how to evaluate and change the process

against their environment

If you have model, then you can compare

it to your environment and

adjust... adjust the process or the environment or the model

How does my definition or model of

testing help me?

Strategy - Why? Why build this model?

Why compare to this part of the system?

Why... etc.

Your strategy starts with Why

Why are you building and conceptualising certain models and

why they are important to

compare?

Approach - How? How am I going to

compare this model? How am I going to

expand this model? How... etc.

Planning - Who and When? Who is going

to compare this? Who has the skills? When to compare? Who...

When... etc.

Your model, or definition, of testing can help guide you

through your general strategy/approach/

planning process

Some Thoughts on Models and

Definitions of Testing

Summary• The Name is not the Thing

• Build a model of what you do by listing your daily activities

• Creating a definition can be hard, but we can evolve it

• I describe testing as - "Testing is building and comparing models of the system to the system"

• Use other peoples' definitions to guide you to yours - what do they not cover that you value as important?

Summary• Bad processes come from thoughtless models of testing

• Definitions guide us, not constrain us, for Strategy/Approach/Plan

Alan RichardsonRead my writing and blogs at:

• www.compendiumdev.co.uk

• blog.eviltester.com

• seleniumsimplified.com

• blog.javafortesters.com

Alan RichardsonFollow me on social media:

• uk.linkedin.com/in/eviltester

• twitter.com/eviltester - @eviltester

• youtube.com/user/EviltesterVideos

• instagram.com/eviltester

Alan RichardsonBooks And Training

• "Java For Testers" - Learn to code in Java

• "Dear Evil Tester" - Enjoy your testing

• Online Training in Technical Testing, Selenium WebDriver, Java and more