Last night, my wife was out on an errand in our car. She parked it, entered the store, and came out again. She tried to start the car. It wouldn’t start. She called home to consult with me. We tried a couple of things over the phone. We considered a couple of possible problems. From what I could tell, the starter motor wasn’t engaging. Not exactly a surprise, because I … Read more
Every fifteen minutes or so, in testing blogs, on LinkedIn, at conferences, or on the job, someone raises the question of “why test automation projects fail”. Perhaps the question keeps coming up because there are so many failure modes, and so many possible answers. Here’s one answer, though: “test automation projects” are software development projects, and all software development projects are vulnerable to failure. One of the bigger and more … Read more
I’ve had a long career in this silly business. All the way along, one of the sillier things that people have said is this: “Testing slows down the project.” This is roughly equivalent to saying that looking out the windshield and attending to the dashboard slows down the journey. Sometimes people say that discovering problems slows down the project, but that’s not true either. Discovering problems can dispel the illusion … Read more
An online chat with a coaching student. I want to set up a Zoom meeting with her tomorrow. At some point during the last couple of days, there was a new version of the Zoom plugin for Outlook. Maybe there was a new version of Outlook, too; I’m not sure. But in any case…
It’s common these days to hear people say that they don’t want to focus on finding bugs; they want to focus on preventing bugs. They want to focus on “building quality in”. Let’s face it: building quality in is a pretty great idea, and preventing bugs from reaching customers is a really good thing. On this, reasonable people agree. To prevent bugs from reaching customers, you’ll have to become a … Read more
On my iPad, I’m reading a discussion on LinkedIn. A reply piques my interest, and I want to alert a colleague to it. I tap on the dots in the upper right. The options offered are are “Message (the author of the reply)”, “Share via…”, and “Report”. I tap on “Share via…” Nothing happens. I move to my computer, and go to the same reply. The three dots in the … Read more
So this happened today… I mean, there’s supposedly a book about that. It gets a little wackier. I don’t know how the algorithms are coming up with the categories in the lower half of the list.
Selenium! Playwright! Cypress! Postman! There’s constant hubbub around these tools and others primarily focused on checking output—and now the din is getting louder about low-code or no-code tools for checking output. (Last year I reviewed a couple of those, here and here. Did these companies use their own tools to test their own tools? Either a Yes or No answer would be disturbing.) Want some heuristics for choosing tools of … Read more
I sit down with a coffee, retrieve my mail, and open it up. I’ve received a spammy kind of message. It provides a link to unsubscribe. The link returns {“code”:1020,”message”:”fail”}. I’ve received another spammy kind of message, this time from Yellow Pages (yp.ca). In the text, it is addressed to “[{Recipient.FirstName}]”. The message asks “How do you show up online?” Better than YellowPages shows up in my inbox, I hope. … Read more
Deep testing — testing that maximizes the change of finding every elusive bug that matters — is the kind of testing work that engages and motivates serious testers. Developers tend to prefer shallow testing that doesn’t disrupt the developer’s mindset and the developer’s focus on getting the danged product built. (Before anyone gets too upset, note that the shallowness of shallow testing is a feature, not a bug. There’s lots more … Read more