Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Sustainable Test Automation: Collaborate within Team

124 views

Published on

Доклад Berk Dülger на SQA Days-22. 17-18 ноября 2017. Санкт-Петербург, Россия
www.sqadays.com

Published in: Education
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1url.pw/NO0pz ◀ ◀ ◀ ◀
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Sustainable Test Automation: Collaborate within Team

  1. 1. SUSTAINABLE TEST AUTOMATION COLLABORATE WITHIN TEAM Berk DUlger SQA Days 2017, St. Petersburg
  2. 2. BusinessKnow-How Asymmetry Changing Requirements ImproperRisk Management Tool Dependence Insufficient Time UntestableCode Test AutomationAnti-Patterns Problematic Data Management Monolithic Applications Technical Debt Over Expectations Unclear Duties Challenges in Test Automation
  3. 3. Any Test Automation ACTIVITY should address Manual Testing Efforts Long feedback times Operatıonal Blındness Error-Prone Actıvıtıes
  4. 4. We need to make test automation SUSTAINABLE
  5. 5. Sustainable success requires both bottom-up practices and top-down management support
  6. 6. Handle Test automatıon As an Actıvıty Make part of Definition of Done
  7. 7. It’s not Reasonable to automate everything Manualtesting is strongly advised andALSO required for SOMETest Level/types
  8. 8. Learn RISK MANAGEment IDENTIFY, ASSESS and MITIGATE RISKS Be Friend of P-I Tables
  9. 9. %80 of Customer Usage arises from %20 Functionality, Pareto Prınciple No need to automateAll of Your Test CaseS
  10. 10. More cases you develop, More Maıntenance effort you face Soon or Later, Logistics curve will be here Get rid of old test cases
  11. 11. Continuous Testing E-commerce Case Study InflectionPoint 2-3TestCasesperMan/Day NearlyNoMaintanceEffort 3-5TestCasesperMan/Day LessMaintance Effort (%20) 2-3TestCasesperMan/Day ModerateMaintanceEffort (%70) 3 TestCasesperMan/Day ModerateMaintanceEffort (%50) ~1TestCasesper Man/Day HeavyMaintanceEffort (%90) Basedon metricsfrom 14 consultancyprojects
  12. 12. Test Automation BEST Practices Software Testıng Ice-Cone Antı-Pattern vs Ideal Software testıng pyramıd IMAGE, www.thoughtworks.com/insights/blog/architecting-continuous-delivery
  13. 13. Four Design Techniques for Successful Test Automation Data Management A typical maturity level of data management for test automationprocess is outlinedhere; FullyIntegrated Test Data PartiallyIndependentTest Data StoringTest Datainan External Source DynamicTest Data Management (MicroServices, GUI ?)
  14. 14. EMBRACE MICROServıces At Least Services ımage https://martinfowler.com/articles/microservices
  15. 15. Learn more about Data Virtualization It makes test data management easier An added advantage here is thatif the data in any environmentis corrupted – let’s say after a round of testing- it is very easy to revert the data back to original state.
  16. 16. Make Test Automation, Backbone of the CI/CD Pipeline
  17. 17. Test Automation, like other CI/CD activities,is extremely CROSS-DISCIPLINARY And require different skill and mind-set
  18. 18. MAKEEveryoneintheTeam InvolvedintheProcess, 3-Amigos Analyst Developer Tester
  19. 19. BDDfocuses on obtaining a clear understandingof desiredsoftware behaviorthrough discussion with stakeholders. Martin Fowler’s Business Readable, Domain Specific Language Blog Post
  20. 20. Another crucial point is to provide an abstraction layer between automation tool and test sUite. Selenium, Sahi, UFT, Coded UI whatever tool underlying should not be concern for automator
  21. 21. Three LayerArchitecture andBDD
  22. 22. A Test Architect is responsiblefor FRAMEWORK LAYER, whichprovides utility functionsto upper layers It is heavily one-timeeffort, and not addressedin the project iterations
  23. 23. DEVELOPERS within projects/sprints is responsible for PAGE LAYER, provide keywords for upper/bdd layer.
  24. 24. Testers are responsiblefor TEST LAYER, which is Better To BE BDD, to create business value to each stakeholder Analystsare responsible for detailedand correct acceptance-criteria thatBDD Scripts base on
  25. 25. ALSO %50 of THE MAINTENANCEEFFORTCOMES FROM CHANgING OBJECT IDENTIFIERS LET’S MAKEIT EVERYONE’SJOB IN THE TEAM NOT ONLY SOMEONe
  26. 26. Спасибо berk.dulger@keytorc.com berkdulger.github.io www.linkedin.com/in/berkdulger

×