SlideShare a Scribd company logo
Test automation – the
bitter truth
Some unpleasant truths about “test automation”
Be a part of the show!
Ask a question or leave your feedback at:
https://www.sli.do/ using code #7346
Before we start, few
prerequisites:
Here’s a story …
What do testers imagine when they see “manual
testing”?
• Ineffective
• Boring
• Slow
• Easy to perform by anyone
• Mindless banging of keys
What do managers feel when they speak of
“manual testing”?
• “You are wasting too
much time. “
• “We have too much
testers”
• “We can easily automate
what you do.”
• “You are not reliable”
How both managers and testers react when
someone mentions “automation”?
• Totally fangirling
• We will reduce costs
• We will have more time for
“manual” testing
• I will only hit the “Run”
button and it will test on
its own
What do testers imagine, when they speak of
“test automation”?
About me
• Senior Software tester at
http://siteground.com
• Lecturer at Pragmatic
• Interested in software testing from
scientific perspective
• Would never say “Machines will replace
us”, because I don’t believe it!
• Blogger at: http://mrslavchev.com
Definitions:
Manual testing:
Totally useless term
Failure to provide value by executing
“steps”
Please, don’t dumb down your
expertise by calling it “manual
testing”
Better term: Analytical
testing, Human testing or just
Testing
Automation testing:
Made up “unicorn” term
False belief that testing is simple
sequence of steps
Relies on false belief that testing is
automate-able
Better term: Tool assisted
testing, automated checking,
automation in testing,
programmatic testing
No “manual” and “automation” testing
• Testing is not a car
transmission
• Not all tasks in testing
are equally automate-able
• Testing is analytical
human activity
• Has nothing to do with
hands or manuals
No hate intended
• I actually love coding and resolving
problems in a programmatic way!
• I love testing, too
• I hate it, when false expectations of
testing are spread
• We need to say some “bitter truths” in
order to set things right
• So think of them as “medicines”
Bitter truth #1:
You can’t automate “all the tests”
Activities we perform during testing
Tasks that are easily automatable
Confirmation / Verification
Low level checking
Precision
Functional correctness
Deterministic tests
Solving machine problems
But automation sucks when dealing with:
Exploration
Unanticipated risks
Qualitative evaluation
Open ended questions
Adaptive learning
Solving human problems
Inspired by:Things Could Get Worse- Michael
Bolton
Bitter truth #2:
Test automation won’t decrease
cost of testing
And that’s not even half the truth
Things we hear about automation:
It will decrease time
It will run faster
It’s more reliable
It’s cost effective
Thing is … it’s only
execution cost
How automation can increase cost:
Cost of tools/time
Development
Maintenance
Debugging your own
code
Make the madaf***r
work!
Bitter truth #3:
Don’t think automatic testing,
think programmatic testing
Why does this distinction matter?
Automated testing
Implies testing is fully
automatable
Implies human testing is
replaceable with tools
Defines testing as simple
execution of steps
Looks at testing as test
execution, only
Programmatic testing
Record and play tools =
totally useless!
Understanding of limitations
Understanding of the
approach
Understanding of goals
Bitter truth #4:
Your testing code sux, just like
any other
Because…
Things that testers often forget:
We are “mere mortals” like
anyone else
We design bad tests
We sometimes have no ides
what the f**k are we up to
Testing code is not pixie
dust
What should be our focus, instead?
Why are you automating?
Value?
Development approach
Infrastructure and
maintenance
Testing your own code
Bitter truth #5:
Automation is not human testing
on steroids
The nature of “automation”:
We still use “test
automation” without
realizing what it means
There’s plenty of
analytical “brain” work
automation can’t do.
Humans won’t be replaced
by it, unless they act as
script executors.
Few important takeaways…
It’s a trend and it won’t be
easy
People enjoy easy
We can be successful by using
tools for their right purpose
“Manual” and “automated”
testing are useless terms.
Don’t think inside the labeled
boxes
And most important…
Try not to think
like:
Automate to replace
human testing
but rather:
Automate to extend
your testing and let
it do whatever it can
do better than you
Thank you very much!
Any questions?
Feedback is love!
Feedback is life!
Share your feedback
with us!
https://www.sli.do/
Code #7346

More Related Content

PPTX
"Worst" practices of software testing
PDF
Worst practices in software testing by the Testing troll
PPTX
Automation vs. intelligence - "follow me if you want to live"
PPTX
Break to build - the mindset of the modern day tester
PPTX
Hindsight lessons about API testing
PPTX
James thomas
PPTX
TestWorksConf: Experience exploratory testing
PPTX
What is What is Professional Testing?
"Worst" practices of software testing
Worst practices in software testing by the Testing troll
Automation vs. intelligence - "follow me if you want to live"
Break to build - the mindset of the modern day tester
Hindsight lessons about API testing
James thomas
TestWorksConf: Experience exploratory testing
What is What is Professional Testing?

What's hot (20)

PPTX
Testing All the Way Down, and Other Directions
PPTX
Exploring with Automation
PPTX
Santa Barbara Agile: Exploratory Testing Explained and Experienced
PPTX
How to Test Anything
PPTX
A Context-Driven Approach to Automation in Testing
PPTX
Intro to TDD
PDF
03 - chomu prohramisty ne testuiut - yurii chulovskyi - it event 2013 (5)
PPTX
Bug-Free Software? Go For It!
PDF
Agile Testers: Becoming a key asset for your team
PDF
TestIstanbul May 2013 Keynote Experiences With Exploratory Testing
PDF
Agile Testing Days 2014 Keynote - Helping Testers Add Value on Agile Projects
PDF
Things Could Get Worse: Ideas About Regression Testing
PDF
Push Functional Testing Further
PPTX
Claudiu Draghia ITEM 2018
PDF
A Taste of Exploratory Testing
PDF
Debugging Design [EN]
PPTX
Exploratory testing part 3
PDF
Tests are Nothing, Testing is Everything
PPT
Exploratory Testing Explained
Testing All the Way Down, and Other Directions
Exploring with Automation
Santa Barbara Agile: Exploratory Testing Explained and Experienced
How to Test Anything
A Context-Driven Approach to Automation in Testing
Intro to TDD
03 - chomu prohramisty ne testuiut - yurii chulovskyi - it event 2013 (5)
Bug-Free Software? Go For It!
Agile Testers: Becoming a key asset for your team
TestIstanbul May 2013 Keynote Experiences With Exploratory Testing
Agile Testing Days 2014 Keynote - Helping Testers Add Value on Agile Projects
Things Could Get Worse: Ideas About Regression Testing
Push Functional Testing Further
Claudiu Draghia ITEM 2018
A Taste of Exploratory Testing
Debugging Design [EN]
Exploratory testing part 3
Tests are Nothing, Testing is Everything
Exploratory Testing Explained
Ad

Similar to Test automation – the bitter truth (20)

PDF
Automation testing: how tools are important?
PDF
Keynote: Lightning Strikes the Keynotes
PPTX
Pride and Prejudice and Software Testing
PDF
Graham Thomas - Software Testing Secrets We Dare Not Tell - EuroSTAR 2013
PPTX
A Happy Marriage between Context-Driven and Agile
PPTX
Breathing the breath of the monster combining agile and context-driven
PPTX
Best practices for test automation
PPTX
It's Automation, Not Automagic
PDF
Intelligent Mistakes in Test Automation
PPTX
Test automation and Agile software development
PPTX
Digital Transformation, Testing and Automation
PDF
Blunders in Test Automation
PDF
Check This - Test Automation, A Development Managers View
PDF
Blunders in Test Automation
PPTX
Testing for cognitive bias in ai systems
PDF
Ilari henrik
PPTX
Psychology and Engineering of Testing
PPTX
SDLC. QA Role
PPTX
Fantastic Tests - The Crimes of Bad Test Design
PDF
Re-thinking Test Automation and Test Process Modelling (in pictures)
Automation testing: how tools are important?
Keynote: Lightning Strikes the Keynotes
Pride and Prejudice and Software Testing
Graham Thomas - Software Testing Secrets We Dare Not Tell - EuroSTAR 2013
A Happy Marriage between Context-Driven and Agile
Breathing the breath of the monster combining agile and context-driven
Best practices for test automation
It's Automation, Not Automagic
Intelligent Mistakes in Test Automation
Test automation and Agile software development
Digital Transformation, Testing and Automation
Blunders in Test Automation
Check This - Test Automation, A Development Managers View
Blunders in Test Automation
Testing for cognitive bias in ai systems
Ilari henrik
Psychology and Engineering of Testing
SDLC. QA Role
Fantastic Tests - The Crimes of Bad Test Design
Re-thinking Test Automation and Test Process Modelling (in pictures)
Ad

Recently uploaded (20)

PDF
Design an Analysis of Algorithms I-SECS-1021-03
PPTX
Operating system designcfffgfgggggggvggggggggg
PDF
Audit Checklist Design Aligning with ISO, IATF, and Industry Standards — Omne...
PDF
How to Migrate SBCGlobal Email to Yahoo Easily
PPTX
ManageIQ - Sprint 268 Review - Slide Deck
PDF
Upgrade and Innovation Strategies for SAP ERP Customers
PPTX
Odoo POS Development Services by CandidRoot Solutions
PDF
System and Network Administraation Chapter 3
PDF
Adobe Illustrator 28.6 Crack My Vision of Vector Design
PDF
SAP S4 Hana Brochure 3 (PTS SYSTEMS AND SOLUTIONS)
PDF
Understanding Forklifts - TECH EHS Solution
PPTX
Introduction to Artificial Intelligence
PDF
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
PDF
Odoo Companies in India – Driving Business Transformation.pdf
PDF
AI in Product Development-omnex systems
PPTX
ai tools demonstartion for schools and inter college
PDF
How Creative Agencies Leverage Project Management Software.pdf
PPTX
Lecture 3: Operating Systems Introduction to Computer Hardware Systems
PDF
Which alternative to Crystal Reports is best for small or large businesses.pdf
PDF
2025 Textile ERP Trends: SAP, Odoo & Oracle
Design an Analysis of Algorithms I-SECS-1021-03
Operating system designcfffgfgggggggvggggggggg
Audit Checklist Design Aligning with ISO, IATF, and Industry Standards — Omne...
How to Migrate SBCGlobal Email to Yahoo Easily
ManageIQ - Sprint 268 Review - Slide Deck
Upgrade and Innovation Strategies for SAP ERP Customers
Odoo POS Development Services by CandidRoot Solutions
System and Network Administraation Chapter 3
Adobe Illustrator 28.6 Crack My Vision of Vector Design
SAP S4 Hana Brochure 3 (PTS SYSTEMS AND SOLUTIONS)
Understanding Forklifts - TECH EHS Solution
Introduction to Artificial Intelligence
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
Odoo Companies in India – Driving Business Transformation.pdf
AI in Product Development-omnex systems
ai tools demonstartion for schools and inter college
How Creative Agencies Leverage Project Management Software.pdf
Lecture 3: Operating Systems Introduction to Computer Hardware Systems
Which alternative to Crystal Reports is best for small or large businesses.pdf
2025 Textile ERP Trends: SAP, Odoo & Oracle

Test automation – the bitter truth

  • 1. Test automation – the bitter truth Some unpleasant truths about “test automation”
  • 2. Be a part of the show! Ask a question or leave your feedback at: https://www.sli.do/ using code #7346
  • 3. Before we start, few prerequisites: Here’s a story …
  • 4. What do testers imagine when they see “manual testing”? • Ineffective • Boring • Slow • Easy to perform by anyone • Mindless banging of keys
  • 5. What do managers feel when they speak of “manual testing”? • “You are wasting too much time. “ • “We have too much testers” • “We can easily automate what you do.” • “You are not reliable”
  • 6. How both managers and testers react when someone mentions “automation”? • Totally fangirling • We will reduce costs • We will have more time for “manual” testing • I will only hit the “Run” button and it will test on its own
  • 7. What do testers imagine, when they speak of “test automation”?
  • 8. About me • Senior Software tester at http://siteground.com • Lecturer at Pragmatic • Interested in software testing from scientific perspective • Would never say “Machines will replace us”, because I don’t believe it! • Blogger at: http://mrslavchev.com
  • 10. Manual testing: Totally useless term Failure to provide value by executing “steps” Please, don’t dumb down your expertise by calling it “manual testing” Better term: Analytical testing, Human testing or just Testing
  • 11. Automation testing: Made up “unicorn” term False belief that testing is simple sequence of steps Relies on false belief that testing is automate-able Better term: Tool assisted testing, automated checking, automation in testing, programmatic testing
  • 12. No “manual” and “automation” testing • Testing is not a car transmission • Not all tasks in testing are equally automate-able • Testing is analytical human activity • Has nothing to do with hands or manuals
  • 13. No hate intended • I actually love coding and resolving problems in a programmatic way! • I love testing, too • I hate it, when false expectations of testing are spread • We need to say some “bitter truths” in order to set things right • So think of them as “medicines”
  • 14. Bitter truth #1: You can’t automate “all the tests”
  • 15. Activities we perform during testing
  • 16. Tasks that are easily automatable Confirmation / Verification Low level checking Precision Functional correctness Deterministic tests Solving machine problems
  • 17. But automation sucks when dealing with: Exploration Unanticipated risks Qualitative evaluation Open ended questions Adaptive learning Solving human problems Inspired by:Things Could Get Worse- Michael Bolton
  • 18. Bitter truth #2: Test automation won’t decrease cost of testing And that’s not even half the truth
  • 19. Things we hear about automation: It will decrease time It will run faster It’s more reliable It’s cost effective Thing is … it’s only execution cost
  • 20. How automation can increase cost: Cost of tools/time Development Maintenance Debugging your own code Make the madaf***r work!
  • 21. Bitter truth #3: Don’t think automatic testing, think programmatic testing
  • 22. Why does this distinction matter? Automated testing Implies testing is fully automatable Implies human testing is replaceable with tools Defines testing as simple execution of steps Looks at testing as test execution, only Programmatic testing Record and play tools = totally useless! Understanding of limitations Understanding of the approach Understanding of goals
  • 23. Bitter truth #4: Your testing code sux, just like any other
  • 25. Things that testers often forget: We are “mere mortals” like anyone else We design bad tests We sometimes have no ides what the f**k are we up to Testing code is not pixie dust
  • 26. What should be our focus, instead? Why are you automating? Value? Development approach Infrastructure and maintenance Testing your own code
  • 27. Bitter truth #5: Automation is not human testing on steroids
  • 28. The nature of “automation”: We still use “test automation” without realizing what it means There’s plenty of analytical “brain” work automation can’t do. Humans won’t be replaced by it, unless they act as script executors.
  • 29. Few important takeaways… It’s a trend and it won’t be easy People enjoy easy We can be successful by using tools for their right purpose “Manual” and “automated” testing are useless terms. Don’t think inside the labeled boxes
  • 30. And most important… Try not to think like: Automate to replace human testing but rather: Automate to extend your testing and let it do whatever it can do better than you
  • 31. Thank you very much! Any questions?
  • 32. Feedback is love! Feedback is life! Share your feedback with us! https://www.sli.do/ Code #7346