GDS timeline and testing approach
•
0 j'aime•51 vues
This document summarizes the early history and development of the Government Digital Service (GDS) in the UK. It discusses how GDS was set up to create a single government domain (GOV.UK) and transform government services. It describes the initial split into "mainstream" and "inside government" work streams. It provides a timeline of departments that transitioned to GOV.UK between 2012-2013. It also discusses features of the platform, technical challenges around testing, and how adopting a service object pattern improved testability and code design.
Recommandé
Recommandé
Contenu connexe
Similaire à GDS timeline and testing approach
Similaire à GDS timeline and testing approach (20)
Plus de David Heath
Plus de David Heath (6)
Dernier
Dernier (20)
GDS timeline and testing approach
- 1. GDS David Heath David Heath Developer Government Digital Service @dgheath21
- 3. GDS David Heath Directgov 2010 and Beyond: Revolution Not Evolution GDS David Heath
- 4. Set up GDS Single domain Transform services Go wholesale GDS David Heath
- 5. Set up GDS Single domain Transform services Go wholesale GDS David Heath
- 7. GDS David Heath Early split into two work-streams 7
- 8. GDS David Heath Early split into two work-streams “Mainstream” 8
- 9. GDS David Heath Early split into two work-streams “Mainstream” Citizen-facing 9
- 10. GDS David Heath Early split into two work-streams “Mainstream” Citizen-facing Top 1000 user needs 10
- 11. GDS David Heath Early split into two work-streams “Mainstream” Citizen-facing Top 1000 user needs Directgov search logs 11
- 14. GDS David Heath “Inside Government” For specialists and policy makers 14
- 15. GDS David Heath “Inside Government” For specialists and policy makers 25 orgs 100k documents 15
- 16. GDS David Heath Vision: Don’t need to know the structure of government to fi nd what you need 16
- 21. GDS David Heath Feb 2012 - Inside Gov Beta 21
- 22. GDS David Heath Feb 2012 - Inside Gov Beta May 2012 - Dev work starts 22
- 23. GDS David Heath Feb 2012 - Inside Gov Beta May 2012 - Dev work starts Oct 2012 - GOV.UK mainstream live 23
- 24. GDS David Heath Feb 2012 - Inside Gov Beta May 2012 - Dev work starts Oct 2012 - GOV.UK mainstream live Nov 2012 - DfT, DCLG 24
- 27. GDS David Heath Feb 2012 - Inside Gov Beta May 2012 - Dev work starts Oct 2012 - GOV.UK mainstream live Nov 2012 - DfT, DCLG Dec 2012 - MoD, FCO, BIS, AGO 27
- 28. GDS David Heath Feb 2012 - Inside Gov Beta May 2012 - Dev work starts Oct 2012 - GOV.UK mainstream live Nov 2012 - DfT, DCLG Dec 2012 - MoD, FCO, BIS, AGO Jan 2013 - DECC, Scotland of fi ce 28
- 29. GDS David Heath Feb 2012 - Inside Gov Beta May 2012 - Dev work starts Oct 2012 - GOV.UK mainstream live Nov 2012 - DfT, DCLG Dec 2012 - MoD, FCO, BIS, AGO Jan 2013 - DECC, Scotland of fi ce Feb 2013 - Cabinet of fi ce (plus Commons Lords of fi ce) 29
- 30. GDS David Heath Feb 2012 - Inside Gov Beta May 2012 - Dev work starts Oct 2012 - GOV.UK mainstream live Nov 2012 - DfT, DCLG Dec 2012 - MoD, FCO, BIS, AGO Jan 2013 - DECC, Scotland of fi ce Feb 2013 - Cabinet of fi ce (plus Commons Lords of fi ce) Feb 2013 - FCO travel services 30
- 31. GDS David Heath Feb 2012 - Inside Gov Beta May 2012 - Dev work starts Oct 2012 - GOV.UK mainstream live Nov 2012 - DfT, DCLG Dec 2012 - MoD, FCO, BIS, AGO Jan 2013 - DECC, Scotland of fi ce Feb 2013 - Cabinet of fi ce (plus Commons Lords of fi ce) Feb 2013 - FCO travel services Mar 2013 - DfID, DoH, HO, Wales of fi ce 31
- 32. GDS David Heath Feb 2012 - Inside Gov Beta May 2012 - Dev work starts Oct 2012 - GOV.UK mainstream live Nov 2012 - DfT, DCLG Dec 2012 - MoD, FCO, BIS, AGO Jan 2013 - DECC, Scotland of fi ce Feb 2013 - Cabinet of fi ce (plus Commons Lords of fi ce) Feb 2013 - FCO travel services Mar 2013 - DfID, DoH, HO, Wales of fi ce Apr 2013 - Defra, MOJ, DWP, DfE HMT 32
- 35. GDS David Heath Features Bulk document import 35
- 36. GDS David Heath Features Bulk document import Iterating admin work fl ow 36
- 37. GDS David Heath Features Bulk document import Iterating admin work fl ow - Scheduled publishing 37
- 38. GDS David Heath Features Bulk document import Iterating admin work fl ow - Scheduled publishing Iterating the navigation and design 38
- 39. GDS David Heath Features Bulk document import Iterating admin work fl ow - Scheduled publishing Iterating the navigation and design Filter pages 39
- 40. GDS David Heath Features Bulk document import Iterating admin work fl ow - Scheduled publishing Iterating the navigation and design Filter pages Email alerts 40
- 41. GDS David Heath Features Bulk document import Iterating admin work fl ow - Scheduled publishing Iterating the navigation and design Filter pages Email alerts Organisations 41
- 42. GDS David Heath Features Bulk document import Iterating admin work fl ow - Scheduled publishing Iterating the navigation and design Filter pages Email alerts Organisations - corporate information 42
- 43. GDS David Heath Features Bulk document import Iterating admin work fl ow - Scheduled publishing Iterating the navigation and design Filter pages Email alerts Organisations - corporate information - featuring 43
- 44. GDS David Heath 12 months 16 contributors 6,598 commits added 123k lines of ruby removed 63k lines of ruby 44
- 46. GDS David Heath No time to refactor 46
- 47. GDS David Heath Changing personnel with different approaches/styles 47
- 49. GDS David Heath Consequences - tech debt 49
- 50. GDS David Heath Consequences - tech debt - slow test suite 50
- 51. GDS David Heath Slow test suite - 45 mins on dev machines 51
- 52. GDS David Heath “ fi xes” - branch building on travis - parallel builds on travis - bigger CI box - branch builds on our CI 52
- 54. GDS David Heath Test/unit, rails “functional” tests, cucumber, phantomjs 54
- 55. GDS David Heath 55 Rails STI
- 57. GDS David Heath Debates about testing style 57
- 58. GDS David Heath Position 1 - - rails functional tests are effective, pragmatic, powerful tests - cucumber is a complicated and unnecessary abstraction 58
- 59. GDS David Heath Position 2 - - no advantage of functional tests over integration tests - cucumber is great and every new feature should have cucumber coverage 59
- 60. GDS David Heath How I think about testing 60
- 62. GDS David Heath Javascript HTML Views/templates Controllers Services Models Database 62 Testing layers JS unit test
- 65. GDS David Heath Javascript HTML Views/templates Controllers Services Models Database 65 Testing layers Heavily stubbe d functional test
- 67. GDS David Heath Javascript HTML Views/templates Controllers Services Models Database 67 Testing layers Cucumber with @javascript tag
- 69. GDS David Heath 69 not man y of these mostly these
- 70. GDS David Heath But I was fi nding this really hard in Rails... 70
- 71. GDS David Heath ... I must be a really rubbish programmer 71
- 72. GDS David Heath Rich Hickey to the rescue! .. “Simple made easy” QCcon March 2012 72
- 73. GDS David Heath Complexity is the enemy 73
- 74. GDS David Heath Complexity is the enemy good software design allows us to reason about code and makes it testable 74
- 75. GDS David Heath Rails conventions followed unthinkingly can lead to poor design - coupled database, models, controllers and views Bob Martin - “Architecture, the lost years” 75
- 76. GDS David Heath How did we apply these insights? 76
- 77. GDS David Heath Service object pattern 77
- 78. GDS David Heath Before Edition#after_publish hook sends email noti fi cation 78
- 79. GDS David Heath After EditionPublisher - given an edition - call #perform - observers trigger other actions such as email noti fi cation 79
- 80. GDS David Heath Advantages - can unit test EditionPublisher and email noti fi cations separately 80
- 83. GDS David Heath Before: edition publishes itself
- 84. GDS David Heath Publishing operation in mixin
- 89. GDS David Heath
- 90. GDS David Heath
- 93. GDS David Heath Win! - reduced controller and model complexity 93
- 94. GDS David Heath Win! - reduced controller and model complexity - publisher and listeners independently testable 94
- 96. GDS David Heath If your code is hard to test in isolation... 96
- 97. GDS David Heath If your code is hard to test in isolation... ...your software design can be improved 97
- 98. GDS David Heath Rails conventions do not encourage isolated designs 98
- 99. GDS David Heath Rails conventions do not encourage isolated designs ...to achieve good software design, you need to study and thoughtfully apply it 99
- 100. GDS David Heath Single responsibility Open/close Liskov substitution Interface segregation Dependency inversion See Bob Martin “Clean Code” 100
- 101. GDS David Heath Some patterns which help: 101
- 102. GDS David Heath Some patterns which help: - service objects 102
- 103. GDS David Heath Some patterns which help: - service objects - repository 103
- 104. GDS David Heath Some patterns which help: - service objects - repository - dependency injection 104
- 105. GDS David Heath Some patterns which help: - service objects - repository - dependency injection - “hexagonal” architecture (isolate business logic from app framework) 105
- 106. GDS David Heath Accumulating tech debt is sometimes appropriate to achieve business goals 106
- 107. GDS David Heath 107
- 108. GDS David Heath Challenge is to make tech debt visible business decision makers... 108
- 109. GDS David Heath Challenge is to make tech debt visible business decision makers... ...developers see the costs every day, they don’t 109
- 110. GDS David Heath We’re hiring! ... developers, webops, etc https://gds.blog.gov.uk/jobs 110
- 112. GDS David Heath David Heath Developer Government Digital Service @dgheath21