What does testing being everyone's responsibility actually mean? Testing is the headlights of the project from 'Lessons Learned in Software Testing' is our first talking point. Software testing is more than pass/fail. #AADays2019
Does this analogy make sense when we're driving in broad daylight? Testing can be expensive. We need to make it as efficient and valuable as possible. Without testing, how do we know the state of quality in our software? #AADays2019
We need more than headlights. We need fuel gauges, drivers ability, speedometer, GPS measurements etc. Our end state is driven by our business values. We get credit for reducing cost and earning revenue #AADays2019
Exploratory testing is essential. We need to put it in a context that helps people understand the value that it offers. 'Testing gives visibility. Quality tells you how far we need to go.' Quality is value to some person. It's subjective. #AADays2019
Build the right product. Build the product right. Support the product. From an ops perspective, can we support the product? How do we know we have built the right product and built it right? We need to ask these questions as early on as possible #AADays2019
Infrastructure, process and people all impact quality. Psychological safety plays a big part in software quality. If your team doesn't feel safe enough to raise risks then you're threatening the quality of the product. #AADays2019
There are many new threats to quality. Bloated process for example. The Spotify model is not a one size fits all approach. Spotify's values may not match your company's values. #AADays2019
Speed to market is a new quality attribute. Who are testers to stand in the way of that? Yes, it involves difficult conversations, but we can definitely help with that quality attribute. Build times, flaky tests etc all help with this attribute. #AADays2019
Recoverability is another new quality attribute. Observability both pre production and in production is extremely important. We need to be able to tell what's going on with our product. Its up to us to bring these conversations to our teams. #AADays2019
Software teams are moving more towards deploying a service. How can an API be consumed by an external developer? Is our documentation useful for consumers? Our automation should be easy for other team members to pick up #AADays2019
@charrett invented the word 'Qualitability'. We don't talk enough about how to make quality visible. How easy it is to see the state of quality at any point in time? #AADays2019
Metrics make quality visible. Team based metrics, business outcomes, emphasis is learning, hindsight downsides are what our metrics should focus on. Metrics need to be valuable to the team. Teams need to have autonomy around deicisions to do with quality. #AADays2019
Highlight downsides* not hindsight. We need to be aware of how metrics can be misused. Use it as a focus on learning rather than a tool to blame people for not meeting targets. #AADays2019
We need to make quality improvement visible. Track improvement over time. Make gradual improvement over big changes. Change through coaching and not doing #AADays2019
We should look at ways that we can pair better with the business. We often demo to business stakeholders, so why don't we ask business stakeholders to demo to us? What do they do? How can we support them? #AADays2019
@charrett believes that a large part of the quality person of the future will be a quality coach role. This role compromises of many different aptitudes. #AADays2019
Software testing is the headlights, quality is the journey and business outcomes are the destination. Really great opening keynote from @charrett #AADays2019
