SlideShare a Scribd company logo
Version 2.5© Bredex GmbH
Using Functional Test Automation to
Prevent Defects from Escaping the
Development Phase
Alexandra Schladebeck
2
Agenda
 Prevention versus cure
 Testing close to development
 Focus on the user perspective
 Automation as a quality-enhancing activity
 Open points for the test process
 Checklist and conclusions
3
Prevention versus cure
 Prevention?  Discovery and
removal
 (or: seek and
destroy)
4
How soon is now?
5
Software, defend yourself!
 Justification
 Test criteria
 During development
 Frequently
 Regardless of model…
 More information is
beneficial
 As early as possible
6
Focusing on what‘s important
 What informaton do we want?
 What sources are available to us?
 What are our priorities?
 Our focus: customer perspective
 … the perspective with which
it will be used
7
Use test automation to test…
 Automate acceptance tests during
development
 ATDD / In parallel / Just after
 The early automator
gets the worm
 Steps…
 Review
 Automate
 Repeat
 (React)
8
Step 1: Preparing for automation
 Explore
 Read, talk, prototype, document, play
 Set the bar
 What is good enough
 Tests and checks
 Select automation
candidates
9
Bugs prevented in step one
 Case 1: Remembered report
Report written during test Report generated after test
10
Bugs prevented in step one
 Case 2: Forgotten option
11
Step 2: Do the automation
 As close as possible
 Be a user while writing the test
 Different paths and alternatives while
designing / testing
 Exactness for automation
 Added bonuses
 Usability testing
 Open questions
12
Step 2: Do the automation
 Long-life tests
 Test structure
 Levels of detail
 Small use cases
 Independent tests
 Plan for change
13
Bugs caught in step two
 Enter customer name
 Enter address
 Enter telephone
number
 Leave field via enter
 Enter customer name
 Enter address
 Enter telephone
number
 Don‘t leave field /
leave field via click
14
Bugs caught in step two
 Validation  PDF Library
Mandatory fields
with *
Mandatory fields
validated by
program
…all of them? … NoClassDefFound
15
Step 3: Lather, rinse, repeat
 Activity of automating test has gathered
all information it can?
 Multiply
 Same test  new area of application
 Same test  another platform
 Same test  new software versions
16
Step 3: The glossy finish
 Continuous
integration
 Error handling in
tests
17
Bugs prevented by step three
 Case 1:
Multiplication error
 Case 2:
Regression error
OK
OK
OK
Failed
18
Step 4: React
19
Step 4: React
20
What have we got so far?
21
What‘s missing?
22
Checklist
 Add the test perspective
 Tester, User, Documentation
 Start automating
 As close as possible
 Explicit tests
 Find ways to gain feedback
 CI, Show & Tell, Docu
 React to feedback
23
Thank you!
Alexandra.Schladebeck@bredex.de
blog.bredex.de
www.bredexsw.com
Twitter: alex_schl

More Related Content

What's hot (20)

PPTX
'Growing to a Next Level Test Organisation' by Tim Koomen
TEST Huddle
 
PPT
Mattias Diagl - Low Budget Tooling - Excel-ent
TEST Huddle
 
PPT
Bart Knaack - The Truth About Model-Based Quality Improvements
TEST Huddle
 
PPT
'Acceptance Testing' by Erik Boelen
TEST Huddle
 
PPT
Kasper Hanselman - Imagination is More Important Than Knowledge
TEST Huddle
 
PPT
Peter Zimmerer - Establishing Testing Knowledge and Experience Sharing at Sie...
TEST Huddle
 
PPT
Vipul Kocher - Software Testing, A Framework Based Approach
TEST Huddle
 
PDF
Fredrik Rydberg - Can Exploratory Testing Save Lives - EuroSTAR 2010
TEST Huddle
 
PPT
Derk jan de Grood - ET, Best of Both Worlds
TEST Huddle
 
PPT
Paula O' Grady - Prioritising tests? - Use Your Gut Instinct
TEST Huddle
 
PPT
'Continuous Quality Improvements – A Journey Through The Largest Scrum Projec...
TEST Huddle
 
PPT
Otto Vinter - Analysing Your Defect Data for Improvement Potential
TEST Huddle
 
PPTX
Mickiel Vroon - Test Environment, The Future Achilles’ Heel
TEST Huddle
 
PPT
Michael Roar Borlund & Christian Carlsen - Real Exploratory Testing, Now With...
TEST Huddle
 
PDF
Julian Harty - Alternatives To Testing - EuroSTAR 2010
TEST Huddle
 
PPT
Mattias Ratert - Incremental Scenario Testing
TEST Huddle
 
PDF
Henrik Andersson - Exploratory Testing Champions - EuroSTAR 2010
TEST Huddle
 
PPT
Testing
nazeer pasha
 
PDF
Doron Reuveni - The Mobile App Quality Challenge - EuroSTAR 2010
TEST Huddle
 
PDF
Christian Bk Hansen - Agile on Huge Banking Mainframe Legacy Systems - EuroST...
TEST Huddle
 
'Growing to a Next Level Test Organisation' by Tim Koomen
TEST Huddle
 
Mattias Diagl - Low Budget Tooling - Excel-ent
TEST Huddle
 
Bart Knaack - The Truth About Model-Based Quality Improvements
TEST Huddle
 
'Acceptance Testing' by Erik Boelen
TEST Huddle
 
Kasper Hanselman - Imagination is More Important Than Knowledge
TEST Huddle
 
Peter Zimmerer - Establishing Testing Knowledge and Experience Sharing at Sie...
TEST Huddle
 
Vipul Kocher - Software Testing, A Framework Based Approach
TEST Huddle
 
Fredrik Rydberg - Can Exploratory Testing Save Lives - EuroSTAR 2010
TEST Huddle
 
Derk jan de Grood - ET, Best of Both Worlds
TEST Huddle
 
Paula O' Grady - Prioritising tests? - Use Your Gut Instinct
TEST Huddle
 
'Continuous Quality Improvements – A Journey Through The Largest Scrum Projec...
TEST Huddle
 
Otto Vinter - Analysing Your Defect Data for Improvement Potential
TEST Huddle
 
Mickiel Vroon - Test Environment, The Future Achilles’ Heel
TEST Huddle
 
Michael Roar Borlund & Christian Carlsen - Real Exploratory Testing, Now With...
TEST Huddle
 
Julian Harty - Alternatives To Testing - EuroSTAR 2010
TEST Huddle
 
Mattias Ratert - Incremental Scenario Testing
TEST Huddle
 
Henrik Andersson - Exploratory Testing Champions - EuroSTAR 2010
TEST Huddle
 
Testing
nazeer pasha
 
Doron Reuveni - The Mobile App Quality Challenge - EuroSTAR 2010
TEST Huddle
 
Christian Bk Hansen - Agile on Huge Banking Mainframe Legacy Systems - EuroST...
TEST Huddle
 

Viewers also liked (8)

PDF
Innovate 2013 session 1243 mobile testing.v3
Leigh Williamson
 
PPT
Automated Testing vs Manual Testing
Directi Group
 
PDF
Agile Testing Framework - The Art of Automated Testing
Dimitri Ponomareff
 
PPTX
How to Design a Successful Test Automation Strategy
Impetus Technologies
 
PDF
Introduction to Test Automation - Technology and Tools
KMS Technology
 
PPT
Test Automation Strategies For Agile
Naresh Jain
 
PPT
Automation testing strategy, approach & planning
SivaprasanthRentala1975
 
PPT
Test Automation Framework Designs
Sauce Labs
 
Innovate 2013 session 1243 mobile testing.v3
Leigh Williamson
 
Automated Testing vs Manual Testing
Directi Group
 
Agile Testing Framework - The Art of Automated Testing
Dimitri Ponomareff
 
How to Design a Successful Test Automation Strategy
Impetus Technologies
 
Introduction to Test Automation - Technology and Tools
KMS Technology
 
Test Automation Strategies For Agile
Naresh Jain
 
Automation testing strategy, approach & planning
SivaprasanthRentala1975
 
Test Automation Framework Designs
Sauce Labs
 
Ad

Similar to Using Functional ,Test Automation to Prevent Defects from Escaping the Development Phase' by Alexandra Schladebeck (20)

PPT
Usability Primer - for Alberta Municipal Webmasters Working Group
NormanMendoza
 
PPTX
Insoft training day_1
Sriram Angajala
 
PDF
Heuristics of performance testing
Pradeep Soundararajan
 
PPT
Q Labs Webinar on Testcase Prioritization [Feb 20, 2009]
Vipul Gupta
 
PDF
Agile Testing Pasadena JUG Aug2009
Grig Gheorghiu
 
PPT
Test case development
Hrushikesh Wakhle
 
PPT
Software testing
thaneofife
 
DOC
Manual testing interview question by INFOTECH
Pravinsinh
 
PPTX
Use Automation to Assist -Not Replace- Manual Testing
SmartBear
 
PPT
Risk Driven Testing
Jorge Boria
 
PDF
Effective Testing fo Startups
Testnetic
 
PDF
Usability Testing 101 - an introduction
Elizabeth Snowdon
 
PPT
Less01 1 introduction_module
Suresh Mishra
 
PDF
What is Test Case in Manual Testing (1).pdf
Infotek Solutions
 
PDF
Session17-Software Testing.pdf
PeterTran514407
 
DOC
Manualtestinginterviewquestionbyinfotech 100901071035-phpapp01
Anshuman Rai
 
DOC
Manual testing interview questions by infotech
suhasreddy1
 
PPT
Best practices quality assurance
Shakal Shukla
 
PPT
11_Automated_Testing.ppt
ShivareddyGangam
 
Usability Primer - for Alberta Municipal Webmasters Working Group
NormanMendoza
 
Insoft training day_1
Sriram Angajala
 
Heuristics of performance testing
Pradeep Soundararajan
 
Q Labs Webinar on Testcase Prioritization [Feb 20, 2009]
Vipul Gupta
 
Agile Testing Pasadena JUG Aug2009
Grig Gheorghiu
 
Test case development
Hrushikesh Wakhle
 
Software testing
thaneofife
 
Manual testing interview question by INFOTECH
Pravinsinh
 
Use Automation to Assist -Not Replace- Manual Testing
SmartBear
 
Risk Driven Testing
Jorge Boria
 
Effective Testing fo Startups
Testnetic
 
Usability Testing 101 - an introduction
Elizabeth Snowdon
 
Less01 1 introduction_module
Suresh Mishra
 
What is Test Case in Manual Testing (1).pdf
Infotek Solutions
 
Session17-Software Testing.pdf
PeterTran514407
 
Manualtestinginterviewquestionbyinfotech 100901071035-phpapp01
Anshuman Rai
 
Manual testing interview questions by infotech
suhasreddy1
 
Best practices quality assurance
Shakal Shukla
 
11_Automated_Testing.ppt
ShivareddyGangam
 
Ad

More from TEST Huddle (20)

PPTX
Why We Need Diversity in Testing- Accenture
TEST Huddle
 
PPTX
Keys to continuous testing for faster delivery euro star webinar
TEST Huddle
 
PPTX
Why you Shouldnt Automated But You Will Anyway
TEST Huddle
 
PDF
Being a Tester in Scrum
TEST Huddle
 
PDF
Leveraging Visual Testing with Your Functional Tests
TEST Huddle
 
PPTX
Using Test Trees to get an Overview of Test Work
TEST Huddle
 
PPTX
Big Data: The Magic to Attain New Heights
TEST Huddle
 
PPTX
Will Robots Replace Testers?
TEST Huddle
 
PPTX
TDD For The Rest Of Us
TEST Huddle
 
PDF
Scaling Agile with LeSS (Large Scale Scrum)
TEST Huddle
 
PPTX
Creating Agile Test Strategies for Larger Enterprises
TEST Huddle
 
PPTX
Is There A Risk?
TEST Huddle
 
PDF
Are Your Tests Well-Travelled? Thoughts About Test Coverage
TEST Huddle
 
PDF
Growing a Company Test Community: Roles and Paths for Testers
TEST Huddle
 
PDF
Do we need testers on agile teams?
TEST Huddle
 
PDF
How to use selenium successfully
TEST Huddle
 
PDF
Testers & Teams on the Agile Fluency™ Journey
TEST Huddle
 
PDF
Practical Test Strategy Using Heuristics
TEST Huddle
 
PDF
Thinking Through Your Role
TEST Huddle
 
PDF
Using Selenium 3 0
TEST Huddle
 
Why We Need Diversity in Testing- Accenture
TEST Huddle
 
Keys to continuous testing for faster delivery euro star webinar
TEST Huddle
 
Why you Shouldnt Automated But You Will Anyway
TEST Huddle
 
Being a Tester in Scrum
TEST Huddle
 
Leveraging Visual Testing with Your Functional Tests
TEST Huddle
 
Using Test Trees to get an Overview of Test Work
TEST Huddle
 
Big Data: The Magic to Attain New Heights
TEST Huddle
 
Will Robots Replace Testers?
TEST Huddle
 
TDD For The Rest Of Us
TEST Huddle
 
Scaling Agile with LeSS (Large Scale Scrum)
TEST Huddle
 
Creating Agile Test Strategies for Larger Enterprises
TEST Huddle
 
Is There A Risk?
TEST Huddle
 
Are Your Tests Well-Travelled? Thoughts About Test Coverage
TEST Huddle
 
Growing a Company Test Community: Roles and Paths for Testers
TEST Huddle
 
Do we need testers on agile teams?
TEST Huddle
 
How to use selenium successfully
TEST Huddle
 
Testers & Teams on the Agile Fluency™ Journey
TEST Huddle
 
Practical Test Strategy Using Heuristics
TEST Huddle
 
Thinking Through Your Role
TEST Huddle
 
Using Selenium 3 0
TEST Huddle
 

Using Functional ,Test Automation to Prevent Defects from Escaping the Development Phase' by Alexandra Schladebeck

  • 1. Version 2.5© Bredex GmbH Using Functional Test Automation to Prevent Defects from Escaping the Development Phase Alexandra Schladebeck
  • 2. 2 Agenda  Prevention versus cure  Testing close to development  Focus on the user perspective  Automation as a quality-enhancing activity  Open points for the test process  Checklist and conclusions
  • 3. 3 Prevention versus cure  Prevention?  Discovery and removal  (or: seek and destroy)
  • 5. 5 Software, defend yourself!  Justification  Test criteria  During development  Frequently  Regardless of model…  More information is beneficial  As early as possible
  • 6. 6 Focusing on what‘s important  What informaton do we want?  What sources are available to us?  What are our priorities?  Our focus: customer perspective  … the perspective with which it will be used
  • 7. 7 Use test automation to test…  Automate acceptance tests during development  ATDD / In parallel / Just after  The early automator gets the worm  Steps…  Review  Automate  Repeat  (React)
  • 8. 8 Step 1: Preparing for automation  Explore  Read, talk, prototype, document, play  Set the bar  What is good enough  Tests and checks  Select automation candidates
  • 9. 9 Bugs prevented in step one  Case 1: Remembered report Report written during test Report generated after test
  • 10. 10 Bugs prevented in step one  Case 2: Forgotten option
  • 11. 11 Step 2: Do the automation  As close as possible  Be a user while writing the test  Different paths and alternatives while designing / testing  Exactness for automation  Added bonuses  Usability testing  Open questions
  • 12. 12 Step 2: Do the automation  Long-life tests  Test structure  Levels of detail  Small use cases  Independent tests  Plan for change
  • 13. 13 Bugs caught in step two  Enter customer name  Enter address  Enter telephone number  Leave field via enter  Enter customer name  Enter address  Enter telephone number  Don‘t leave field / leave field via click
  • 14. 14 Bugs caught in step two  Validation  PDF Library Mandatory fields with * Mandatory fields validated by program …all of them? … NoClassDefFound
  • 15. 15 Step 3: Lather, rinse, repeat  Activity of automating test has gathered all information it can?  Multiply  Same test  new area of application  Same test  another platform  Same test  new software versions
  • 16. 16 Step 3: The glossy finish  Continuous integration  Error handling in tests
  • 17. 17 Bugs prevented by step three  Case 1: Multiplication error  Case 2: Regression error OK OK OK Failed
  • 20. 20 What have we got so far?
  • 22. 22 Checklist  Add the test perspective  Tester, User, Documentation  Start automating  As close as possible  Explicit tests  Find ways to gain feedback  CI, Show & Tell, Docu  React to feedback

Editor's Notes

  • #2: AS 26.06.13 Preventing defects
  • #4: AS 26.06.13 Preventing defects
  • #5: AS 26.06.13 Preventing defects
  • #6: AS 26.06.13 Preventing defects
  • #7: AS 26.06.13 Preventing defects
  • #8: AS 26.06.13 Preventing defects
  • #9: AS 26.06.13 Preventing defects
  • #10: AS 26.06.13 Preventing defects
  • #11: AS 26.06.13 Preventing defects
  • #12: AS 26.06.13 Preventing defects
  • #13: AS 26.06.13 Preventing defects
  • #14: AS 26.06.13 Preventing defects
  • #15: AS 26.06.13 Preventing defects
  • #16: AS 26.06.13 Preventing defects
  • #18: AS 26.06.13 Preventing defects
  • #19: AS 26.06.13 Preventing defects
  • #20: AS 26.06.13 Preventing defects
  • #21: AS 26.06.13 Preventing defects
  • #23: AS 26.06.13 Preventing defects