We Don't Know?
•Download as PPTX, PDF•
0 likes•514 views
The document discusses quality assurance and testing. It provides different definitions of quality, bugs, and testing from various sources. The key point is that there is no single agreed upon definition for these terms, and as testers, we don't truly know what we are doing or if our work is effective. The overall message is that in quality assurance and testing, there is still much that is unknown.
Report
Share
Report
Share
Recommended
Kanban method: The Practices aren't the Point
Capping our 10-month series on the Kanban Method; in this presentation we discuss that the Practices of the Kanban Method are a means, not an end.
The true end goal: enabling efficient flow of high value, high quality work.
Tranquilty Over Tubulence
Many different styles and frameworks of Agile Software Development have been developed since The Agile Manifesto was written. A prevailing goal across the alternatives is to promote peace of mind for customers, users, and the development team. Unfortunately, it is all too common for Agile teams to experience turbulence rather than tranquility.
Seven guiding principles that promote peace of mind are presented. These principles provide a framework for discovering new processes and practices that will improve team productivity, communication, and performance. The goal for practitioners is to find, identify, and implement practices that work in their environment and make people awesome.
To Estimate or Not to Estimate, Is that the Question? (2017 Better Software C...
This document discusses different approaches to software project estimation, including arguments for and against estimating. It presents a spectrum of estimating approaches from never estimating to always estimating. It advocates for probabilistic and data-driven forecasting over deterministic estimates based on intuition. The key ideas are to reduce sources of variation, gather data over time to build probabilistic forecasts, focus on delivering value quickly, and establish service-level expectations rather than commitments.
React introduction
This document appears to be notes from a workshop on React.js held at Trend Micro. It discusses key React concepts like components, data flow, and the component lifecycle. Components are the basic building blocks, and data flows unidirectionally from parent to child via props but can be mutated internally via state. The lifecycle methods like getInitialState and render are where components are initialized and updated. React aims to make views structural and predictable through its use of components and one-way data flow.
De-Risky Business: Techniques for Mitigating and Managing Risk
From http://esp.leankanban.com/
In this presentation, which covers blocker clustering, service-delivery review and fitness criteria metrics, you will discover some techniques for identifying and mitigating risk. The talk is based on software-delivery experiences at both the delivery-team and management levels.
Better Living Through Design – WebVisions May 2015
As UX designers, we seek to relate to our users through empathy and understanding. But what about ourselves? What happens when we take the processes and tools we use in our work in product design and apply them to our lives?
In this lively talk, Paul McAleer shares his story. He'll take you through each phase of the iterative, ongoing project that is his life: research (gathering input from stakeholders), strategy (coming up with an overall goal and plan), execution/experimentation, and getting feedback.
You'll get tips and tricks on paying attention to your own needs, how to encourage a good critique, and other practical tools that can get you started on designing your life and yourself.
Using Checklists to Increase Productiviity and Consistency in Publication Tas...
Using Checklists to Increase Productiviity and Consistency in Publication Tas...Kelly Schrank, MA, ELS
Anyone writing, editing, or managing any type of communications for a living is feeling the crunch. There is less time to create and edit; more types and formats of content; more apps, software, and systems to learn. And we expect quality, accuracy, and consistency from ourselves because we take pride in our work. This session discussed how to address a multitude of modern dilemmas with a relatively old-school hack: a checklist.
This session was about how using a comprehensive checklist created and updated for a specific communication task can help you differentiate workflows, systems, and activities; spell out style and formatting details, track your progress, document metrics, and give you a sense of completion and peace of mind.The #NoEstimates Movement - Ryan Ripley
The #NoEstimates Movement explore the question of whether or not we need traditional estimates to make decisions about software development projects. By working in an agile way can we break down our work, inspect and adapt frequently, and deliver value to our customers. This presentation was give at Derby City Agile on June 15, 2018. http://derbycityagile.com/
Recommended
Kanban method: The Practices aren't the Point
Capping our 10-month series on the Kanban Method; in this presentation we discuss that the Practices of the Kanban Method are a means, not an end.
The true end goal: enabling efficient flow of high value, high quality work.
Tranquilty Over Tubulence
Many different styles and frameworks of Agile Software Development have been developed since The Agile Manifesto was written. A prevailing goal across the alternatives is to promote peace of mind for customers, users, and the development team. Unfortunately, it is all too common for Agile teams to experience turbulence rather than tranquility.
Seven guiding principles that promote peace of mind are presented. These principles provide a framework for discovering new processes and practices that will improve team productivity, communication, and performance. The goal for practitioners is to find, identify, and implement practices that work in their environment and make people awesome.
To Estimate or Not to Estimate, Is that the Question? (2017 Better Software C...
This document discusses different approaches to software project estimation, including arguments for and against estimating. It presents a spectrum of estimating approaches from never estimating to always estimating. It advocates for probabilistic and data-driven forecasting over deterministic estimates based on intuition. The key ideas are to reduce sources of variation, gather data over time to build probabilistic forecasts, focus on delivering value quickly, and establish service-level expectations rather than commitments.
React introduction
This document appears to be notes from a workshop on React.js held at Trend Micro. It discusses key React concepts like components, data flow, and the component lifecycle. Components are the basic building blocks, and data flows unidirectionally from parent to child via props but can be mutated internally via state. The lifecycle methods like getInitialState and render are where components are initialized and updated. React aims to make views structural and predictable through its use of components and one-way data flow.
De-Risky Business: Techniques for Mitigating and Managing Risk
From http://esp.leankanban.com/
In this presentation, which covers blocker clustering, service-delivery review and fitness criteria metrics, you will discover some techniques for identifying and mitigating risk. The talk is based on software-delivery experiences at both the delivery-team and management levels.
Better Living Through Design – WebVisions May 2015
As UX designers, we seek to relate to our users through empathy and understanding. But what about ourselves? What happens when we take the processes and tools we use in our work in product design and apply them to our lives?
In this lively talk, Paul McAleer shares his story. He'll take you through each phase of the iterative, ongoing project that is his life: research (gathering input from stakeholders), strategy (coming up with an overall goal and plan), execution/experimentation, and getting feedback.
You'll get tips and tricks on paying attention to your own needs, how to encourage a good critique, and other practical tools that can get you started on designing your life and yourself.
Using Checklists to Increase Productiviity and Consistency in Publication Tas...
Using Checklists to Increase Productiviity and Consistency in Publication Tas...Kelly Schrank, MA, ELS
Anyone writing, editing, or managing any type of communications for a living is feeling the crunch. There is less time to create and edit; more types and formats of content; more apps, software, and systems to learn. And we expect quality, accuracy, and consistency from ourselves because we take pride in our work. This session discussed how to address a multitude of modern dilemmas with a relatively old-school hack: a checklist.
This session was about how using a comprehensive checklist created and updated for a specific communication task can help you differentiate workflows, systems, and activities; spell out style and formatting details, track your progress, document metrics, and give you a sense of completion and peace of mind.The #NoEstimates Movement - Ryan Ripley
The #NoEstimates Movement explore the question of whether or not we need traditional estimates to make decisions about software development projects. By working in an agile way can we break down our work, inspect and adapt frequently, and deliver value to our customers. This presentation was give at Derby City Agile on June 15, 2018. http://derbycityagile.com/
How to improve the mobile product by 25% for only 5% of its creation budget -...
This document discusses how mobile app and game developers can improve their products by 25-40% through playtesting, which involves testing a product with target users early in the development process to gather feedback. Playtesting for only 5% of a product's budget can significantly increase its quality before release. The document outlines 10 best practices for effective playtesting, such as clearly identifying goals and metrics, observing users, and applying feedback iteratively. By addressing issues early, playtesting can help developers launch higher quality products faster and with fewer revisions than developing in an "information vacuum" without user input.
Metrics at Every (Flight) Level [2020 Agile Kanban Istanbul FlowConf]
Slides as presented on Dec 8, 2020 at FlowConf organized by Agile Kanban Istanbul. https://www.flowconf.com/
Organizational change often stalls out at departmental boundaries, whether that is IT or another division. How do we help organizations connect vertically and horizontally to realize the outcomes that they have when undertaking large-scale change efforts?
Join this session to learn from a case study of a bank that combined flight levels and metrics to bridge their departmental boundaries and recognize gains not only in software delivery effectiveness but unifying higher-level strategy.
Software Estimation in the Agile of Agile - Agile Indy North Side Meetup 2018
Estimation is difficult. It involved estimating the work, all of the things that stop us from doing our work, and the unforeseen. Instead, let's focus on the work at hand and reduce the complexity of software estimation.
To Estimate or Not to Estimate, Is that the Question? LeanAgileUS 2017
The document discusses the debate around estimating work in software development projects. It presents different perspectives on estimating, from never estimating to always estimating. It acknowledges that many factors contribute to variation in how long work takes, beyond just the estimated effort. Approaches like focusing on reducing waste, making work visible, and creating probabilistic forecasts based on delivery data can help address variation better than relying solely on upfront estimates. The question is reframed from whether to estimate or not, to what can be done to maximize value and reduce risk in planning and delivery.
B leach
This document discusses improving the quality of Microsoft Project schedules. It identifies ten common problems with schedule quality such as missing predecessors, successors, improper use of constraints and lags. Poor schedule quality can result in not knowing the true project finish date, rework, schedule slippage, budget overruns and lack of trust. The document promotes improving schedule quality by addressing issues such as ensuring tasks, resources, assignments and costs are accurate.
The Continuous Improvement Model
The document outlines the continuous improvement model which follows a plan, do, check, act cycle. It involves defining an ideal state and current reality, identifying root causes of any gaps, planning changes to address one cause, implementing changes, analyzing data to check results, and acting on learnings by planning the next improvement cycle. The goal is to continuously refine teaching practice through this ongoing process of planning improvements, testing changes, checking outcomes, and incorporating lessons learned.
Chicago Coders Conference 2017 - Metrics that matter
How many times have you been asked to deliver on metrics that did not make sense, that were counterproductive to the team’s effectiveness, or that were seemingly impossible to collect? Often times, the metrics being collected are the ones that are easy, but not necessarily the ones that matter. When it comes to software delivery, lean and agile practices and methodologies have clearly taken the lead. In the spirit of Kaizen, this session will take a look at the measures we can and should collect from agile teams, why these metrics are relevant and interesting, and how we can use them to help our teams continuously improve.
Portfolio kanban (St. Louis Agile Product Ownership Meetup)
Slides as presented at the St. Louis Agile Product Ownership Meetup, Dec. 10, 2018. https://www.meetup.com/Agile-Product-Ownership/events/tnhplqyxqbnb/
My Mozcon 2015 Slide Deck - Rocking Your CRO Efforts with Radical Redesigns
This is the slide deck for the presentation I gave at Mozcon 2015. The presentation was titled "Rocking Your CRO Efforts with Radical Redesigns".
Testing Small Agile Projects from Agile Vancouver Quality Conference 2014
Slides that support stories for the talk Testing Small Agile Projects given by Lanette Creamer, Director of Quality for Silicon Publishing, Inc, on May 26, 2014 in Vancouver, BC, Canada.
Getting Fit(ness Criteria)
This document discusses fitness criteria, which are defined by customers and stakeholders to determine if a product or service is fit for its intended purpose. Fitness criteria effectively act as key performance indicators and should guide improvement initiatives. The document provides examples of fitness criteria like delivery time and quality. It emphasizes that metrics only matter if they are recognized and cared about by customers, and that fitness criteria should be established through conversations with customers to understand what is important to them.
Documentation triage WTD 2018
Where do I start? The art and practice of documentation triage
WriteTheDocs Portland 2018
Recording: https://youtu.be/2EzIe-3LBwQ
Introdução a Monitoramento - DEM09 - Sao Paulo Summit
Aproveitando a infraestrutura dinâmica disponível por meio de provedores e containers da nuvem, podemos dimensionar como nunca antes. Entretanto, ao aumentar nossa escala, o monitoramento se tornou mais complicado e precisamos ajustar nossa estratégia de monitoramento de acordo. Nesta sessão, aprenda a dimensionar sua estratégia de monitoramento. Mostramos a você como enquadrar suas métricas para determinar quais dados coletar e como interpretá-los. Essa sessão é oferecida pelo parceiro AWS, Datadog.
Data Driven Postmortems - DEV201 - Sao Paulo Summit
This document discusses Datadog's approach to postmortem reviews following incidents or outages. It recommends collecting both technical and human data to understand all factors that contributed. Datadog's postmortem template includes sections summarizing the impact, how the issue was detected and responded to, analyzing the root causes, and identifying action items to prevent future occurrences. The goal is to have a blameless culture where teams can learn and improve through transparent sharing of experiences.
Walking the Talk
Three related coverage risks stood out when I begain to test a chatbot API for a medical symptom checker. With an infinite space of possible chats, how could we:
• look for unintended consequences of changes as we built the API
• discover some of the edge and corner cases bugs that would surely exist
• exercise the API to any significant extent after each iteration
To help mitigate these risks I built a client which would randomly walk through dialogs, unattended, and report on what it had found.
In this talk, I'll describe how I implemented that client by iteratively adding functionality that I hoped would facilitate my exploration of changes and fixes to the emerging API. I'll give examples of features that worked well (such as configuration of probabilities for different types of answers) and those that did not (such as checking for specific classes of medical outcome), explain how I built on top of the client to make a load testing tool, and think about what I'd do differently next time.
James_Thomas_Walk_The_Talk_BCS.pptx
Three related coverage risks stood out when I joined a new project to build a chatbot API for a medical symptom checker. With an infinite space of possible chats, how could we:
1. look for unintended consequences of changes.
2. discover some of the edge and corner cases bugs.
3. exercise the API significantly.
To help mitigate these risks I built a client which would randomly walk through dialogs, unattended, and report
on what it had found.
In this talk, I'll describe how I implemented that client by iteratively adding functionality that I hoped would
facilitate my exploration of changes and fixes to the emerging API. I'll give examples of features that worked
well (such as configuration of probabilities for different types of answers) and those that did not (such as checking for specific classes of medical outcome),
explain how I built on top of the client to make a load testing tool, and think about what I'd do differently next time.
Exploring with Automation
When considering how automation can be useful in testing, many people think only about identifying difference from some expected behaviour, for example with unit tests.
Much of my testing is about exploration, about learning, about finding things that might matter that we haven't already thought about. In this talk, I'll discuss how I use automation to help me to do that. In particular I'll demo some ways in which I ask questions of the product and use automation to find expedient ways to get answers.
How to Test Anything
Presented at https://www.onlinetestconf.com/program-spring-otc-2020/
Sometimes you’re asked to start testing in a context that is not ideal: you’ve only just joined the project, the test environment is broken, the product is migrating to a new stack, the developer has left, no-one seems quite sure what’s being done or why, and there is not much time.
Knowing where to begin and what to focus on can be difficult and so in this talk I’ll describe how I try to meet that challenge.
I’ll share a definition of testing which helps me to navigate uncertainty across contexts and decide on a starting point. I’ll catalogue tools that I use regularly such as conversation, modelling, and drawing; the rule of three, heuristics, and background knowledge; mission-setting, hypothesis generation, and comparison. I’ll show how they’ve helped me in my testing, and how I iterate over different approaches regularly to focus my testing.
The takeaways from this talk will be a distillation of hard-won, hands-on experience that has given me
* an expansive, iterative view of testing
* a comprehensive catalogue of testing tools
* the confidence to start testing anything from anywhere
People problems
My lightning talk at the Cambridge Agile Exchange on how traditional management books have lots to offer us, even in a modern, agile, working environment. In particular, management done well is all about people.
When Support Calls
Testers are said to be advocates for the customer, but when do most testers come face to
face with a real-life customer? I don’t mean internal stakeholders, but the people at the sharp end
of things, the ones actually using the software. Rarely, I find. Which is why it can be a SHOCK!
to be asked to participate in a customer support call. It’s an unusual situation, there’s pressure, the
customer is watching, something needs fixing, and there’s a deadline ... of yesterday. Gulp. But don’t
worry! You’re on the call because a colleague values your input. Perhaps you’re great at analysis, or
lateral thinking, or problem-solving. Maybe you have deep knowledge of your product, or the whole
ecosystem, or the historical angle. You could be there for questions, or answers, or honesty when you
don’t have either. These kinds of tools from your testing toolbox are valuable on support calls and in
this talk I’ll say how and why. I’ll also give an intro to customer support, talk about how to prepare for
calls, what to do during and after them, and - importantly - what you can take away personally, for
your product, and for your team.
From SoftTest 2018, http://softtest.ie/wp-content/uploads/2018/08/SoftTest_Programme_2018_20180829.pdf
Testing vs Chicken
The document discusses how recruiters can understand a candidate's potential for testing during the recruitment process. It suggests exploring the candidate's materials, conversation skills, and performance on exercises to gauge suitability. Specifically, recruiters should look at a candidate's thinking, reasoning, explaining abilities (the yolk) as well as their reporting, behavior, consistency (the white) to get a sense of their testing fit and history. The goal is to mission, audition, and explore the candidate's potential for delivering good testing through a limited recruitment window.
James thomas
Elisabeth Hendrickson’s book, Explore It!, contains this definition: “Tested = Checked + Explored”. When I read it, I was fascinated. “What does that mean?”, I asked myself, “what does it /really/ mean?”
This talk described the journey I undertook to understand it, and other definitions of testing that I found along the way, and then to come up with a new definition that filled the gaps I saw in the others, without losing the aspects of them that I felt were valid and useful.
Essentially, I formalised what testing is for me. And, now that I have my definition, I can ask myself in any given situation whether my actions are consistent with the way I believe I want to behave.
More Related Content
What's hot
How to improve the mobile product by 25% for only 5% of its creation budget -...
This document discusses how mobile app and game developers can improve their products by 25-40% through playtesting, which involves testing a product with target users early in the development process to gather feedback. Playtesting for only 5% of a product's budget can significantly increase its quality before release. The document outlines 10 best practices for effective playtesting, such as clearly identifying goals and metrics, observing users, and applying feedback iteratively. By addressing issues early, playtesting can help developers launch higher quality products faster and with fewer revisions than developing in an "information vacuum" without user input.
Metrics at Every (Flight) Level [2020 Agile Kanban Istanbul FlowConf]
Slides as presented on Dec 8, 2020 at FlowConf organized by Agile Kanban Istanbul. https://www.flowconf.com/
Organizational change often stalls out at departmental boundaries, whether that is IT or another division. How do we help organizations connect vertically and horizontally to realize the outcomes that they have when undertaking large-scale change efforts?
Join this session to learn from a case study of a bank that combined flight levels and metrics to bridge their departmental boundaries and recognize gains not only in software delivery effectiveness but unifying higher-level strategy.
Software Estimation in the Agile of Agile - Agile Indy North Side Meetup 2018
Estimation is difficult. It involved estimating the work, all of the things that stop us from doing our work, and the unforeseen. Instead, let's focus on the work at hand and reduce the complexity of software estimation.
To Estimate or Not to Estimate, Is that the Question? LeanAgileUS 2017
The document discusses the debate around estimating work in software development projects. It presents different perspectives on estimating, from never estimating to always estimating. It acknowledges that many factors contribute to variation in how long work takes, beyond just the estimated effort. Approaches like focusing on reducing waste, making work visible, and creating probabilistic forecasts based on delivery data can help address variation better than relying solely on upfront estimates. The question is reframed from whether to estimate or not, to what can be done to maximize value and reduce risk in planning and delivery.
B leach
This document discusses improving the quality of Microsoft Project schedules. It identifies ten common problems with schedule quality such as missing predecessors, successors, improper use of constraints and lags. Poor schedule quality can result in not knowing the true project finish date, rework, schedule slippage, budget overruns and lack of trust. The document promotes improving schedule quality by addressing issues such as ensuring tasks, resources, assignments and costs are accurate.
The Continuous Improvement Model
The document outlines the continuous improvement model which follows a plan, do, check, act cycle. It involves defining an ideal state and current reality, identifying root causes of any gaps, planning changes to address one cause, implementing changes, analyzing data to check results, and acting on learnings by planning the next improvement cycle. The goal is to continuously refine teaching practice through this ongoing process of planning improvements, testing changes, checking outcomes, and incorporating lessons learned.
Chicago Coders Conference 2017 - Metrics that matter
How many times have you been asked to deliver on metrics that did not make sense, that were counterproductive to the team’s effectiveness, or that were seemingly impossible to collect? Often times, the metrics being collected are the ones that are easy, but not necessarily the ones that matter. When it comes to software delivery, lean and agile practices and methodologies have clearly taken the lead. In the spirit of Kaizen, this session will take a look at the measures we can and should collect from agile teams, why these metrics are relevant and interesting, and how we can use them to help our teams continuously improve.
Portfolio kanban (St. Louis Agile Product Ownership Meetup)
Slides as presented at the St. Louis Agile Product Ownership Meetup, Dec. 10, 2018. https://www.meetup.com/Agile-Product-Ownership/events/tnhplqyxqbnb/
My Mozcon 2015 Slide Deck - Rocking Your CRO Efforts with Radical Redesigns
This is the slide deck for the presentation I gave at Mozcon 2015. The presentation was titled "Rocking Your CRO Efforts with Radical Redesigns".
Testing Small Agile Projects from Agile Vancouver Quality Conference 2014
Slides that support stories for the talk Testing Small Agile Projects given by Lanette Creamer, Director of Quality for Silicon Publishing, Inc, on May 26, 2014 in Vancouver, BC, Canada.
Getting Fit(ness Criteria)
This document discusses fitness criteria, which are defined by customers and stakeholders to determine if a product or service is fit for its intended purpose. Fitness criteria effectively act as key performance indicators and should guide improvement initiatives. The document provides examples of fitness criteria like delivery time and quality. It emphasizes that metrics only matter if they are recognized and cared about by customers, and that fitness criteria should be established through conversations with customers to understand what is important to them.
Documentation triage WTD 2018
Where do I start? The art and practice of documentation triage
WriteTheDocs Portland 2018
Recording: https://youtu.be/2EzIe-3LBwQ
Introdução a Monitoramento - DEM09 - Sao Paulo Summit
Aproveitando a infraestrutura dinâmica disponível por meio de provedores e containers da nuvem, podemos dimensionar como nunca antes. Entretanto, ao aumentar nossa escala, o monitoramento se tornou mais complicado e precisamos ajustar nossa estratégia de monitoramento de acordo. Nesta sessão, aprenda a dimensionar sua estratégia de monitoramento. Mostramos a você como enquadrar suas métricas para determinar quais dados coletar e como interpretá-los. Essa sessão é oferecida pelo parceiro AWS, Datadog.
Data Driven Postmortems - DEV201 - Sao Paulo Summit
This document discusses Datadog's approach to postmortem reviews following incidents or outages. It recommends collecting both technical and human data to understand all factors that contributed. Datadog's postmortem template includes sections summarizing the impact, how the issue was detected and responded to, analyzing the root causes, and identifying action items to prevent future occurrences. The goal is to have a blameless culture where teams can learn and improve through transparent sharing of experiences.
What's hot (14)
How to improve the mobile product by 25% for only 5% of its creation budget -...
How to improve the mobile product by 25% for only 5% of its creation budget -...
Metrics at Every (Flight) Level [2020 Agile Kanban Istanbul FlowConf]
Metrics at Every (Flight) Level [2020 Agile Kanban Istanbul FlowConf]
Software Estimation in the Agile of Agile - Agile Indy North Side Meetup 2018
Software Estimation in the Agile of Agile - Agile Indy North Side Meetup 2018
To Estimate or Not to Estimate, Is that the Question? LeanAgileUS 2017
To Estimate or Not to Estimate, Is that the Question? LeanAgileUS 2017
Chicago Coders Conference 2017 - Metrics that matter
Chicago Coders Conference 2017 - Metrics that matter
Portfolio kanban (St. Louis Agile Product Ownership Meetup)
Portfolio kanban (St. Louis Agile Product Ownership Meetup)
My Mozcon 2015 Slide Deck - Rocking Your CRO Efforts with Radical Redesigns
My Mozcon 2015 Slide Deck - Rocking Your CRO Efforts with Radical Redesigns
Testing Small Agile Projects from Agile Vancouver Quality Conference 2014
Testing Small Agile Projects from Agile Vancouver Quality Conference 2014
Introdução a Monitoramento - DEM09 - Sao Paulo Summit
Introdução a Monitoramento - DEM09 - Sao Paulo Summit
Data Driven Postmortems - DEV201 - Sao Paulo Summit
Data Driven Postmortems - DEV201 - Sao Paulo Summit
More from James Thomas
Walking the Talk
Three related coverage risks stood out when I begain to test a chatbot API for a medical symptom checker. With an infinite space of possible chats, how could we:
• look for unintended consequences of changes as we built the API
• discover some of the edge and corner cases bugs that would surely exist
• exercise the API to any significant extent after each iteration
To help mitigate these risks I built a client which would randomly walk through dialogs, unattended, and report on what it had found.
In this talk, I'll describe how I implemented that client by iteratively adding functionality that I hoped would facilitate my exploration of changes and fixes to the emerging API. I'll give examples of features that worked well (such as configuration of probabilities for different types of answers) and those that did not (such as checking for specific classes of medical outcome), explain how I built on top of the client to make a load testing tool, and think about what I'd do differently next time.
James_Thomas_Walk_The_Talk_BCS.pptx
Three related coverage risks stood out when I joined a new project to build a chatbot API for a medical symptom checker. With an infinite space of possible chats, how could we:
1. look for unintended consequences of changes.
2. discover some of the edge and corner cases bugs.
3. exercise the API significantly.
To help mitigate these risks I built a client which would randomly walk through dialogs, unattended, and report
on what it had found.
In this talk, I'll describe how I implemented that client by iteratively adding functionality that I hoped would
facilitate my exploration of changes and fixes to the emerging API. I'll give examples of features that worked
well (such as configuration of probabilities for different types of answers) and those that did not (such as checking for specific classes of medical outcome),
explain how I built on top of the client to make a load testing tool, and think about what I'd do differently next time.
Exploring with Automation
When considering how automation can be useful in testing, many people think only about identifying difference from some expected behaviour, for example with unit tests.
Much of my testing is about exploration, about learning, about finding things that might matter that we haven't already thought about. In this talk, I'll discuss how I use automation to help me to do that. In particular I'll demo some ways in which I ask questions of the product and use automation to find expedient ways to get answers.
How to Test Anything
Presented at https://www.onlinetestconf.com/program-spring-otc-2020/
Sometimes you’re asked to start testing in a context that is not ideal: you’ve only just joined the project, the test environment is broken, the product is migrating to a new stack, the developer has left, no-one seems quite sure what’s being done or why, and there is not much time.
Knowing where to begin and what to focus on can be difficult and so in this talk I’ll describe how I try to meet that challenge.
I’ll share a definition of testing which helps me to navigate uncertainty across contexts and decide on a starting point. I’ll catalogue tools that I use regularly such as conversation, modelling, and drawing; the rule of three, heuristics, and background knowledge; mission-setting, hypothesis generation, and comparison. I’ll show how they’ve helped me in my testing, and how I iterate over different approaches regularly to focus my testing.
The takeaways from this talk will be a distillation of hard-won, hands-on experience that has given me
* an expansive, iterative view of testing
* a comprehensive catalogue of testing tools
* the confidence to start testing anything from anywhere
People problems
My lightning talk at the Cambridge Agile Exchange on how traditional management books have lots to offer us, even in a modern, agile, working environment. In particular, management done well is all about people.
When Support Calls
Testers are said to be advocates for the customer, but when do most testers come face to
face with a real-life customer? I don’t mean internal stakeholders, but the people at the sharp end
of things, the ones actually using the software. Rarely, I find. Which is why it can be a SHOCK!
to be asked to participate in a customer support call. It’s an unusual situation, there’s pressure, the
customer is watching, something needs fixing, and there’s a deadline ... of yesterday. Gulp. But don’t
worry! You’re on the call because a colleague values your input. Perhaps you’re great at analysis, or
lateral thinking, or problem-solving. Maybe you have deep knowledge of your product, or the whole
ecosystem, or the historical angle. You could be there for questions, or answers, or honesty when you
don’t have either. These kinds of tools from your testing toolbox are valuable on support calls and in
this talk I’ll say how and why. I’ll also give an intro to customer support, talk about how to prepare for
calls, what to do during and after them, and - importantly - what you can take away personally, for
your product, and for your team.
From SoftTest 2018, http://softtest.ie/wp-content/uploads/2018/08/SoftTest_Programme_2018_20180829.pdf
Testing vs Chicken
The document discusses how recruiters can understand a candidate's potential for testing during the recruitment process. It suggests exploring the candidate's materials, conversation skills, and performance on exercises to gauge suitability. Specifically, recruiters should look at a candidate's thinking, reasoning, explaining abilities (the yolk) as well as their reporting, behavior, consistency (the white) to get a sense of their testing fit and history. The goal is to mission, audition, and explore the candidate's potential for delivering good testing through a limited recruitment window.
James thomas
Elisabeth Hendrickson’s book, Explore It!, contains this definition: “Tested = Checked + Explored”. When I read it, I was fascinated. “What does that mean?”, I asked myself, “what does it /really/ mean?”
This talk described the journey I undertook to understand it, and other definitions of testing that I found along the way, and then to come up with a new definition that filled the gaps I saw in the others, without losing the aspects of them that I felt were valid and useful.
Essentially, I formalised what testing is for me. And, now that I have my definition, I can ask myself in any given situation whether my actions are consistent with the way I believe I want to behave.
Theoreticus Prime vs Praktikertron
There is a perceived tension between theory and practice, and between theorists and practitioners. In this talk, we will propose and illustrate using a practical example that practice generates data and theory is the data which we care about. Rather than focusing on theory over practice or practice over theory, a choice of theory, practice, or both is driven by the data needed for a particular task and contextual factors.
Testing All the Way Down, and Other Directions
Slides from my talk at CEWT #3, http://qahiccupps.blogspot.co.uk/2016/11/testing-all-way-down-and-other.html
The idea that testing is or can be a recursive activity - or even fractal - has some currency. In that view, a test or experiment generates some data, which suggests new experiments, which generate some data, which suggest new experiments and so on. The kinds of activities being done at each stage will be self-similar and testing is used as a kind of microscope to focus in on some aspect of the system under test. Testing all the way down.
In this talk, I'll instead view testing as a number of different instruments that can be used in an arbitrary number of dimensions. Further, I'll suggest that testing can be applied not only to a system, but to descriptions of that system, to models of that system, to abstractions of that system, to a system which is testing that system, and to a system which is testing the system which is testing that system. And so on. It's testing all the way round.
I'll finish by proposing a definition of testing that I think might capture this wide applicability.
What is What is Professional Testing?
These are the slides that I presented at MEWT #5 https://mewtblog.wordpress.com/2016/02/06/what-is-professional-testing/
Bug-Free Software? Go For It!
I consider whether we as testers can be too closed-minded in our attitudes, whether there are schools of thought or approaches that, even if we care deeply about context, we are very unlikely even to consider and perhaps that we sometimes favour our reputation over giving ourselves the chance to do the best job that we can.
From CEWT#2, http://cewtblog.blogspot.co.uk/2016/02/cewt-2-abstracts.html
Your Testing is a Joke
My presentation from EuroSTAR 2015:
Your testing is a joke. Or, rather, some parts of some of the testing done by some people reading this will be somewhat analogous to some subset of what some people would accept as jokes. Sometimes. Language can be tricky like that. And that’s one of the things that makes it such a productive tool for jokes, and such a flawed tool for specification.
Edward de Bono, in his Lateral Thinking books, makes a strong connection between humour and creativity. Creativity is a key to testing, but jokes? Well, the punchline for a joke could be a violation of some expectation, the exposure of some ambiguity, an observation that no one else has made, or just making a surprising connection. Jokes can make you think and then laugh. But they don’t always work. Does that sound familiar?
At Linguamatics we have a weekly caption competition. I wondered what my process for creating entries was and as I spent more time thinking about it, I started to notice parallels with the way that I think about how I test. For instance, I might take each of the key entities in the picture and “factor” them – generate a list of features, related concepts, synonyms and so on. In testing I might then look for overlapping factors for potentially interesting test ideas, in the quest for a caption I might try to use the same approach to find an ambiguity and hence a joke.
In this talk I’ll take a genuine joke-making process and de-construct it to make comparisons between aspects of joking and concepts from testing such as the difference between a fault and a failure, oracles, heuristics, factoring, modelling testing as the exploration of a space of possibilities, stopping strategies, bug advocacy and the possibility that a bug, today, in this context might not be one tomorrow or in another.
Yes, there will be some jokes in the session. And I’ll try explain why the groans you’ll hear are a good sign too.
You're Having a Laugh
My talk delivered at the UK Test Management Forum on 2015-07-29. http://uktmf.com/?q=node/5283
As a test manager I don't test as much as I'd like to so I try to find ways to stay loose and ready for those occasions where I get the chance.
In this talk I'll describe one activity based on joking that I think can fit the bill. How? Well, the punchline for a joke could be a violation of some expectation, the exposure of some ambiguity, an observation that no one else has made, or just making a surprising connection. Jokes can make you think and then laugh. But they don't always work. Does that sound familiar?
It started with the weekly caption competition at Linguamatics where I noticed parallels in my approach to it and testing. For instance, I might take each of the key entities in the picture and "factor" them - generate a list of features, related concepts, synonyms and so on. In testing I might then look for overlapping factors for potentially interesting test ideas, in the quest for a caption I might try to use the same approach to find an ambiguity and hence a joke. Doing this, I've found analogies between joking and concepts from testing such as oracles, heuristics, factoring, stopping strategies, bug advocacy and the possibility that a bug, today, in this context might not be one tomorrow or in another.
I'm interested to find out from the audience what things they "just do" that they feel helps them.
It's Like That
This presentation talks about the use of analogy as a device for generating ideas at multiple levels of testing including test activity, methodology and reporting. In it, I associate analogy with lateral thinking and give an example of a specific analogy that I'm interested in at the moment.
More from James Thomas (15)
Recently uploaded
E-commerce Application Development Company.pdf
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
https://2024.springio.net/sessions/automated-software-refactoring-with-openrewrite-and-generative-ai/
OpenMetadata Community Meeting - 5th June 2024
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Artificia Intellicence and XPath Extension Functions
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
LORRAINE ANDREI_LEQUIGAN_HOW TO USE ZOOM
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
openEuler Case Study - The Journey to Supply Chain Security
openEuler Case Study - The Journey to Supply Chain Security
Measures in SQL (SIGMOD 2024, Santiago, Chile)
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
Oracle 23c New Features For DBAs and Developers.pptx
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise EditionEnvertis Software Solutions
Odoo ERP software
Odoo ERP software, a leading open-source software for Enterprise Resource Planning (ERP) and business management, has recently launched its latest version, Odoo 17 Community Edition. This update introduces a range of new features and enhancements designed to streamline business operations and support growth.
The Odoo Community serves as a cost-free edition within the Odoo suite of ERP systems. Tailored to accommodate the standard needs of business operations, it provides a robust platform suitable for organisations of different sizes and business sectors. Within the Odoo Community Edition, users can access a variety of essential features and services essential for managing day-to-day tasks efficiently.
This blog presents a detailed overview of the features available within the Odoo 17 Community edition, and the differences between Odoo 17 community and enterprise editions, aiming to equip you with the necessary information to make an informed decision about its suitability for your business.ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Presentation from Ghazal Aakel and Eric Jochum at the GSD Community Stage Meetup on June 6th, 2024
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-fusion-buddy-review
AI Fusion Buddy Review: Key Features
✅Create Stunning AI App Suite Fully Powered By Google's Latest AI technology, Gemini
✅Use Gemini to Build high-converting Converting Sales Video Scripts, ad copies, Trending Articles, blogs, etc.100% unique!
✅Create Ultra-HD graphics with a single keyword or phrase that commands 10x eyeballs!
✅Fully automated AI articles bulk generation!
✅Auto-post or schedule stunning AI content across all your accounts at once—WordPress, Facebook, LinkedIn, Blogger, and more.
✅With one keyword or URL, generate complete websites, landing pages, and more…
✅Automatically create & sell AI content, graphics, websites, landing pages, & all that gets you paid non-stop 24*7.
✅Pre-built High-Converting 100+ website Templates and 2000+ graphic templates logos, banners, and thumbnail images in Trending Niches.
✅Say goodbye to wasting time logging into multiple Chat GPT & AI Apps once & for all!
✅Save over $5000 per year and kick out dependency on third parties completely!
✅Brand New App: Not available anywhere else!
✅ Beginner-friendly!
✅ZERO upfront cost or any extra expenses
✅Risk-Free: 30-Day Money-Back Guarantee!
✅Commercial License included!
See My Other Reviews Article:
(1) AI Genie Review: https://sumonreview.com/ai-genie-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIFusionBuddyReview,
#AIFusionBuddyFeatures,
#AIFusionBuddyPricing,
#AIFusionBuddyProsandCons,
#AIFusionBuddyTutorial,
#AIFusionBuddyUserExperience
#AIFusionBuddyforBeginners,
#AIFusionBuddyBenefits,
#AIFusionBuddyComparison,
#AIFusionBuddyInstallation,
#AIFusionBuddyRefundPolicy,
#AIFusionBuddyDemo,
#AIFusionBuddyMaintenanceFees,
#AIFusionBuddyNewbieFriendly,
#WhatIsAIFusionBuddy?,
#HowDoesAIFusionBuddyWorks
Using Xen Hypervisor for Functional Safety
An update on making Xen hypervisor functionally safe and enhancing its usage in automotive and industrial use cases
E-commerce Development Services- Hornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Recently uploaded (20)
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
openEuler Case Study - The Journey to Supply Chain Security
openEuler Case Study - The Journey to Supply Chain Security
Oracle 23c New Features For DBAs and Developers.pptx
Oracle 23c New Features For DBAs and Developers.pptx
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
We Don't Know?
- 1. WE DON’T KNOW? James Thomas @qahiccupps qahiccupps.blogspot.com CEWT #7. 2019-11-24
- 2. @qahiccupps
- 3. WE ARE IN THE QUALITY BUSINESS @qahiccupps
- 4. QUALITY Value to some person (Weinberg) Conformance to requirements (Crosby) Response to bugs in production (Sussman/Garvin) @qahiccupps
- 5. QUALITY, FOR US A positive attribute Meeting intended purpose Satisfactory outcome (for all stakeholders) Value to someone who matters @qahiccupps
- 6. WE DON’T KNOW WHAT QUALITY IS @qahiccupps
- 7. BUG Property of a product that threatens its value (RST 3.0) Bugs someone (Bach) Causes an unnecessary or unreasonable reduction in quality (BBST) @qahiccupps
- 8. BUG, FOR US Unforeseen or undesirable reaction or behaviour Perceived failure to meet expectation Difference between desired and perceived An entry in Bugzilla @qahiccupps
- 9. WE DON’T KNOW WHAT BUGS ARE @qahiccupps
- 10. TESTING Executing a program with the intent of finding errors (Meyers) To find information that informs critical decisions (Kaner, Bach, Pettichord) Interact with SUT, observe behaviour, compare to expectations (Hendrickson) @qahiccupps
- 11. TESTING, FOR US Activity of assessing the quality of a thing A process between software development and EOL Ensures software behaves as expected/meets requirements Uncovering unknowns @qahiccupps
- 12. WE DON’T KNOW WHAT TESTING IS @qahiccupps
- 13. @qahiccupps
- 14. @qahiccupps
- 15. THE CORRECT ANSWER TO MANY QUESTIONS ABOUT TESTING IS “WE DON’T KNOW (FOR SURE)” @qahiccupps
- 16. WE DON’T KNOW WHAT WE ARE DOING But let’s keep that to ourselves, eh? @qahiccupps
- 17. @qahiccupps
- 19. Selected Credits • http://www.jkuat.ac.ke/directorates/daqa/list-of-senate-approved- programs/qa/ (QA logo) • https://bemestyle.com/products/snoopy-my-job-is-top-secret-even- shirt/ (Snoopy shirt) • https://www.peopleandprocess.ie/online-data-protection-training- course/top-secret-stamp/ (Top Secret stamp) • https://ansonanalytics.com/316-321-338-fiduciaries/confusion- 311388_1280/ (confusion)