DevelopsenseLogo

Talking About Testing

Frequently, both online and in face-to-fact conversations, testers express reservations to me about making a clear distinction between testing and checking when talking to others. It’s true: “test” is an overloaded word. In some contexts, it refers to a heuristic process: evaluating a product by learning about it through experiencing, exploring and experimenting; that’s what testers refer to when they’re talking about testing, and that’s how we describe it in … Read more

Risk in the Wild

In several of our Rapid Software Testing classes, for the last four years at least, these three slides have part of our materials on risk: And then what do you know?! This happened. Here’s the link. And this happened too… Here’s the link to that. Don’t say we didn’t warn you.

Premature Formalization

Formal Bow Tie and Shirtfront

“The real problem is that programmers have spent far too much time worrying about efficiency in the wrong places and at the wrong times; premature optimization is the root of all evil (or at least most of it) in programming.” -Donald Knuth, The Art of Computer Programming Most of the time testing shouldn’t be too formal — unless you want to miss lots of bugs. To test something formally means … Read more

Testing Deep and Shallow (3): Determination

After almost a year of the blog lying fallow, it’s time to continue the series on Testing Deep and Shallow that begins here. (Shallow testing (not an insult!) is testing that has a chance of finding every easy bug. Deep testing maximizes the chance of finding every elusive bug that matters.) Premise 6 of Rapid Software Testing is about cost and value. “We commit to performing credible, cost-effective testing, and … Read more

Sailing Out of Harbour

Well… the new developsense.com site has been up for a week, and it seems stable. Time for an actual post. First: this site is now modern-looking and responsive. There are some nice new features (including a catalog of videos), and many more to come. I think it all looks great, and the reviews have been overwhelmingly positive. That’s really down to one person. This site (along with the Rapid Software … Read more

Testing Deep and Shallow (2): “Shallow” is a feature, not an insult!

When we talk about deep and shallow testing in the Rapid Software Testing namespace, some people might assume that we mean “deep testing” is good and decent and honourable, and that we mean “shallow” to be an insult. But we don’t. “Shallow” is not an insult. Depth and shallowness are ways of talking about the thoroughness of testing, but they’re not assessments of its value. The value or quality or … Read more

Testing Deep and Shallow (1): Coverage

Many years ago, I went on a quest. “Coverage” seemed to be an important word in testing, but it began to occur to me that I had been thinking about it in a vague, hand-wavey kind of way. I sensed that I was not alone in that. I wanted to know what people meant by coverage. I wanted to know what I meant by coverage. In the Rapid Software Testing … Read more

‘Demonstration, Experiment, and Testing’ by Michael Bolton #ATAGTR2021

The comments for this video posted on YouTube read:

Keynote Session by Michael Bolton, “Demonstration, Experiment, and Testing” at #ATAGTR2021; for the Agile Testing Alliance
Our Speaker – Michael Bolton

Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn’t realize they could solve.

It was the 6th Edition of “Global Testing Retreat” happened on 11-12 December 2021.

To know more about the upcoming events, please visit: https://ataevents.org/

Expert Panel on Failures of Software Industry around Testing & Quality

Expert Panel on Failures of Software Industry around Testing & Quality
Webinar with Anna Royzman, Aprajita M, James Bach and Michael Bolton

FailQonf, 2021

Panel Topic: Inadequate and inefficient software testing practices can contribute to poor quality products released to customers. In this session, we’ll discuss different failures in software testing. We’ll aim to highlight and share experiences from the panel covering failures in both testing process/approach and individual tester level