Impact of Testing

Add by Ash Winter | Jun 29, 2016 21:08  485 |  43
Impact of Testing
Download

Map Outline

Impact of Testing
1 What is the value of a tester?
1.1 Exploring risk helps stakeholders make decisions
1.1.1 What to build
1.1.2 What not to build
1.1.3 How to build
1.1.4 What has been built
1.1.5 Whether problems have been solved
1.2 Introducing testability benefits the
1.2.1 Team
1.2.1.1 Collaboration
1.2.1.2 Conversation
1.2.1.3 Shared vision
1.2.2 Product
1.2.2.1 Observable
1.2.2.2 Controllable
1.2.2.3 Explicit Knowledge
1.2.3 Operations
1.2.3.1 Maintainable
1.2.3.2 Collaborative
1.2.3.3 Is Devops!
1.3 Thinking at scale
1.3.1 In the age of Ticket by Ticket syndrome
1.3.1.1 Small teams on small items may lead to small thinking about big risks
1.3.2 This appears to work here but what about?
1.3.2.1 Next door?
1.3.2.2 Adjcaent systems
1.3.2.3 On 100 webservers?
1.4 Challenging
1.4.1 Is that best practice whats needed here?
1.4.2 Well the system appears to do X from the point of view of my tests, but it takes 30 seconds, that OK?
1.4.3 Is the problem solved by the solution?
2 What are testers accountable for?
2.1 Having
2.1.1 A PARADIGM OF TESTING
2.1.2 KNOWLEDGE THEY ARE NOT RESPONSIBLE FOR QUALITY
2.1.3 APPRECIATION THAT THE INFINITY OF TESTING IS A STRENGTH
2.2 Their own learning
2.2.1 Personal journey
2.2.1.1 Technology
2.2.1.2 Thinking
2.2.1.3 Questioning skills
2.2.1.4 Communication skills
2.2.1.5 Testing skills
2.3 Sharing their learning
2.3.1 With each other
2.3.2 With those in different disciplines
2.3.3 Outside of their organisations
2.3.4 Community focused
2.3.4.1 internal
2.3.4.1.1 sharing and refinement
2.3.4.2 external
2.3.4.2.1 new ideas
2.4 Enabling testing as an activity
2.4.1 Advocating testing to all
2.4.2 Giving and receiving advice
2.4.3 Making product and testing models apparent
2.5 Performing testing
2.5.1 Focus on performance not artifacts
2.5.2 Finding problems that matter
2.5.3 Showing their findings to those who matter
2.5.4 Knowing who matters
2.5.5 Telling a compelling testing story
3 Whats your opinion on the future of testers?
3.1 Process (as opposed to skill) based testing will reduce
3.1.1 Testers as administrators
3.1.2 Testers who do not improve themselves
3.1.3 Testers without a delivery focus
3.1.4 Organisation wide test strategies will diminish
3.1.4.1 Context will become the new normal
3.1.4.2 Ability to build context sensitive strategies
3.2 Testers will become more technologically aware
3.2.1 This does not mean they will neccesarily code
3.2.2 This may mean they understand technology
3.2.2.1 Strengths
3.2.2.2 Weaknesses
3.2.2.3 How we allow it to fool us
3.3 Fewer testers
3.3.1 Tactical and surgical
3.3.1.1 Coach
3.3.1.2 Guide
3.3.1.3 Strategise
3.3.1.4 Facilitate
3.3.2 More skilled and with legitimate expertise
3.3.2.1 See process driven
3.3.3 Less big 'consultancy'
3.3.3.1 Testers gets more skilful and legitimate
3.3.3.2 Less of a disposable mindset
3.3.3.3 Consultants will need to make a difference, not just reflect the clients thinking
3.3.3.3.1 Try something else?
3.4 Community OVER organisations
3.4.1 The great questions around testing will not be solved by organisations
3.4.1.1 Too much conflict of commercial interest
3.4.2 Community is best placed to drive debate
3.5 Testing is Dead?
3.5.1 Similar to saying 'thinking is dead'
3.5.1.1 Which may be true in some organisations
3.5.2 Devops?
3.5.2.1 Deploying 100 times a day?
3.5.2.1.1 Still need information on risk to determine if its worth deploying
4 About
4.1 Authored by Ash Winter
4.2 29th Day of June, 2016
4.3 Prepared in Ilkley, West Yorkshire
4.4 Discussion in Leeds, West Yorkshire
4.5 Thoughts captured before an 'Impact of Testing' round table discussion
4.6 Motivation: Step out of my bubble, peek into the mind of the local testing scene
4.7 Participants - Directors and managers over active testing practitioners

More Maps From User