際際滷shows by User: AshWinter / http://www.slideshare.net/images/logo.gif 際際滷shows by User: AshWinter / Sun, 12 Dec 2021 15:26:45 GMT 際際滷Share feed for 際際滷shows by User: AshWinter Testability Advocacy Canvas /slideshow/testability-coaching-canvas-250825632/250825632 testabilitycoachingcanvas-211212152645
A coaching aid for those who want to help others achieve greater testability within their development team and wider organisation. Additionally can be used to track your own journey.]]>
A coaching aid for those who want to help others achieve greater testability within their development team and wider organisation. Additionally can be used to track your own journey.]]> Sun, 12 Dec 2021 15:26:45 GMT /slideshow/testability-coaching-canvas-250825632/250825632 AshWinter@slideshare.net(AshWinter) Testability Advocacy Canvas AshWinter A coaching aid for those who want to help others achieve greater testability within their development team and wider organisation. Additionally can be used to track your own journey. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testabilitycoachingcanvas-211212152645-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> A coaching aid for those who want to help others achieve greater testability within their development team and wider organisation. Additionally can be used to track your own journey.
Testability Advocacy Canvas from Ash Winter
]]> 1150 0 https://cdn.slidesharecdn.com/ss_thumbnails/testabilitycoachingcanvas-211212152645-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Testability Sales Pitch /AshWinter/testability-sales-pitch-232256929 salespitchtomanagers-200419140904
Testability can make our testing lives so much better. But we need to sell it to those who can pay for the changes needed. Find out what they need (delivery, flow, stability, resilience), how it can be measured the use the handy examples below! ]]>
Testability can make our testing lives so much better. But we need to sell it to those who can pay for the changes needed. Find out what they need (delivery, flow, stability, resilience), how it can be measured the use the handy examples below! ]]> Sun, 19 Apr 2020 14:09:04 GMT /AshWinter/testability-sales-pitch-232256929 AshWinter@slideshare.net(AshWinter) Testability Sales Pitch AshWinter Testability can make our testing lives so much better. But we need to sell it to those who can pay for the changes needed. Find out what they need (delivery, flow, stability, resilience), how it can be measured the use the handy examples below! <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/salespitchtomanagers-200419140904-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Testability can make our testing lives so much better. But we need to sell it to those who can pay for the changes needed. Find out what they need (delivery, flow, stability, resilience), how it can be measured the use the handy examples below!
Testability Sales Pitch from Ash Winter
]]> 659 0 https://cdn.slidesharecdn.com/ss_thumbnails/salespitchtomanagers-200419140904-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Architectural Testability Workshop for Test Academy Barcelona /slideshow/architectural-testability-workshop-for-test-academy-barcelona/226249273 workshop-200130214856
Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model. ]]>
Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model. ]]> Thu, 30 Jan 2020 21:48:56 GMT /slideshow/architectural-testability-workshop-for-test-academy-barcelona/226249273 AshWinter@slideshare.net(AshWinter) Architectural Testability Workshop for Test Academy Barcelona AshWinter Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/workshop-200130214856-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model.
Architectural Testability Workshop for Test Academy Barcelona from Ash Winter
]]> 258 0 https://cdn.slidesharecdn.com/ss_thumbnails/workshop-200130214856-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Testability Squad Health Check /slideshow/testability-squad-health-check/197949998 testability-squad-health-check-model-191126145009
Based on the Spotify Squad Health Check and the 10 P's of Testability model by Robert Meaney, a means of seeing how your testable your products are. ]]>
Based on the Spotify Squad Health Check and the 10 P's of Testability model by Robert Meaney, a means of seeing how your testable your products are. ]]> Tue, 26 Nov 2019 14:50:09 GMT /slideshow/testability-squad-health-check/197949998 AshWinter@slideshare.net(AshWinter) Testability Squad Health Check AshWinter Based on the Spotify Squad Health Check and the 10 P's of Testability model by Robert Meaney, a means of seeing how your testable your products are. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testability-squad-health-check-model-191126145009-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Based on the Spotify Squad Health Check and the 10 P&#39;s of Testability model by Robert Meaney, a means of seeing how your testable your products are.
Testability Squad Health Check from Ash Winter
]]> 681 0 https://cdn.slidesharecdn.com/ss_thumbnails/testability-squad-health-check-model-191126145009-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Testability is Everyone's Responsibility /slideshow/testability-is-everyones-responsibility/169542383 testabilityiseveryonesresponsibilityv4-190906143924
Testability is a first class concern for all disciplines within software development. There, I said it. No hedging, no nebulous phrasing, maybes or it depends. Too often we labour under systems that are hard to test, manifesting themselves with frantic searches for more testers, lengthy acceptance test runs, fearful testing for regressions with a hopeful release at the end. Worst of all, it usually ends up with a project manager sat on the testers desk asking 'when will testing be done.' It's never done, it can only stop, just so you know. Throughout my career, often the testability of a system has been deemed to be the testers concern. If something was hard to test, then it was the testers problem. However, the causes of low testability effect the activities of all disciplines, whether it be speed of feedback to developers or flow of value generating features for product managers. During the talk, we will cover: * How testability is a key advantage in building systems of ever increasing complexity. * Why it's important for developers and operational stakeholders to build inherently testable systems. * What testers can do to be catalysts for testability improvements. The activity of testing is rarely the bottleneck, how testable your system is is your problem. Poor testability cannot be remedied by one discipline alone. It's for all of us to care about.]]>
Testability is a first class concern for all disciplines within software development. There, I said it. No hedging, no nebulous phrasing, maybes or it depends. Too often we labour under systems that are hard to test, manifesting themselves with frantic searches for more testers, lengthy acceptance test runs, fearful testing for regressions with a hopeful release at the end. Worst of all, it usually ends up with a project manager sat on the testers desk asking 'when will testing be done.' It's never done, it can only stop, just so you know. Throughout my career, often the testability of a system has been deemed to be the testers concern. If something was hard to test, then it was the testers problem. However, the causes of low testability effect the activities of all disciplines, whether it be speed of feedback to developers or flow of value generating features for product managers. During the talk, we will cover: * How testability is a key advantage in building systems of ever increasing complexity. * Why it's important for developers and operational stakeholders to build inherently testable systems. * What testers can do to be catalysts for testability improvements. The activity of testing is rarely the bottleneck, how testable your system is is your problem. Poor testability cannot be remedied by one discipline alone. It's for all of us to care about.]]> Fri, 06 Sep 2019 14:39:24 GMT /slideshow/testability-is-everyones-responsibility/169542383 AshWinter@slideshare.net(AshWinter) Testability is Everyone's Responsibility AshWinter Testability is a first class concern for all disciplines within software development. There, I said it. No hedging, no nebulous phrasing, maybes or it depends. Too often we labour under systems that are hard to test, manifesting themselves with frantic searches for more testers, lengthy acceptance test runs, fearful testing for regressions with a hopeful release at the end. Worst of all, it usually ends up with a project manager sat on the testers desk asking 'when will testing be done.' It's never done, it can only stop, just so you know. Throughout my career, often the testability of a system has been deemed to be the testers concern. If something was hard to test, then it was the testers problem. However, the causes of low testability effect the activities of all disciplines, whether it be speed of feedback to developers or flow of value generating features for product managers. During the talk, we will cover: * How testability is a key advantage in building systems of ever increasing complexity. * Why it's important for developers and operational stakeholders to build inherently testable systems. * What testers can do to be catalysts for testability improvements. The activity of testing is rarely the bottleneck, how testable your system is is your problem. Poor testability cannot be remedied by one discipline alone. It's for all of us to care about. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testabilityiseveryonesresponsibilityv4-190906143924-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Testability is a first class concern for all disciplines within software development. There, I said it. No hedging, no nebulous phrasing, maybes or it depends. Too often we labour under systems that are hard to test, manifesting themselves with frantic searches for more testers, lengthy acceptance test runs, fearful testing for regressions with a hopeful release at the end. Worst of all, it usually ends up with a project manager sat on the testers desk asking &#39;when will testing be done.&#39; It&#39;s never done, it can only stop, just so you know. Throughout my career, often the testability of a system has been deemed to be the testers concern. If something was hard to test, then it was the testers problem. However, the causes of low testability effect the activities of all disciplines, whether it be speed of feedback to developers or flow of value generating features for product managers. During the talk, we will cover: * How testability is a key advantage in building systems of ever increasing complexity. * Why it&#39;s important for developers and operational stakeholders to build inherently testable systems. * What testers can do to be catalysts for testability improvements. The activity of testing is rarely the bottleneck, how testable your system is is your problem. Poor testability cannot be remedied by one discipline alone. It&#39;s for all of us to care about.
Testability is Everyone's Responsibility from Ash Winter
]]> 199 0 https://cdn.slidesharecdn.com/ss_thumbnails/testabilityiseveryonesresponsibilityv4-190906143924-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Testers Guide to the Illusions of Unit Testing /slideshow/testers-guide-to-the-illusions-of-unit-testing/164376860 testersguidetotheillusionsofunittesting-190816205319
One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour. To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus. This is a topic that has always intrigued me, having predominantly worked as a single tester on a team for the last five or so years. I reached out to the community with the question What do testers believe about unit testing? and received a lot of engagement. The good users of Twitter added another 50 or so illusions that testers might have about this layer of testing. I figured that based on that level of engagement, maybe this would make an interesting talk! It wasnt only testers who responded too, suggesting that there might be some shared illusions about unit testing that are cross disciplinary. The list alone is interesting but now I would like to share my analysis of it with you, focusing on: * Recurring themes within the list and how to address them as a tester or developer. * Particular illusions to look out for with examples from my recent past. * A guide for developers to engage with testers on unit testing, and testers with developers.]]>
One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour. To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus. This is a topic that has always intrigued me, having predominantly worked as a single tester on a team for the last five or so years. I reached out to the community with the question What do testers believe about unit testing? and received a lot of engagement. The good users of Twitter added another 50 or so illusions that testers might have about this layer of testing. I figured that based on that level of engagement, maybe this would make an interesting talk! It wasnt only testers who responded too, suggesting that there might be some shared illusions about unit testing that are cross disciplinary. The list alone is interesting but now I would like to share my analysis of it with you, focusing on: * Recurring themes within the list and how to address them as a tester or developer. * Particular illusions to look out for with examples from my recent past. * A guide for developers to engage with testers on unit testing, and testers with developers.]]> Fri, 16 Aug 2019 20:53:19 GMT /slideshow/testers-guide-to-the-illusions-of-unit-testing/164376860 AshWinter@slideshare.net(AshWinter) Testers Guide to the Illusions of Unit Testing AshWinter One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour. To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus. This is a topic that has always intrigued me, having predominantly worked as a single tester on a team for the last five or so years. I reached out to the community with the question What do testers believe about unit testing? and received a lot of engagement. The good users of Twitter added another 50 or so illusions that testers might have about this layer of testing. I figured that based on that level of engagement, maybe this would make an interesting talk! It wasnt only testers who responded too, suggesting that there might be some shared illusions about unit testing that are cross disciplinary. The list alone is interesting but now I would like to share my analysis of it with you, focusing on: * Recurring themes within the list and how to address them as a tester or developer. * Particular illusions to look out for with examples from my recent past. * A guide for developers to engage with testers on unit testing, and testers with developers. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testersguidetotheillusionsofunittesting-190816205319-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour. To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus. This is a topic that has always intrigued me, having predominantly worked as a single tester on a team for the last five or so years. I reached out to the community with the question What do testers believe about unit testing? and received a lot of engagement. The good users of Twitter added another 50 or so illusions that testers might have about this layer of testing. I figured that based on that level of engagement, maybe this would make an interesting talk! It wasnt only testers who responded too, suggesting that there might be some shared illusions about unit testing that are cross disciplinary. The list alone is interesting but now I would like to share my analysis of it with you, focusing on: * Recurring themes within the list and how to address them as a tester or developer. * Particular illusions to look out for with examples from my recent past. * A guide for developers to engage with testers on unit testing, and testers with developers.
Testers Guide to the Illusions of Unit Testing from Ash Winter
]]> 217 4 https://cdn.slidesharecdn.com/ss_thumbnails/testersguidetotheillusionsofunittesting-190816205319-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 10 P's of Testability /slideshow/10-ps-of-testability/164088035 10pstestability-190815173533
Lightning talk based on the 10 P's of Testability by Robert Meaney, talk designed by Ash Winter. Make your testing life better by embrace testability as a team.]]>
Lightning talk based on the 10 P's of Testability by Robert Meaney, talk designed by Ash Winter. Make your testing life better by embrace testability as a team.]]> Thu, 15 Aug 2019 17:35:32 GMT /slideshow/10-ps-of-testability/164088035 AshWinter@slideshare.net(AshWinter) 10 P's of Testability AshWinter Lightning talk based on the 10 P's of Testability by Robert Meaney, talk designed by Ash Winter. Make your testing life better by embrace testability as a team. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/10pstestability-190815173533-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Lightning talk based on the 10 P&#39;s of Testability by Robert Meaney, talk designed by Ash Winter. Make your testing life better by embrace testability as a team.
10 P's of Testability from Ash Winter
]]> 3434 3 https://cdn.slidesharecdn.com/ss_thumbnails/10pstestability-190815173533-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 The Wheel of Testing /AshWinter/the-wheel-of-testing ashwinter-wizardingwheeloftesting-190718122738
One of my recent endeavours has been to create a "career model" for the testers within my organisation. I sat in my office at home and designed "the testing wheel". I wanted it to be simple, inclusive and offer questions but no answers. Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others. My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models.]]>
One of my recent endeavours has been to create a "career model" for the testers within my organisation. I sat in my office at home and designed "the testing wheel". I wanted it to be simple, inclusive and offer questions but no answers. Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others. My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models.]]> Thu, 18 Jul 2019 12:27:38 GMT /AshWinter/the-wheel-of-testing AshWinter@slideshare.net(AshWinter) The Wheel of Testing AshWinter One of my recent endeavours has been to create a "career model" for the testers within my organisation. I sat in my office at home and designed "the testing wheel". I wanted it to be simple, inclusive and offer questions but no answers. Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others. My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/ashwinter-wizardingwheeloftesting-190718122738-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> One of my recent endeavours has been to create a &quot;career model&quot; for the testers within my organisation. I sat in my office at home and designed &quot;the testing wheel&quot;. I wanted it to be simple, inclusive and offer questions but no answers. Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others. My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models.
The Wheel of Testing from Ash Winter
]]> 118 2 https://cdn.slidesharecdn.com/ss_thumbnails/ashwinter-wizardingwheeloftesting-190718122738-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Making testability our mission /slideshow/making-testability-our-mission/151967383 makingtestabilityourmissionv2-190626115239
This is a call to action. On our cross functional teams and during our devops transformations we talk about how testing is for the whole team. Quality is everyone's responsibility. How much are we really doing to make this happen? Often we are working on systems that are hard to test for many reasons, but if we simply do more testing, write more automation we are neglecting what should be our main mission, advocating for increasing levels of testability, to truly get everyone involved in testing. We all have stories about how something is difficult to test, often never being tested or certainly left with the tester to figure it out. It doesn't have to be this way. During my talk, I want to introduce a set of principles for testability engineering. A new way to approach our work as testers. These principles will tackle how we make our systems more observable, controllable, how we share knowledge across teams and improve the testability of our dependencies. I believe it is time to create a new focus on testability, as it affects everything we do, what our teams do and beyond into how value is delivered for customers. I want you to take away from the talk: * Why a focus on testability can multiply your effectiveness as a tester * What the principles of testability engineering are and how to advocate for them * How you can make iterative changes to what you do in order to embrace testability New technology and complexity is rendering many software development techniques and paradigms obsolete at an increasing rate. We already exist in a space where an infinite number of tests of an array of different types can be performed. A new mission is needed, one that leverages the varied talents of all kinds of testers and culminates in a new focus on the exponential benefits that testability brings.]]>
This is a call to action. On our cross functional teams and during our devops transformations we talk about how testing is for the whole team. Quality is everyone's responsibility. How much are we really doing to make this happen? Often we are working on systems that are hard to test for many reasons, but if we simply do more testing, write more automation we are neglecting what should be our main mission, advocating for increasing levels of testability, to truly get everyone involved in testing. We all have stories about how something is difficult to test, often never being tested or certainly left with the tester to figure it out. It doesn't have to be this way. During my talk, I want to introduce a set of principles for testability engineering. A new way to approach our work as testers. These principles will tackle how we make our systems more observable, controllable, how we share knowledge across teams and improve the testability of our dependencies. I believe it is time to create a new focus on testability, as it affects everything we do, what our teams do and beyond into how value is delivered for customers. I want you to take away from the talk: * Why a focus on testability can multiply your effectiveness as a tester * What the principles of testability engineering are and how to advocate for them * How you can make iterative changes to what you do in order to embrace testability New technology and complexity is rendering many software development techniques and paradigms obsolete at an increasing rate. We already exist in a space where an infinite number of tests of an array of different types can be performed. A new mission is needed, one that leverages the varied talents of all kinds of testers and culminates in a new focus on the exponential benefits that testability brings.]]> Wed, 26 Jun 2019 11:52:39 GMT /slideshow/making-testability-our-mission/151967383 AshWinter@slideshare.net(AshWinter) Making testability our mission AshWinter This is a call to action. On our cross functional teams and during our devops transformations we talk about how testing is for the whole team. Quality is everyone's responsibility. How much are we really doing to make this happen? Often we are working on systems that are hard to test for many reasons, but if we simply do more testing, write more automation we are neglecting what should be our main mission, advocating for increasing levels of testability, to truly get everyone involved in testing. We all have stories about how something is difficult to test, often never being tested or certainly left with the tester to figure it out. It doesn't have to be this way. During my talk, I want to introduce a set of principles for testability engineering. A new way to approach our work as testers. These principles will tackle how we make our systems more observable, controllable, how we share knowledge across teams and improve the testability of our dependencies. I believe it is time to create a new focus on testability, as it affects everything we do, what our teams do and beyond into how value is delivered for customers. I want you to take away from the talk: * Why a focus on testability can multiply your effectiveness as a tester * What the principles of testability engineering are and how to advocate for them * How you can make iterative changes to what you do in order to embrace testability New technology and complexity is rendering many software development techniques and paradigms obsolete at an increasing rate. We already exist in a space where an infinite number of tests of an array of different types can be performed. A new mission is needed, one that leverages the varied talents of all kinds of testers and culminates in a new focus on the exponential benefits that testability brings. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/makingtestabilityourmissionv2-190626115239-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This is a call to action. On our cross functional teams and during our devops transformations we talk about how testing is for the whole team. Quality is everyone&#39;s responsibility. How much are we really doing to make this happen? Often we are working on systems that are hard to test for many reasons, but if we simply do more testing, write more automation we are neglecting what should be our main mission, advocating for increasing levels of testability, to truly get everyone involved in testing. We all have stories about how something is difficult to test, often never being tested or certainly left with the tester to figure it out. It doesn&#39;t have to be this way. During my talk, I want to introduce a set of principles for testability engineering. A new way to approach our work as testers. These principles will tackle how we make our systems more observable, controllable, how we share knowledge across teams and improve the testability of our dependencies. I believe it is time to create a new focus on testability, as it affects everything we do, what our teams do and beyond into how value is delivered for customers. I want you to take away from the talk: * Why a focus on testability can multiply your effectiveness as a tester * What the principles of testability engineering are and how to advocate for them * How you can make iterative changes to what you do in order to embrace testability New technology and complexity is rendering many software development techniques and paradigms obsolete at an increasing rate. We already exist in a space where an infinite number of tests of an array of different types can be performed. A new mission is needed, one that leverages the varied talents of all kinds of testers and culminates in a new focus on the exponential benefits that testability brings.
Making testability our mission from Ash Winter
]]> 98 1 https://cdn.slidesharecdn.com/ss_thumbnails/makingtestabilityourmissionv2-190626115239-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 A Testers Guide to the Myths, Legends and Tales of Unit Testing /slideshow/a-testers-guide-to-the-myths-legends-and-tales-of-unit-testing/108232951 testersguidetotheillusionsofunittesting-compressed-26-07-18-180801134600
One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour. To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus.]]>
One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour. To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus.]]> Wed, 01 Aug 2018 13:46:00 GMT /slideshow/a-testers-guide-to-the-myths-legends-and-tales-of-unit-testing/108232951 AshWinter@slideshare.net(AshWinter) A Testers Guide to the Myths, Legends and Tales of Unit Testing AshWinter One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour. To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testersguidetotheillusionsofunittesting-compressed-26-07-18-180801134600-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour. To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus.
A Testers Guide to the Myths, Legends and Tales of Unit Testing from Ash Winter
]]> 261 4 https://cdn.slidesharecdn.com/ss_thumbnails/testersguidetotheillusionsofunittesting-compressed-26-07-18-180801134600-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Testing Below the Application /slideshow/testing-below-the-application/97017606 ashwinter-testingbelowtheapplication-180514090701
How often have you found a problem with your application which is directly related to the infrastructure it is deployed upon? How often have you found a problem and not known? Testing is beginning to reach new depths. In my experience, saying that infrastructure needed to be tested used to trigger disbelieving looks in Ops teams faces, but less so now. The lines between infrastructure and code are blurring, so lets update our skills and outlook accordingly. * What I mean by infrastructure and why it is important to apply a testing mindset to this area * Questions to determine what to test, how to organise those thoughts and techniques that might be applied * A selection of tools to both explore and programatically check your infrastructure pre-deployment]]>
How often have you found a problem with your application which is directly related to the infrastructure it is deployed upon? How often have you found a problem and not known? Testing is beginning to reach new depths. In my experience, saying that infrastructure needed to be tested used to trigger disbelieving looks in Ops teams faces, but less so now. The lines between infrastructure and code are blurring, so lets update our skills and outlook accordingly. * What I mean by infrastructure and why it is important to apply a testing mindset to this area * Questions to determine what to test, how to organise those thoughts and techniques that might be applied * A selection of tools to both explore and programatically check your infrastructure pre-deployment]]> Mon, 14 May 2018 09:07:01 GMT /slideshow/testing-below-the-application/97017606 AshWinter@slideshare.net(AshWinter) Testing Below the Application AshWinter How often have you found a problem with your application which is directly related to the infrastructure it is deployed upon? How often have you found a problem and not known? Testing is beginning to reach new depths. In my experience, saying that infrastructure needed to be tested used to trigger disbelieving looks in Ops teams faces, but less so now. The lines between infrastructure and code are blurring, so lets update our skills and outlook accordingly. * What I mean by infrastructure and why it is important to apply a testing mindset to this area * Questions to determine what to test, how to organise those thoughts and techniques that might be applied * A selection of tools to both explore and programatically check your infrastructure pre-deployment <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/ashwinter-testingbelowtheapplication-180514090701-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> How often have you found a problem with your application which is directly related to the infrastructure it is deployed upon? How often have you found a problem and not known? Testing is beginning to reach new depths. In my experience, saying that infrastructure needed to be tested used to trigger disbelieving looks in Ops teams faces, but less so now. The lines between infrastructure and code are blurring, so lets update our skills and outlook accordingly. * What I mean by infrastructure and why it is important to apply a testing mindset to this area * Questions to determine what to test, how to organise those thoughts and techniques that might be applied * A selection of tools to both explore and programatically check your infrastructure pre-deployment
Testing Below the Application from Ash Winter
]]> 81 4 https://cdn.slidesharecdn.com/ss_thumbnails/ashwinter-testingbelowtheapplication-180514090701-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Shift Testability /slideshow/shift-testability-96947991/96947991 shifttestability-180513181016
Delivered at NWEWT 3 in Liverpool, using a testability focus to solve testing related problems at their root rather than their symptoms. Focusing on two metrics, "time to start testing" and "unplanned downtime." ]]>
Delivered at NWEWT 3 in Liverpool, using a testability focus to solve testing related problems at their root rather than their symptoms. Focusing on two metrics, "time to start testing" and "unplanned downtime." ]]> Sun, 13 May 2018 18:10:16 GMT /slideshow/shift-testability-96947991/96947991 AshWinter@slideshare.net(AshWinter) Shift Testability AshWinter Delivered at NWEWT 3 in Liverpool, using a testability focus to solve testing related problems at their root rather than their symptoms. Focusing on two metrics, "time to start testing" and "unplanned downtime." <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/shifttestability-180513181016-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Delivered at NWEWT 3 in Liverpool, using a testability focus to solve testing related problems at their root rather than their symptoms. Focusing on two metrics, &quot;time to start testing&quot; and &quot;unplanned downtime.&quot;
Shift Testability from Ash Winter
]]> 429 4 https://cdn.slidesharecdn.com/ss_thumbnails/shifttestability-180513181016-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Part of the Pipeline /AshWinter/part-of-the-pipeline ashwinter-partofthepipelinev1-180319150504
Nobody /really/ likes change, its human nature. Testers have a special relationship with changing tools and techniques, they change and we tend to flounder a little and end up very nervous about our place in the new world. Continuous delivery is one such circumstance, I see and speak to many testers really struggling. However, with a significant shift in outlook and a chunk of personal development, testers can excel in environments such as these. Its time to start to get out in front of a changing world, rather than always battling to catch up. I want to share my experience of adding value as a tester in a continuous delivery environment, what new technologies and techniques I've learned, using your Production environment as an oracle, advocating testability and most crucially, not overestimating what our testing can achieve. Testing is not the only form of feedback, its time to let go of some the aspects of testing we cling to. Continuous delivery adds richness and variety to our role as testers. To me, it is a facilitator for the autonomy and respect that testers have craved for a long time, so lets get involved...]]>
Nobody /really/ likes change, its human nature. Testers have a special relationship with changing tools and techniques, they change and we tend to flounder a little and end up very nervous about our place in the new world. Continuous delivery is one such circumstance, I see and speak to many testers really struggling. However, with a significant shift in outlook and a chunk of personal development, testers can excel in environments such as these. Its time to start to get out in front of a changing world, rather than always battling to catch up. I want to share my experience of adding value as a tester in a continuous delivery environment, what new technologies and techniques I've learned, using your Production environment as an oracle, advocating testability and most crucially, not overestimating what our testing can achieve. Testing is not the only form of feedback, its time to let go of some the aspects of testing we cling to. Continuous delivery adds richness and variety to our role as testers. To me, it is a facilitator for the autonomy and respect that testers have craved for a long time, so lets get involved...]]> Mon, 19 Mar 2018 15:05:04 GMT /AshWinter/part-of-the-pipeline AshWinter@slideshare.net(AshWinter) Part of the Pipeline AshWinter Nobody /really/ likes change, its human nature. Testers have a special relationship with changing tools and techniques, they change and we tend to flounder a little and end up very nervous about our place in the new world. Continuous delivery is one such circumstance, I see and speak to many testers really struggling. However, with a significant shift in outlook and a chunk of personal development, testers can excel in environments such as these. Its time to start to get out in front of a changing world, rather than always battling to catch up. I want to share my experience of adding value as a tester in a continuous delivery environment, what new technologies and techniques I've learned, using your Production environment as an oracle, advocating testability and most crucially, not overestimating what our testing can achieve. Testing is not the only form of feedback, its time to let go of some the aspects of testing we cling to. Continuous delivery adds richness and variety to our role as testers. To me, it is a facilitator for the autonomy and respect that testers have craved for a long time, so lets get involved... <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/ashwinter-partofthepipelinev1-180319150504-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Nobody /really/ likes change, its human nature. Testers have a special relationship with changing tools and techniques, they change and we tend to flounder a little and end up very nervous about our place in the new world. Continuous delivery is one such circumstance, I see and speak to many testers really struggling. However, with a significant shift in outlook and a chunk of personal development, testers can excel in environments such as these. Its time to start to get out in front of a changing world, rather than always battling to catch up. I want to share my experience of adding value as a tester in a continuous delivery environment, what new technologies and techniques I&#39;ve learned, using your Production environment as an oracle, advocating testability and most crucially, not overestimating what our testing can achieve. Testing is not the only form of feedback, its time to let go of some the aspects of testing we cling to. Continuous delivery adds richness and variety to our role as testers. To me, it is a facilitator for the autonomy and respect that testers have craved for a long time, so lets get involved...
Part of the Pipeline from Ash Winter
]]> 89 1 https://cdn.slidesharecdn.com/ss_thumbnails/ashwinter-partofthepipelinev1-180319150504-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Scroll Based Testing Strategy /slideshow/scroll-based-testing-strategy/91161134 scrollbasedtestingstrategy-180319135612
No one paying attention to your test strategy? Its too long. More crucially, it has no scrolls. Here's a template for the agile testing quadrants, but with scrolls for extra unforgettability. ]]>
No one paying attention to your test strategy? Its too long. More crucially, it has no scrolls. Here's a template for the agile testing quadrants, but with scrolls for extra unforgettability. ]]> Mon, 19 Mar 2018 13:56:12 GMT /slideshow/scroll-based-testing-strategy/91161134 AshWinter@slideshare.net(AshWinter) Scroll Based Testing Strategy AshWinter No one paying attention to your test strategy? Its too long. More crucially, it has no scrolls. Here's a template for the agile testing quadrants, but with scrolls for extra unforgettability. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/scrollbasedtestingstrategy-180319135612-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> No one paying attention to your test strategy? Its too long. More crucially, it has no scrolls. Here&#39;s a template for the agile testing quadrants, but with scrolls for extra unforgettability.
Scroll Based Testing Strategy from Ash Winter
]]> 285 3 https://cdn.slidesharecdn.com/ss_thumbnails/scrollbasedtestingstrategy-180319135612-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Bullseye or The Testing Wheel /slideshow/bullseye-or-the-testing-wheel/73345068 ashwinter-bullseye-170320101147
One of my recent endeavours has been to create a "career model" for the testers within my organisation. I sat in my office at home and designed "the testing wheel". I wanted it to be simple, inclusive and offer questions but few answers. Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others. My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models.]]>
One of my recent endeavours has been to create a "career model" for the testers within my organisation. I sat in my office at home and designed "the testing wheel". I wanted it to be simple, inclusive and offer questions but few answers. Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others. My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models.]]> Mon, 20 Mar 2017 10:11:47 GMT /slideshow/bullseye-or-the-testing-wheel/73345068 AshWinter@slideshare.net(AshWinter) Bullseye or The Testing Wheel AshWinter One of my recent endeavours has been to create a "career model" for the testers within my organisation. I sat in my office at home and designed "the testing wheel". I wanted it to be simple, inclusive and offer questions but few answers. Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others. My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/ashwinter-bullseye-170320101147-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> One of my recent endeavours has been to create a &quot;career model&quot; for the testers within my organisation. I sat in my office at home and designed &quot;the testing wheel&quot;. I wanted it to be simple, inclusive and offer questions but few answers. Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others. My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models.
Bullseye or The Testing Wheel from Ash Winter
]]> 698 7 https://cdn.slidesharecdn.com/ss_thumbnails/ashwinter-bullseye-170320101147-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Ash_Winter-DEWT7_V1 /slideshow/ashwinterdewt7v1/71585523 82d489e2-603b-4cd7-aea1-a2c6d50117ac-170131123010
]]>
]]> Tue, 31 Jan 2017 12:30:10 GMT /slideshow/ashwinterdewt7v1/71585523 AshWinter@slideshare.net(AshWinter) Ash_Winter-DEWT7_V1 AshWinter <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/82d489e2-603b-4cd7-aea1-a2c6d50117ac-170131123010-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Ash_Winter-DEWT7_V1 from Ash Winter
]]> 411 2 https://cdn.slidesharecdn.com/ss_thumbnails/82d489e2-603b-4cd7-aea1-a2c6d50117ac-170131123010-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Ash_Winter-Forgotten-ility_V1 /slideshow/ashwinterforgottenilityv1/71585062 d0cfb8b5-d0e0-4e43-a34a-e9e3b0a5f437-170131121822
]]>
]]> Tue, 31 Jan 2017 12:18:22 GMT /slideshow/ashwinterforgottenilityv1/71585062 AshWinter@slideshare.net(AshWinter) Ash_Winter-Forgotten-ility_V1 AshWinter <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/d0cfb8b5-d0e0-4e43-a34a-e9e3b0a5f437-170131121822-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Ash_Winter-Forgotten-ility_V1 from Ash Winter
]]> 826 2 https://cdn.slidesharecdn.com/ss_thumbnails/d0cfb8b5-d0e0-4e43-a34a-e9e3b0a5f437-170131121822-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Main Talk v1.1 /slideshow/main-talk-v11/66048874 d05a33ca-7d64-4553-ae8d-05459945216b-160915084139
]]>
]]> Thu, 15 Sep 2016 08:41:39 GMT /slideshow/main-talk-v11/66048874 AshWinter@slideshare.net(AshWinter) Main Talk v1.1 AshWinter <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/d05a33ca-7d64-4553-ae8d-05459945216b-160915084139-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Main Talk v1.1 from Ash Winter
]]> 298 3 https://cdn.slidesharecdn.com/ss_thumbnails/d05a33ca-7d64-4553-ae8d-05459945216b-160915084139-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Ash Winter - What is testing? /slideshow/ash-winter-what-is-testing/64432447 c94d095a-6aa9-49c5-b7c2-037979a2959e-160727112314
]]>
]]> Wed, 27 Jul 2016 11:23:14 GMT /slideshow/ash-winter-what-is-testing/64432447 AshWinter@slideshare.net(AshWinter) Ash Winter - What is testing? AshWinter <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/c94d095a-6aa9-49c5-b7c2-037979a2959e-160727112314-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Ash Winter - What is testing? from Ash Winter
]]> 220 4 https://cdn.slidesharecdn.com/ss_thumbnails/c94d095a-6aa9-49c5-b7c2-037979a2959e-160727112314-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Turbo Mindmapping Your App /slideshow/turbo-mindmapping-your-app/64287558 mindmappingworkshop-160722152645
Mini workshop for collaboratively mindmapping your app using mindmup!]]>
Mini workshop for collaboratively mindmapping your app using mindmup!]]> Fri, 22 Jul 2016 15:26:45 GMT /slideshow/turbo-mindmapping-your-app/64287558 AshWinter@slideshare.net(AshWinter) Turbo Mindmapping Your App AshWinter Mini workshop for collaboratively mindmapping your app using mindmup! <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/mindmappingworkshop-160722152645-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Mini workshop for collaboratively mindmapping your app using mindmup!
Turbo Mindmapping Your App from Ash Winter
]]> 240 2 https://cdn.slidesharecdn.com/ss_thumbnails/mindmappingworkshop-160722152645-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-AshWinter-48x48.jpg?cb=1639321757 https://cdn.slidesharecdn.com/ss_thumbnails/testabilitycoachingcanvas-211212152645-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/testability-coaching-canvas-250825632/250825632 Testability Advocacy C... https://cdn.slidesharecdn.com/ss_thumbnails/salespitchtomanagers-200419140904-thumbnail.jpg?width=320&height=320&fit=bounds AshWinter/testability-sales-pitch-232256929 Testability Sales Pitch https://cdn.slidesharecdn.com/ss_thumbnails/workshop-200130214856-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/architectural-testability-workshop-for-test-academy-barcelona/226249273 Architectural Testabil...