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.

Agile Testing Framework - The Art of Automated Testing


Published on

Once your organization has successfully implemented Agile methodologies, there are two major areas that will require improvements: Continuous Integration and Automated Testing.

This presentation illustrates why it's important to invest in an Automated Testing Framework (ATF) to reduce technical debt, increase quality and accelerate time to market.

Learn more at

Published in: Technology
  • Substandard data quality is harming organizations to an immense extent. Inaccurate and erroneous data impacts organizations with budget increments, customer displeasure, and organizational uncertainty. This is where automation testing can resolve the vulnerability by verifying the data.
    Are you sure you want to  Yes  No
    Your message goes here
  • Learn how to build a continuous testing framework for your clients with out Whitepaper.
    Are you sure you want to  Yes  No
    Your message goes here
  • Nice !! Download 100 % Free Ebooks, PPts, Study Notes, Novels, etc @
    Are you sure you want to  Yes  No
    Your message goes here

Agile Testing Framework - The Art of Automated Testing

  1. 1. Agile Testing Framework The Art of Automated Testing
  2. 2. About Dimitri Ponomareff Dimitri Ponomareff ( is a Coach. Whether it's a sports team, software products or entire organizations, Dimitri has that ability to relate and energize people. He is consistently recognized as a very passionate and successful change agent, with an overwhelming capacity to motivate and mobilize teams on their path to continuous improvements. He is a master facilitator, as well as a captivating speaker with consistent, positive feedback regarding his ability to engage an audience. As a certified Coach, Project Manager and Facilitator of "The 7 Habits of Highly Effective People", Dimitri brings a full spectrum of knowledge in his delivery of methodologies. Through teaching by example, he is able to build teams of people who understand where to focus their work to generate the most value. He has coached and provided tailor-made services and training for a multitude of organizations. The short list includes, American Express, Charles Schwab, Bank of America, Morgan Stanley, Best Western, Choice Hotels, JDA Software, LifeLock, First Solar, Infusionsoft and Mayo Clinic. Dimitri enjoys his work, and does everything to ensure he shares his knowledge with others who seek it.
  3. 3. Agenda ● Agile Methodologies ● Agile Testing Quadrant ● Quality ● Technical Debt ● The Testing Pyramid ● Driven Development ○ FDD ○ TDD ○ BDD ● Agile Testing Framework
  4. 4. Agile Methodologies
  5. 5. The Triple Constraint Waterfall Predictive Process The plan creates cost and schedule estimates Constraints Estimates Scope (requirements) Cost Time Plan Driven Agile Adaptive Process The vision creates feature estimates Cost Time Scope (features) Value Driven When it doesn’t fit in Agile, we cut Scope, not Quality!
  6. 6. 5 Levels of Agile Planning
  7. 7. Agile Testing Touch Points ● Release Planning ○ Document dependencies ○ Write - End to end flow tests ○ Write - Workflow tests ○ Write - Integration tests ○ ● Release Testing ○ Run - End to end flow tests ○ Run - Workflow tests ○ Run - Integration tests ○ Run - Performance and security tests ● Iteration Planning ○ Review - Acceptance criteria ● Iteration Testing ○ Write/Run - Acceptance tests ○ Write/Run - Unit tests ○ Write/Run - Component tests
  8. 8. Agile Testing Quadrant Are we building the right product? Are we building the product right? Business Facing Technology Facing
  9. 9. Agile Testing Quadrant Functional, Story & Prototype Testing Unit & Component Testing Business Facing Technology Facing Exploratory & Usability Testing Performance, Load & Security Testing CritiqueProduct SupportingtheTeam
  10. 10. Agile Quality QA is no longer the Sole Quality Gatekeeper! ● QA may play new role ● Agile Quality requires new skills ● Focuses on Prevention instead of Detection ● Testing role may be done by others ● Testing done upfront ● Automation plays a bigger role ● Focuses on xUnit testing
  11. 11. Up front testing leads to lower costs and better quality
  12. 12. Test FirstTest First Quality focus on Test first vs. Test last Test First Continuous Integration Refactoring Functional Testing Performance Testing
  13. 13. The whole team is responsible for quality Business ● Product Owners / Product Manager ● Subject Matter Experts Technology ● Architects ● Database Administrators ● User Experience Designers ● Operations/Support team members Team ● Developers ● Testers ● Business Analysts
  14. 14. Is incurred by not developing in the correct way... Technical Debt Like Financial Debt - is dangerous if the incurred interest and the debt itself are not payed...
  15. 15. Two ways of doing things! Technical Debt Clean and smart way - takes longer to implement but makes change easier in the future Quick and dirty way - get your features sooner, but make the future changes very hard
  16. 16. Technical Debt “Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite... The danger occurs when the debt is not repaid. Every minute spent on not-quite-right code counts as interest on that debt.” Ward Cunningham (1992-03-26). "The WyCash Portfolio Management System".
  17. 17. ● Loss of Productivity ● Increase in Testing ● Postponed Releases ● Code Duplication ● Low Code Coverage ● Increase in Bugs ● Unreadable Code ● Decreased Velocity ● Using Old Libraries ● Heavy Stress on Approaching Deadlines ● Being Scared of Changing Anything ● Evil Hacks Wrong Design ● Wrong Choice of Technology Symptoms of Technical Debt
  18. 18. Continuous inspection with SonarQube Managing 7 axes of code quality or preventing the Developers' 7 Deadly Sins 1. Potential Bugs 2. No Coding Standards 3. Duplications 4. Lack of Unit Tests 5. Bad Distribution of Complexity 6. Spaghetti Design 7. Not Enough or Too Many Comments Strategic Design 1. Strategic debt intentionally accumulated in a project. 2. Conscious, proactive decisions with larger short term benefits. 3. Focuses on architectural and/or business trade-offs. 4. Forgo’s extensive architecture for increased speed to market or reduced overhead Agile Engineering Practices Pair Programming, TDD, Continuous Integration, Automated Unit Tests, Automated Functional Tests, Automated Other Tests(Regression), Refactoring, Clear Definition of Done Fixing the Technical Debt
  19. 19. The Testing Pyramid Source: Traditional Agile
  20. 20. The DDs... FDD FEATURE Driven Development TDD TEST Driven Development BDD BEHAVIOR Driven Development
  21. 21. FDD - Feature Driven Development ● Is a client-centric, architecture-centric, and pragmatic software process ● Feature Breakdown Structure (FBS) instead of WBS ● A feature is a small, client-valued function expressed in the form: <action> the <result> by/for/of/to a <object>
  22. 22. TDD - Test Driven Development Is a rapid cycle of testing, coding, and refactoring ● Relies on a very short development cycle ● Developer writes automated test case first ● Test case defines desired improvement or new function ● Next develops minimum amount of code to pass test ● Lastly refactors the new code to acceptable standards Code refactoring is a "disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior"
  23. 23. BDD - Behavior Driven Development ● Outside-in and pull-based - Wire-frame > Test Cases > Coding ● Multiple-stakeholder, multiple-scale, high-automation ● Describes a cycle of interactions with well-defined outputs ● Results in the delivery of working, tested software that matters
  24. 24. TDD, BDD and automated testing... TDDBDD TDD invests in automated Unit tests. BDD invests in automated Acceptance tests.
  25. 25. BDD - User Story Traceability ID: 27 STORY NAME: Save a list of potential cars for later review As a: Buyer I can: Add a car to my wish list So that: I can review my top choices at a later time. Acceptance Criteria Scenario 27.1: Add a car to my wish list Given: A potential buyer is logged in And: The car is available for sale When: The ‘Add to Favorites’ option appears And: A buyer flags the car for the wish list Then: The car details are displayed in the wish list Scenario 27.2: Review list of favorite cars Given: A potential buyer is logged in Given: A potential buyer has previously picked some favorite cars’ And: A buyer clicks on “view my favorites’ When: The buyer views the wish list And: The car is still available for sale Then: The buyer can view the car summary in the wish list Story As a <role>, I can <activity>, so that <business value> Scenarios Given <context> When <event> Then <outcome>
  26. 26. Agile Testing Framework (ATF)
  27. 27. Agile Testing Framework Agile Planning Stage ● BDD Tests written in Agile Project Management Tool
  28. 28. Agile Testing Framework Agile Implementation Stage ● BDD Tests Pulled/Run ● Data Driven/Functional Tests written ● Services Tests Run ● CI process run ● Quality, Build Status, Test Results Reported
  29. 29. Agile Testing Framework Agile Regression / Release Stage ● Regression Tests - Selenium/BDD ● Performance Testing - Front End/JVM/Load ● Security Testing ● Web Accessibility Testing ● Web Consistency Testing
  30. 30. Agile Testing Framework Agile Feedback Loop ● Technical Debt Management ● Quality Metrics ● Build Status ● Code Coverage - Unit/Functional ● Test Results ● Code Reviews
  31. 31. © Torak, Inc. Agile, Kanban & DevOps Coaching Learn more at Learn more at Learn more at
  32. 32. This presentation was inspired by the work of many people and we have done our very best to attribute all authors of texts and images, and recognize any copyrights. If you think that anything in this presentation should be changed, added or removed, please contact us.