Coaching Model for Unrecognised Internal Models
•Download as PPTX, PDF•
0 likes•172 views
This document proposes a coaching model to help testers recognize the testing models they already use intuitively and help them improve. The model focuses on using questioning rather than providing answers to guide testers to higher levels of thinking based on Bloom's Taxonomy. By getting testers to apply models through practice and reflection, and by iterating the model over time based on emergent needs, the coaching model aims to improve testing skills through collaborative learning.
Report
Share
Report
Share
Recommended
Week 2 Effective Speech
The document provides tips for reducing public speaking anxiety and improving speaking skills. It recommends visualizing past successful speakers and picturing the audience as friendly. Preparing well by knowing the topic in-depth and practicing delivery are emphasized. Autogenic training exercises and embracing nervous energy are suggested for managing fear. The overall message is that preparation, focusing on the audience, and passion for the topic will lead to effective speaking.
Maintaining motivation4. lesson 3 maintaining the enthusiasm to succeed des...
This document provides strategies for maintaining enthusiasm when facing struggles. It suggests visualizing success to avoid dwelling on challenges, minimizing stress, staying focused on goals, keeping a fresh perspective through variation, avoiding procrastination, keeping an open mind, and not sweating the small things. Maintaining enthusiasm through struggles is important for sustaining motivation and willpower to achieve success, which is sweeter when one has overcome great obstacles. The document encourages applying these techniques to challenges in one's own life.
Coaching by leaders
Coaching is a blend of training and mentoring that helps employees become more successful by identifying and eliminating roadblocks and unleashing their potential to prepare them for the next level. Coaching involves both short-term performance improvement and long-term performance development. It is an ongoing, interactive and collaborative process based on honesty and trust. While coaching does not always provide answers, it helps employees calibrate to find the answers themselves. Coaching provides benefits for employees such as skills growth, motivation and job satisfaction, and benefits for leaders and organizations such as increased productivity, engagement and performance. Common coaching challenges like lack of time can be overcome by prioritizing coaching for interested employees, and lack of training can be addressed by acquiring relevant skills
Performance coaching handbook
This document provides an overview of performance coaching. It defines coaching as a dialogue between coach and coachee to facilitate learning and change through practical actions. Performance coaching focuses specifically on improving work performance. The document outlines key aspects of coaching including how it differs from other approaches like mentoring or consulting. It also discusses the coach and coachee roles, benefits of coaching, and tools coaches can use like questioning, listening and challenge. Models for structuring coaching conversations are presented, including the GROW model which outlines setting a goal, understanding current reality, exploring options, and agreeing on actions.
Checklist for trainer in teambuilding exercises
The “Checklist for trainer in teambuilding exercises” offers 11 points to verify before and during your team-building exercises and activities. Spread the advice!
Brand-led learning: Kineo makes the case!
Brand-led earning programs can make the difference between blah-blah-blah elearning and programs that really connect with people's hearts and minds to change behavior and make them feel a part of the bigger picture. So what is brand-led learning? And is it safe to do this at home?
Reinvent your life,Online Self Coaching Program in South Africa|Coachingself.com
Change your life and accomplish lifelong goals for a better future with online self coaching program by the best life coaches at Coachingself.com in South Africa.
http://coachingself.com/
9 tips to work more effectively from your desk!
The document provides 9 tips for working more effectively from a desk. The tips include taking notes during meetings, setting priorities in the morning, delegating productive hours to top projects, taking breaks to avoid burnout, identifying time-consuming tasks, focusing on one task at a time instead of multitasking, maintaining boundaries between work and personal life, staying organized, and limiting distractions. The document was written by Solomon Vijayanand, the Chief Enabling Officer of Solomon People Solutions, a consulting firm that offers training and talent solutions.
Recommended
Week 2 Effective Speech
The document provides tips for reducing public speaking anxiety and improving speaking skills. It recommends visualizing past successful speakers and picturing the audience as friendly. Preparing well by knowing the topic in-depth and practicing delivery are emphasized. Autogenic training exercises and embracing nervous energy are suggested for managing fear. The overall message is that preparation, focusing on the audience, and passion for the topic will lead to effective speaking.
Maintaining motivation4. lesson 3 maintaining the enthusiasm to succeed des...
This document provides strategies for maintaining enthusiasm when facing struggles. It suggests visualizing success to avoid dwelling on challenges, minimizing stress, staying focused on goals, keeping a fresh perspective through variation, avoiding procrastination, keeping an open mind, and not sweating the small things. Maintaining enthusiasm through struggles is important for sustaining motivation and willpower to achieve success, which is sweeter when one has overcome great obstacles. The document encourages applying these techniques to challenges in one's own life.
Coaching by leaders
Coaching is a blend of training and mentoring that helps employees become more successful by identifying and eliminating roadblocks and unleashing their potential to prepare them for the next level. Coaching involves both short-term performance improvement and long-term performance development. It is an ongoing, interactive and collaborative process based on honesty and trust. While coaching does not always provide answers, it helps employees calibrate to find the answers themselves. Coaching provides benefits for employees such as skills growth, motivation and job satisfaction, and benefits for leaders and organizations such as increased productivity, engagement and performance. Common coaching challenges like lack of time can be overcome by prioritizing coaching for interested employees, and lack of training can be addressed by acquiring relevant skills
Performance coaching handbook
This document provides an overview of performance coaching. It defines coaching as a dialogue between coach and coachee to facilitate learning and change through practical actions. Performance coaching focuses specifically on improving work performance. The document outlines key aspects of coaching including how it differs from other approaches like mentoring or consulting. It also discusses the coach and coachee roles, benefits of coaching, and tools coaches can use like questioning, listening and challenge. Models for structuring coaching conversations are presented, including the GROW model which outlines setting a goal, understanding current reality, exploring options, and agreeing on actions.
Checklist for trainer in teambuilding exercises
The “Checklist for trainer in teambuilding exercises” offers 11 points to verify before and during your team-building exercises and activities. Spread the advice!
Brand-led learning: Kineo makes the case!
Brand-led earning programs can make the difference between blah-blah-blah elearning and programs that really connect with people's hearts and minds to change behavior and make them feel a part of the bigger picture. So what is brand-led learning? And is it safe to do this at home?
Reinvent your life,Online Self Coaching Program in South Africa|Coachingself.com
Change your life and accomplish lifelong goals for a better future with online self coaching program by the best life coaches at Coachingself.com in South Africa.
http://coachingself.com/
9 tips to work more effectively from your desk!
The document provides 9 tips for working more effectively from a desk. The tips include taking notes during meetings, setting priorities in the morning, delegating productive hours to top projects, taking breaks to avoid burnout, identifying time-consuming tasks, focusing on one task at a time instead of multitasking, maintaining boundaries between work and personal life, staying organized, and limiting distractions. The document was written by Solomon Vijayanand, the Chief Enabling Officer of Solomon People Solutions, a consulting firm that offers training and talent solutions.
Галина Єфремова - "Once Again on Motivation or How to Make Them Do What I Wan...
Kharkiv PMDay 2017
Галина Єфремова - "Once Again on Motivation or How to Make Them Do What I Want"
D I Y Training - 101 HRD - Management - Development - Panning - Getting Started
D I Y Training - 101 HRD - Management - Development - Panning - Getting StartedService on Sight Research & Consultancy Inc
Making a change means learning something new. Being unprepared or untrained means doing something new. Make a start and do it now.How to Enjoy Work !
The document provides tips for how to enjoy work, such as knowing your role, respecting yourself and your work, working towards growth and goals in innovative ways, taking responsibility, multitasking, updating knowledge, polishing skills, sharing experiences by working in teams, listening to music, taking feedback, challenging yourself, being effective by minimizing errors and increasing speed, having a strong work ethic, and balancing work and life.
What is creativity
The document discusses creativity from several perspectives. It begins by defining two types of creativity: technical creativity which involves creating new ideas and theories, and artistic creativity which is a form of self-expression. It notes that everyone thinks differently and it is important to consider different thinking styles as a designer. The document also stresses that creative work requires a significant time investment and regular breaks to avoid burnout. Finally, it suggests that creativity can be developed over time through engaging in creative exercises, learning new things, getting adequate sleep, and being open to new experiences.
Ten business success principles slides
The document provides advice for entrepreneurs on overcoming mental roadblocks and mistakes to achieve success. It recommends having a growth mindset of "I have not done that yet" instead of "I cannot do something". Mistakes should be viewed as opportunities to learn and strengthen weak areas. Any problem can be solved by thinking outside the box. Goals and deadlines should be set to accomplish milestones. Don't try to do everything alone, leverage others' strengths. Feedback and problems indicate what customers want - listen, learn, and provide solutions. Connect with successful people in the industry to learn from them. Daily action is key to building a business.
How to become a super delegator - Top Tip Tuesday to help you over Hump Day W...
To become an effective delegator, focus on delegating tasks that are low priority but could become urgent if not handled. When delegating a task, prepare the person by explaining what is needed, showing them how to complete it, and letting them try it themselves. Be sure to set SMART objectives for delegated tasks that specify what should be achieved and how the person will know, and give a timescale for completion. Periodically check in with those you delegate to ensure they are on track to meet objectives and get help if needed.
d.Maps: Design Cultural Maps Lab 1
d.Maps: Design Cultural Maps Lab 1
*Material adapted from dschool.stanford.edu
*Special thanks to Carly Geehr, Rich Crandell, Susie Wise, Erica Estrada for allowing shamelessly stolen inspiration
Creative leadership
This workshop teaches creative problem solving and thinking methods to help leaders and teams leave rational thinking behind and explore new ideas. The workshop uses visual techniques like doodling and drawing, which anyone can do, to get ideas out in new ways in addition to words. It is especially useful when teams have over-rationalized and gotten stuck in their thinking, and can be done as a full day session or shorter 1-3 hour session to help teams get unstuck.
How to grow better in your workplace
This is the story of every individual who is or has been a part of a
proactive workforce. It is the story of every employee, manager, and
leader who started with one motive - To learn and grow. More importantly,
it’s the personal story of every individual who’s waiting for that one
opportunity to make it big.
Testability Advocacy Canvas
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 Sales Pitch
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!
Architectural Testability Workshop for Test Academy Barcelona
Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model.
Testability Squad Health Check
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.
Testability is Everyone's Responsibility
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.
Testers Guide to the Illusions of Unit Testing
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 wasn’t 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.
10 P's of Testability
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.
The Wheel of Testing
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.
Making testability our mission
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.
A Testers Guide to the Myths, Legends and Tales of Unit Testing
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.
Testing Below the Application
This document discusses testing infrastructure components that lie beneath applications. It defines infrastructure as the building blocks applications depend on, like hardware, virtualization, containers, and software. The author argues that testers should care about infrastructure testing because infrastructure problems are often found at the wrong level, and the product as a whole is symbiotic between applications and infrastructure. Various testing principles, examples, tactics, and tools are provided for both human/deterministic and machine/deterministic testing of infrastructure, as well as human/random and machine/random approaches.
Shift Testability
The document discusses the importance of testability in software development. It argues that focusing on testability, rather than just features, can lead to important benefits like reduced time to start testing, lower unplanned downtimes, and increased ability to observe and understand the entire system. The document advocates for approaches like enabling faster branching to devices for testing, more automation, and greater collaboration between development and operations teams to improve testability.
Part of the Pipeline
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. It’s 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, it’s 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 let’s get involved...
More Related Content
What's hot
Галина Єфремова - "Once Again on Motivation or How to Make Them Do What I Wan...
Kharkiv PMDay 2017
Галина Єфремова - "Once Again on Motivation or How to Make Them Do What I Want"
D I Y Training - 101 HRD - Management - Development - Panning - Getting Started
D I Y Training - 101 HRD - Management - Development - Panning - Getting StartedService on Sight Research & Consultancy Inc
Making a change means learning something new. Being unprepared or untrained means doing something new. Make a start and do it now.How to Enjoy Work !
The document provides tips for how to enjoy work, such as knowing your role, respecting yourself and your work, working towards growth and goals in innovative ways, taking responsibility, multitasking, updating knowledge, polishing skills, sharing experiences by working in teams, listening to music, taking feedback, challenging yourself, being effective by minimizing errors and increasing speed, having a strong work ethic, and balancing work and life.
What is creativity
The document discusses creativity from several perspectives. It begins by defining two types of creativity: technical creativity which involves creating new ideas and theories, and artistic creativity which is a form of self-expression. It notes that everyone thinks differently and it is important to consider different thinking styles as a designer. The document also stresses that creative work requires a significant time investment and regular breaks to avoid burnout. Finally, it suggests that creativity can be developed over time through engaging in creative exercises, learning new things, getting adequate sleep, and being open to new experiences.
Ten business success principles slides
The document provides advice for entrepreneurs on overcoming mental roadblocks and mistakes to achieve success. It recommends having a growth mindset of "I have not done that yet" instead of "I cannot do something". Mistakes should be viewed as opportunities to learn and strengthen weak areas. Any problem can be solved by thinking outside the box. Goals and deadlines should be set to accomplish milestones. Don't try to do everything alone, leverage others' strengths. Feedback and problems indicate what customers want - listen, learn, and provide solutions. Connect with successful people in the industry to learn from them. Daily action is key to building a business.
How to become a super delegator - Top Tip Tuesday to help you over Hump Day W...
To become an effective delegator, focus on delegating tasks that are low priority but could become urgent if not handled. When delegating a task, prepare the person by explaining what is needed, showing them how to complete it, and letting them try it themselves. Be sure to set SMART objectives for delegated tasks that specify what should be achieved and how the person will know, and give a timescale for completion. Periodically check in with those you delegate to ensure they are on track to meet objectives and get help if needed.
d.Maps: Design Cultural Maps Lab 1
d.Maps: Design Cultural Maps Lab 1
*Material adapted from dschool.stanford.edu
*Special thanks to Carly Geehr, Rich Crandell, Susie Wise, Erica Estrada for allowing shamelessly stolen inspiration
Creative leadership
This workshop teaches creative problem solving and thinking methods to help leaders and teams leave rational thinking behind and explore new ideas. The workshop uses visual techniques like doodling and drawing, which anyone can do, to get ideas out in new ways in addition to words. It is especially useful when teams have over-rationalized and gotten stuck in their thinking, and can be done as a full day session or shorter 1-3 hour session to help teams get unstuck.
How to grow better in your workplace
This is the story of every individual who is or has been a part of a
proactive workforce. It is the story of every employee, manager, and
leader who started with one motive - To learn and grow. More importantly,
it’s the personal story of every individual who’s waiting for that one
opportunity to make it big.
What's hot (9)
Галина Єфремова - "Once Again on Motivation or How to Make Them Do What I Wan...
Галина Єфремова - "Once Again on Motivation or How to Make Them Do What I Wan...
D I Y Training - 101 HRD - Management - Development - Panning - Getting Started
D I Y Training - 101 HRD - Management - Development - Panning - Getting Started
How to become a super delegator - Top Tip Tuesday to help you over Hump Day W...
How to become a super delegator - Top Tip Tuesday to help you over Hump Day W...
More from Ash Winter
Testability Advocacy Canvas
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 Sales Pitch
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!
Architectural Testability Workshop for Test Academy Barcelona
Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model.
Testability Squad Health Check
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.
Testability is Everyone's Responsibility
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.
Testers Guide to the Illusions of Unit Testing
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 wasn’t 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.
10 P's of Testability
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.
The Wheel of Testing
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.
Making testability our mission
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.
A Testers Guide to the Myths, Legends and Tales of Unit Testing
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.
Testing Below the Application
This document discusses testing infrastructure components that lie beneath applications. It defines infrastructure as the building blocks applications depend on, like hardware, virtualization, containers, and software. The author argues that testers should care about infrastructure testing because infrastructure problems are often found at the wrong level, and the product as a whole is symbiotic between applications and infrastructure. Various testing principles, examples, tactics, and tools are provided for both human/deterministic and machine/deterministic testing of infrastructure, as well as human/random and machine/random approaches.
Shift Testability
The document discusses the importance of testability in software development. It argues that focusing on testability, rather than just features, can lead to important benefits like reduced time to start testing, lower unplanned downtimes, and increased ability to observe and understand the entire system. The document advocates for approaches like enabling faster branching to devices for testing, more automation, and greater collaboration between development and operations teams to improve testability.
Part of the Pipeline
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. It’s 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, it’s 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 let’s get involved...
Scroll Based Testing Strategy
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.
Bullseye or The Testing Wheel
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.
Ash_Winter-DEWT7_V1
This document discusses the author's experience consulting with various organizations to improve their testing capabilities. The author found that reviewing testing independently did not address root causes and that organizations often wanted quick fixes rather than systemic changes. The author eventually realized they needed to take a more holistic systems-thinking approach and focus on root causes rather than superficial solutions. They decided to focus more on systems thinking and become nomadic in their work.
Ash_Winter-Forgotten-ility_V1
The document discusses various topics related to software testing including testability, logging, environments, and feedback. It provides tips such as getting to know operations pain points, logging what matters without bloat, understanding past code intent, and focusing more on test flow and feedback rather than number of environments or testability. The document ends with inviting questions.
Main Talk v1.1
Pokémon GO faced several quality issues after its initial release such as app freezing, server overload causing scaling problems, inaccurate GPS, and device fragmentation affecting the ability to catch Pokémon. The document discusses lessons learned around testing and quality from these issues, including the need for a balanced testing approach with different types of testing like functionality, performance, compatibility, and usability testing. It also emphasizes that quality is multifaceted and requires continuously adding and improving features while focusing on the core idea.
Ash Winter - What is testing?
This document discusses different perspectives on what testing is and provides the author's axioms about testing. The author believes that testing is a team-based activity where they help enable testing rather than doing most of the testing themselves. They view testing as a human, intellectual activity involving thinking, learning, sharing ideas. Complete testing is seen as impossible due to logical limitations and infinite possibilities, so balance and variation are important. Testing is considered a performance where the value is in applying it, not just thinking about it. Tools can assist testing but not replace it. Context is also important, as what works in one situation may not work in another.
Turbo Mindmapping Your App
This document provides instructions for collaboratively mindmapping an application using the online tool mindmup.com. Participants are instructed to get into groups of three, with one person creating a real-time collaborative mindmap session for their application and inviting the other two participants. They are then instructed to collaboratively map out the functions, forms, fields, views, integrations, and other aspects of the application to document its functionality and coverage for testing purposes.
More from Ash Winter (20)
Architectural Testability Workshop for Test Academy Barcelona
Architectural Testability Workshop for Test Academy Barcelona
A Testers Guide to the Myths, Legends and Tales of Unit Testing
A Testers Guide to the Myths, Legends and Tales of Unit Testing
Coaching Model for Unrecognised Internal Models
- 1. Coaching Model for Unrecognised Internal Testing Models Or helping testers realise that apply models all the time, they probably just need someone to help them realise. And the rewards of giving time to help other testers.
- 2. How did I get to this what and why?
- 3. Who is this model for?
- 4. Blooms Taxonomy – its generally pretty cool and makes you think.
- 5. Blooms - Good for learning and it makes sense for coaching too.
- 6. Coaching models should have goals. Blooms like goals.
- 7. Build your model on pillars of questions, not answers. You are coaching.
- 8. Models are emergent, therefore let it breathe.
- 9. Getting their hands dirty, more Blooms!
- 10. Learning, iterating, sometimes just spinning.