Dan Ashby: Recent Episodes
None
How good are the communities that you are part of? Also, why don’t different communities that revolve around different crafts mix more? I love the testing communities. I also love the Agile communities. I’m also getting more involved with some Leadership communities that are fabulous. And some compliance & regulatory communities. And of course, I’m […]
In my last blog post, I shared my views on quality regarding goodness, value, and correctness. In this post, I’d like to share a model that I’ve been using for a few years in my past few companies, to describe different perspectives of quality and how they relate, as well as where testing activities fit […]
What’s the quality of your product? What’s the first thing you think about when hearing this question? Is it difficult to answer? For some reason, it feels like most people in software, when building software, tend to overfocus on “correctness”: “it works correctly”, “it works as expected”, “it meets all the specified requirements”, “Everything just […]
Philip Crosby has a big reputation as being a quality leader in the manufacturing industry, having authored many books on quality between 1968 and 1999. Some of his well known work that he’s quoted on regularly include: “quality is free”, “zero defects through prevention”, and his “4 absolutes of quality”. Although Crosby spoke of these […]
I recently attended an Agile workshop for new joiners at my company, where as part of the workshop, the agile manifesto and principles were presented. For those of you that haven’t seen the manifesto in a while, here they are: The manifesto seems to have stood the test of time. I’ve not seen any edits […]
Welcome to the final part on this series about the relationship between Testing and Product Risks.In part one, I discussed the idea and benefits of talking about testing product risks instead of talking about types of testing. If you missed that post, you can view it here.In part two, I then went on to discuss […]
Welcome to part two of this three part series on the relationship between Testing and Product Risks. In part one, I discussed the idea and benefits of talking about testing product risks instead of talking about types of testing. If you missed that post, you can view it here. In this second part, I’ll talk […]
This is the first post of a three posts about the relationship between Testing and Product Risks. In this post, I’m introducing the idea of focusing the conversations about testing on being related to types of risks over the common way of talking about testing in terms of types of testing. Types of testing? Or […]
It’s really surprising how many people believe that code coverage and test coverage are the same thing. I don’t know where this confusion has stemmed from, but from scouring around the internet, it seems to be a common challenge that people switch between code coverage and test coverage interchangeably, probably subconsciously too. They are not […]
We test. From the moment an idea is derived, the plan and approach of how to test it has already begun. Going beyond the idea of merely approaching code as testers – tasked with preparing software for delivery, we approach testing as modern day technologists; reigning in process, testing, tooling and enhancing communication under the […]
The #NoTesting hashtag is having a bit of a resurgence recently, so I thought I would jump on the bandwagon and write down my opinions on the whole thing. The term is very confusing to say the least. Many people take it to mean “don’t do any testing”, which is understandable that they interpret it […]
There has been lots of talk recently about “failing” and “failing fast”. This is actually an extremely complex topic that can be difficult to grasp. It’s not actually about failing. The topic of “failing” is actually all about learning. When we think about the properties of learning, we can break it down into various […]
The Automation Triangle (or pyramid) has continually caused a bit of a stir in the testing world. It has been mislabelled many times to be called a “testing” triangle. It has been abused in many companies by being followed as a “test strategy”. It has been butchered in ways that cause further misunderstandings and has […]