Agile Testing Days 2012 - Lean Mean BDD Automation Machine

  • 591 views
Uploaded on

Agile Testing Days 2012 Presentation from Mike Scott & Tom Roden

Agile Testing Days 2012 Presentation from Mike Scott & Tom Roden

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
591
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
13
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Building a lean, mean, BDDautomation machineMike Scott & Tom Roden@MikeAScott @TomMRodenAgile Testing Days20 November 2012Potsdam, GermanySQS Group Limited
  • 2. Caption CompetitionCaption Competition 2
  • 3. Safia– Archetypes and Templates, a voyage in automating acceptanceA story about building an executable documentation system • Large hedge fund COTS Born out of implementation necessity • Crippling regression test burden • 6-8 month cycle  daily release Results: • 80 times defect reduction • and again Then did it • Same patterns automation again… platform 3
  • 4. Real data from the fieldThe problem quantified Time taken for Release Regression testing 120 700 100 601 600 100 545 500 80 479 78 Man Days Effort 67.5 393 400 # Test Suites 371 60 311 300 284 40 40 217 200 151 106 20 23 15 100 64 12 28 25 5 0 0 0 3 0 0 February April August November February April May June July August Month Man Days Effort for Regression Test # Test Suites # Automated Suites 4
  • 5. Where it came fromThe confidence problem! First Approach to Acceptance Testing: UAT in a phase, after a period of development 5
  • 6. 6
  • 7. What it felt like… 7
  • 8. Building Integrity inBecoming acceptance driven… Ready User Backlog Specify tests Story / examples Automate acceptance Develop Demo / tests Showcase Session Customer Based Verification Testing Stakeholder(s) & BA Developers Testers 8
  • 9. Real data from the fieldThe initial effect of automated acceptance testing Time taken for Release Regression testing 120 700 100 601 600 100 545 500 80 479 78 Man Days Effort 67.5 393 400 # Test Suites 371 60 311 300 284 40 40 217 200 151 106 20 23 15 100 64 12 28 25 5 0 0 0 3 0 0 February April August November February April May June July August Month Man Days Effort for Regression Test # Test Suites # Automated Suites 9
  • 10. What we gained from thisKnowledge and experience to design a framework A set of design patterns • binding tests to investment apps Inject knowledge • from business specialists Vanilla acceptance tests • easy to customise Living documentation • tests as specifications 10
  • 11. How Safia WorksIllogical Architecture Diagram Fitnesse fixtures Maps SAFIA terminology to system terminology Safia fixtures e.g. Calypso, Beauchamps, SummitMaps investment house House Systemterminology to SAFIA Adaptor Adaptorterminology e.g.Trade Capture = Trade Entry API Trading system SAFIA automates at the server level via the API 11
  • 12. How Safia WorksCreating automated test cases using Safia e.g. Run a P&L report e.g. Update a legal entity FX, Bond, Equities Amend SDI IRS, FRA, CDS Test Archetype Instrument Amend fees “Test Function” Template Create a trade IRS template Apply Template & Archetype Test Create a valid IRS trade 12
  • 13. DemoLet’s put it to the test 13
  • 14. Why use a framework like thisIt brings benefits on different levels Increased collaboration Reduced Cost of Ownership Accelerating implementation & learning Benefits Teaching & coaching aid Anyone can interact with it 14
  • 15. In retrospect…It was easy, right? 15
  • 16. Real data from the fieldThe path to faster release Time taken for Release Regression testing 120 700 100 601 600 100 545 500 80 479 78 Man Days Effort 67.5 393 400 # Test Suites 371 60 311 300 284 40 40 217 200 151 23 20 106 15 100 64 12 28 25 5 0 3 0 0 0 0 February April August November February April May June July August Month Man Days Effort for Regression Test # Test Suites # Automated Suites 16
  • 17. How we wrote the testsTests as specs, the principles of test design Self-documenting Based on testable statements About business intentions What makes a good acceptance test? Anyone can understand it Concise and A specification granular not a script 17
  • 18. Reducing the Cost of Ownership~One third is system understanding 18
  • 19. Points to consider when automating Theory ‘aint practice Start early & iterate frequently Distil and simplify Tests or Documentation? DON’T PANIC !!! 19
  • 20. “Brace yourself Daphne…” 20
  • 21. Thank you for listeningQuestions Please evaluate our presentation by using the evaluation booklets which you can find in your conference bag. Thank you! 21
  • 22. Mike Scott & Tom Rodenmike.scott@sqs.comtom.roden@sqs.comSQS Group Limited7-11 Moorgate, London EC2R 6AFInternet: www.sqs.comSQS Group Limited