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

630 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
630
On SlideShare
0
From Embeds
0
Number of Embeds
317
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • AS 26.06.13 Preventing defects
  • Using Functional ,Test Automation to Prevent Defects from Escaping the Development Phase' by Alexandra Schladebeck

    1. 1. Version 2.5© Bredex GmbHUsing Functional Test Automation toPrevent Defects from Escaping theDevelopment PhaseAlexandra Schladebeck
    2. 2. 2Agenda 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. 3Prevention versus cure Prevention?  Discovery andremoval (or: seek anddestroy)
    4. 4. 4How soon is now?
    5. 5. 5Software, defend yourself! Justification Test criteria During development Frequently Regardless of model… More information isbeneficial As early as possible
    6. 6. 6Focusing 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 whichit will be used
    7. 7. 7Use test automation to test… Automate acceptance tests duringdevelopment ATDD / In parallel / Just after The early automatorgets the worm Steps… Review Automate Repeat (React)
    8. 8. 8Step 1: Preparing for automation Explore Read, talk, prototype, document, play Set the bar What is good enough Tests and checks Select automationcandidates
    9. 9. 9Bugs prevented in step one Case 1: Remembered reportReport written during test Report generated after test
    10. 10. 10Bugs prevented in step one Case 2: Forgotten option
    11. 11. 11Step 2: Do the automation As close as possible Be a user while writing the test Different paths and alternatives whiledesigning / testing Exactness for automation Added bonuses Usability testing Open questions
    12. 12. 12Step 2: Do the automation Long-life tests Test structure Levels of detail Small use cases Independent tests Plan for change
    13. 13. 13Bugs caught in step two Enter customer name Enter address Enter telephonenumber Leave field via enter Enter customer name Enter address Enter telephonenumber Don‘t leave field /leave field via click
    14. 14. 14Bugs caught in step two Validation  PDF LibraryMandatory fieldswith *Mandatory fieldsvalidated byprogram…all of them? … NoClassDefFound
    15. 15. 15Step 3: Lather, rinse, repeat Activity of automating test has gatheredall information it can? Multiply Same test  new area of application Same test  another platform Same test  new software versions
    16. 16. 16Step 3: The glossy finish Continuousintegration Error handling intests
    17. 17. 17Bugs prevented by step three Case 1:Multiplication error Case 2:Regression errorOKOKOKFailed
    18. 18. 18Step 4: React
    19. 19. 19Step 4: React
    20. 20. 20What have we got so far?
    21. 21. 21What‘s missing?
    22. 22. 22Checklist 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. 23. 23Thank you!Alexandra.Schladebeck@bredex.deblog.bredex.dewww.bredexsw.comTwitter: alex_schl

    ×