O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

3

Compartilhar

Baixar para ler offline

Inverting Test Pyramid - A First Hand Experience Report

Baixar para ler offline

Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you.

Business Impact:

* Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing.

* Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less.

Reduced test execution time - Backend tests are much faster. Almost 7-10 times faster than UI Tests - improved build certification time.

* Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular.

Details: http://confengine.com/agile-pune-2014/proposal/471/inverting-test-pyramid-a-first-hand-experience-report

Conference: http://pune.agileindia.org/

Audiolivros relacionados

Gratuito durante 30 dias do Scribd

Ver tudo

Inverting Test Pyramid - A First Hand Experience Report

  1. 1. Inverting Test PyramidExperience ReportSachin Natu @natusachinNaresh Jain @nashjain
  2. 2. 25YEARS 6000+CLIENTS Nr 1M ROOMS 94COUNTRIES 95% + ago we started helping clients manage their revenue later we’re still finding the revenue opportunity in every situation around the world are priced every single day using IDeaS on 6 continents have hotels that now run on IDeaS Revenue Management Systems More than 95 percent of all our clients are still working with us today. About IDeaS
  3. 3. Our Worldwide Clients : Hospitality + Travel + Distribution
  4. 4. Agenda ●Where were we? ●Problem ●How we tried to solve? ●How we optimized?
  5. 5. Status of regression time Page
  6. 6. No Automation !
  7. 7. Problems ●Thousands of regression tests ●Cross cutting defects found were more. ●Repeat Execution
  8. 8. Moving to shorter release cycle -a dream?
  9. 9. Regression period is incompressible
  10. 10. Manual and repetitive tasks are error prone.
  11. 11. Issue leakages Page Releases
  12. 12. Let’s automate regression Page
  13. 13. UI Test Page
  14. 14. After Automation Introduced
  15. 15. Production feedback Page
  16. 16. Duration… 2 Yrs Team of 2 full time Automation Testers
  17. 17. State of the Product ManualChecking 45% End-to End UI Tests 40% Integration Tests 10% Unit Tests 5%
  18. 18. Always Catching Up
  19. 19. No pinpointed feedback
  20. 20. Silos
  21. 21. Tests are slow
  22. 22. Costly to maintain
  23. 23. Is there way out? Page
  24. 24. Analysis of Bugs Report
  25. 25. Why are we testing from far?
  26. 26. ManualChecking End-to End Selenium Tests 70% Integration Tests 20% Unit Tests 10% Unit Tests 70% Domain Logic Acceptance Tests 10% Integration Tests 9% Workflow API Tests 6% End to End Flow Tests 4% UI 1% Typical test strategies lead to an inverted testing pyramid This is the need of the hour…. Courtesy: Naresh Jain @AgileFAQs.com The Test Pyramid
  27. 27. Our transition story… •We decided to "Test things right , at right place on right time" which would result in "right test pyramid“ Unit Tests 70% Domain Logic Acceptance Tests 10% Integration Tests 9% Workflow API Tests 6% E to E 4% UI 1%
  28. 28. Business logic test
  29. 29. Current Status
  30. 30. Benefits
  31. 31. Automation is part of development •TDD •BDD •UI Tests only worry for UI
  32. 32. Improved collaboration Developer QA
  33. 33. UI Tests –Grouping Functionality 80 Scenarios -300 + Min!
  34. 34. Correct automation improved time. 80 Scenarios < Min! Workflow -4 Min UI Tests -4 Min
  35. 35. Regression timelines Page Months
  36. 36. Feels like Agile now... Page
  37. 37. Challenges •Legacy code -“Unit test unfriendly” •Mapping acceptance tests with various slices of pyramid •Building team competencies •Pairing/ collaboration is backbone
  38. 38. Key learning •Use UI automation only where really necessary •It’s team responsibility •Testability is important criteria. Unit Tests 70% Domain Logic Acceptance Tests 10% Integration Tests 9% Workflow API Tests 6% End to End Flow Tests 4% UI 1%
  39. 39. Naresh Jain @nashjain Sachin Natu @natusachin Page
  40. 40. Some Statistics...
  • marciosousa7528

    Mar. 11, 2020
  • YenNgo40

    Dec. 7, 2019
  • MekSrunyuStittri

    Sep. 16, 2015

Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you. Business Impact: * Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing. * Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less. Reduced test execution time - Backend tests are much faster. Almost 7-10 times faster than UI Tests - improved build certification time. * Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular. Details: http://confengine.com/agile-pune-2014/proposal/471/inverting-test-pyramid-a-first-hand-experience-report Conference: http://pune.agileindia.org/

Vistos

Vistos totais

2.074

No Slideshare

0

De incorporações

0

Número de incorporações

382

Ações

Baixados

31

Compartilhados

0

Comentários

0

Curtir

3

×