Automation is a part of software testing and enables us to check more effectively. But it is not the whole of software testing.
This presentation from Agile In Covent Garden explains why.
2. Who am I?
Stephen Janaway
• Testing for the last 14 years.
• Mobile phones, mobile networks, mobile
applications, web and web services.
• Ericsson, Motorola, Nokia.
• Test Coach, Trainer and Strategist at the NET-A-
PORTER GROUP.
www.stephenjanaway.co.uk @stephenjanaway
5. What Does It Mean?
Trying the software to see if it works...
What does “try” mean?
How do you know what
“works” means?
6. It’s actually...
Questioning and investigating the software…
...to infer from it’s observed behaviour how it will
behave in the field, and to identify important problems
in the product…
...so that stakeholders can make an informed decision
on it’s suitability for release.
7. Checking vs. Testing
Testing is “the process of evaluating a product
by learning about it through experimentation,
which includes to some degree: questioning,
study, modeling, observation and inference.”
Checking is “the process of making evaluations
by applying algorithmic decision rules to
specific observations of a product.”
10. So Can Automation Replace Testing?
➔Testing is more than checking.
➔Automation scripts only do what they are
instructed to do.
You can only check what you know and
expect. Customers don’t always do what
you expect.
11. We Can’t Automate
Thought patterns
Exploratory testing
Usability
User reactions
Compatibility
Claims testing
Performance
Look and feel
Unknown behaviours
Accessibility
12. So Who Does the Automation?
➔Developers
➔Testers
➔Developers in Test (if you have to)
➔Different people focus at different levels.
Not separate ‘automation’ teams
13. My Ideal Setup
➔6 developers, 1 tester in a cross
functional team.
➔Automation primarily a ‘development’
activity.
➔A thin layer of UI tests.
➔A thick layer of unit tests.
➔Quality owned by the team.
14. Questions?
“Hang on Steve - you haven’t talked about TDD, BDD, Selenium,
Appium,....”
Stephen Janaway
@stephenjanaway
www.stephenjanaway.co.uk
Notes de l'éditeur
I’ve been working in the mobile world for 14 years.
Tested mobile networks, mobile devices and applications, web and web services.
Worked for Nokia, Ericsson, Motorola.
Currently at NAP - global ecomm fashion retailing group with 3 brands. High tech, very exciting. Approx 40 testers currently in IT team of 300.
I blog regularly and here’s my website link.
You can follow me on Twitter.
Sometime we talk about what’s important to us in the software testing world.
Other times we interview other people.
If you want to be involved then let me know :)
So - what is Testing?
Let’s get this out of the way first. Testing does not equal quality. You can’t test quality into a product.
Nokia Quality Gate example.
Don’t throw work at testers.
Testers are not responsible for quality. I hate the term QA.
Testers not being the quality police either.
Everyone is.
Now we’ve got that out of the way then let’s talk about what testing is.
Here’s what most people think it is. But…...
This is what testing actually is.
So it’s about Questions - Identification - Suitability
We can ask these questions using automation or manually. More later.
It’s also important to define what Testing is. And what it is not. So first - some wordy definitions.
Which mean….
I find the testing pyramid a good way to describe what a team should do. Note that there’s automation and manual testing shown. That’s important.
Mention - what’s done at each level. Who does testing at each level.
Smooth flow.
So - there was more automation on that last slide than manual testing?
But automation is excellent for repeatable tests. It’s excellent for test data setup. Its excellent for acceptance testing.
We Need Both Manual Testing and Automation