TestBoss May 2018 - 'How to win with automation and influence people'
•
1 like•295 views
TestBoss creates a unique platform for Test Managers through to Head of Tests across Yorkshire, to debate and discuss hot topics, learn from reputable and established speakers whilst networking with like-minded individuals in an intimate but friendly environment. The Guest Speaker for this presentation was Gwen Diagram, Principal Test Engineer at Sky. The presentation, titled 'How to win with automation and influence people' explains the different layers of testing – and how to sell that idea to not only within the team but outside to senior management as well. If you're a leader within Software Test Management in Yorkshire and would like to find out more about TestBoss, get in touch. Email us at testboss@corecomconsulting.co.uk
Recommended
Recommended
More Related Content
Similar to TestBoss May 2018 - 'How to win with automation and influence people'
Similar to TestBoss May 2018 - 'How to win with automation and influence people' (20)
More from Corecom Consulting
More from Corecom Consulting (20)
Recently uploaded
Recently uploaded (20)
TestBoss May 2018 - 'How to win with automation and influence people'
- 2. Schedule for this evening ● 6.00pm - Networking ● 6.30pm - Welcome and Introduction: Rick Hughes, Corecom Consulting ● 6.40pm – Gwen Diagram, Principal Test Engineer at Sky: “How to win with automation and influence people” ● 7.10pm - Buffet and Refreshments ● 7.40pm - Group Discussions ● 8.30pm - Event close: Refreshments and Networking www.corecomconsulting.co.uk
- 3. How to win with automation and influence people Gwen Diagram @gwendiagram Tester Principal Test Engineer Sky
- 4. About me
- 5. How to win friends and influence people - Dale Carnegie
- 6. An interview
- 7. What automation frameworks were used
- 9. It sounded like a mess
- 10. But it was worse than it sounded
- 11. The front end team
- 12. It was a world of Groovy
- 14. Functional tests – that covered a lot of layers
- 15. Integration tests – duplicated functional
- 16. Slow and flakey tests
- 17. Rerunning for a build was common
- 18. BDD Frameworks inside BDD frameworks
- 19. Unloved tests
- 20. No idea how the code worked
- 22. THIS IS SO BORING, LET US CODE
- 23. Everyone thinks their language is the best
- 24. We needed a framework everyone would use
- 25. Throw down a challenge - Dale Carnegie
- 27. A fair chance
- 28. That wasn’t that fair at all
- 29. Merely stating a truth isn’t enough. The truth has to be made vivid, interesting, dramatic. You have to use showmanship. The movies do it. Television does it. And you will have to do it if you want attention. - Dale Carnegie
- 30. Gauge
- 31. The only way I can get you to do anything is by giving you what you want. - Dale Carnegie
- 32. Reporting
- 34. Arouse in the other person an eager want. - Dale Carnegie
- 35. The testers were writing code
- 36. Smoke tests were the least of our worries
- 37. Regression testing was still two days
- 38. The Jbehave and Serenity tests were huge
- 39. It wouldn’t benefit the whole team
- 40. The API Acceptance Tests
- 41. More of a solo endeavour
- 42. Don’t choose technology as a solo - Me.
- 43. Use cases differed for components { "class":["order"], "properties":{ "orderNumber":42, "itemCount":3, "status":"pending" }, "entities":[ { "class":["items","collection"], "rel":["http://x.io/rels/order-items" ], "href": "http://api.x.io/orders/42/items" }, { "class":["info","customer"], "rel":["http://x.io/rels/customer"], "properties":{ "customerId":"pj123", "name":"PeterJoseph" }, "links":[ {"rel":["self"],"href": "http://api.x.io/customers/pj123"} ] } ], "actions":[ { "name":"add-item", "title":"AddItem", "method":"POST", "href": "http://api.x.io/orders/42/items", "type":"application/x-www-form- urlencoded", "fields":[ {"name":"orderNumber","type": "hidden","value":"42"}, {"name":"productCode","type": "text"}, {"name":"quantity","type":"number" } ] } ], "links":[ {"rel":["self"],"href": "http://api.x.io/orders/42"}, {"rel":["previous"],"href": "http://api.x.io/orders/41"}, {"rel":["next"],"href": "http://api.x.io/orders/43"} ] }
- 44. We didn’t plan ahead so we diverged JsonPath Gson Jackson
- 45. So we’ll need to replace it entirely
- 46. The only way to get the best of an argument is to avoid it. - Dale Carnegie
- 47. Let go Lawyer up, delete Facebook, hit the gym
- 48. Tech radar
- 49. Find out what’s cool at the moment
- 50. We review tech choices as a team
- 51. Tech trying to sneak in can be rejected
- 52. Don’t worry, I hadn’t forgotten unit tests
- 53. Some devs hadn’t written them before
- 54. Talk in terms of the other person's interest. - Dale Carnegie
- 56. Make what a unit is clear Unit tests should cover isolated bits of code. If code is inherited from another class, do not test that class in the inheritance. Component tests should cover this. Derived classes we are just testing changed code.
- 58. Code reviews ensured we had unit tests
- 61. We had two testers on it
- 62. And then we had none
- 63. Component teams weren’t working
- 66. And a new development manager
- 67. I was the only senior left
- 68. Feature squads
- 69. Let the other person feel the idea is his or hers. - Dale Carnegie
- 70. Story Kick Offs Integration of Story / Feature to DoD Events Planning Definition of Ready to Spin Up Feature Squad Product Team make decision of whether a feature should be created Work Intake Board Appropriate Dev Squad members estimate the work required for completing a Feature Initial Solution Architecture / Design Ready for Estimation PO, PE, PE, SA, TA, BA, Ops, Devs Feature Squad Planning Feature Squads Tribe / Chapter Spin Down Feature Squad Hedgehog Squad NFT Ops SA PE SM Idea Spin Down Dev’sreadyfornextFeature ReadyforAnalysis ReadyforApprovalDecision AnalysisComplete New • Feature • Epic • Idea First Look • Feature Analysis • Feature Approved • Feature Doing • Feature Production • Feature Daily Stand-ups Scrum of Scrums Review / Showcase Big Retro / Squad Retro PO
- 71. Working groups
- 72. Dramatise your ideas. - Dale Carnegie
- 73. This calls for the Beastie Boys
- 75. Infomercials know how to sell shit
- 76. The structure I followed for this was • Statement of what the problem is • Proposal of the solution • Testimonials • Concerns of the proposed solution and how the solution takes cares of the concerns • Repetition of the solution
- 77. Everyone knew it was a sales pitch
- 78. Speaking to upper management
- 79. Testing is an expensive waste of time
- 80. You can make more friends in two months by becoming interested in other people than you can in two years by trying to get other people interested in you. - Dale Carnegie
- 81. We had an hour
- 82. Make the other person feel important – and do it sincerely. - Dale Carnegie
- 83. People like cake
- 84. Actions speak louder than words, and a smile says, ‘I like you. You make me happy. I am glad to see you.” - Dale Carnegie
- 85. Make them feel welcome
- 86. Remember that a person's name is, to that person, the sweetest and most important sound in any language. - Dale Carnegie
- 87. Say their name
- 88. They left happy
- 89. And here was Identity’s test strategy
- 90. Identity’s Test Strategy Gwen Diagram, Identity Tribe
- 91. Why test?
- 92. Confidence
- 94. Always available
- 95. Delivering what you want
- 96. Always available, frictionless and secure
- 97. Deployed quickly with known quality
- 98. A journey driven solution
- 99. But really, why test?
- 100. The stability of the platform affects the team
- 101. How do we create a strong and stable system?
- 102. How Identity test
- 103. The Testing Pyramid as a Bug Filter Inspired by Noah Sussman’s Band-Pass Filter
- 104. Unit
- 105. Component
- 106. Integration
- 107. Acceptance
- 108. End to End
- 109. Exploratory
- 110. Making our tribe excellent through support and learning
- 111. Constant learning
- 112. Pairing
- 113. Mentoring
- 114. Creating an internal community
- 115. Increasing team capability Wheel of Testing credited to Ash Winter
- 116. Thank you Especially to Noah Sussman for the testing cone concept and Ash Winter for his Wheel of Testing
- 117. Any questions? Should I brush my cat’s teeth?
- 120. www.corecomconsulting.co.uk Discussion 1: “How do you attract good Technical Testers to your business with a limited budget?”
- 123. www.corecomconsulting.co.uk Discussion 2: “As a Test Manager, how do you effectively measure your test teams’ performance both collectively and individually?”
- 125. www.corecomconsulting.co.uk Discussion 3: “How can we best fit in Performance/Load testing into ever shrinking Agile delivery cycles?”
- 128. www.corecomconsulting.co.uk Discussion 4: “How do you drive Automation forward when it is new to the business?”