Here we’ll continue on from the first and second posts in this series. We made a good start with looking at the idea of correctness and attempting to encode our assumptions about that correctness in the form of code that … Continue reading
We’re going to continue on from the first post in this series by starting to build our Benchmarker application. In the first post we considered design pressure on value. Now we’re going to get into correctness. Value and correctness are … Continue reading
I talked before about whether testers should be developers and I also talked about the intersection of development and testing with a focus on testability. Here I want to make that intersection a little more actionable by considering an example … Continue reading
Part of achieving quality in software means treating testability as a primary quality attribute. Once you do that, you can then adapt your requirements and development styles from that point of view. Whether you call that “agile”, “lean”, “scrappy” or … Continue reading
Like most disciplines, testing has some so-called truisms that get passed around, many often being blindly accepted. The problem is often that our discipline requires a bit of nuance that the truisms — even if accurate — tend to gloss … Continue reading
I personally think the answer to my title question is an obvious “yes.” But I do see a lot of discussions about how the DevOps movement and/or culture has “killed” testing or has removed the need for testers. Let’s talk … Continue reading
There are groups of testers out there right now denying that the term “manual testing” — or the reality of the term — does exist or has ever existed. To me this is a bit of historical revisionism. Let’s talk … Continue reading
I talked before about tradition and dogma in the testing field. It’s often interesting to see how the idea that get passed off for wisdom in the testing world come about. Let’s take one example and break it down.
I see a lot of vocal pundits in the testing world saying that artificial intelligence (by however they choose to define that) is no threat to future testing. I’ll ignore for a moment that most of these pundits get AI … Continue reading
There is a distinction between “being a programmer” and “being a developer.” Yet those two terms get conflated in our industry quite a bit. The idea of a tester also gets conflated with … which? Programmer or Developer? That very … Continue reading
There is still so much wrong with how testers — even those who will write automation — are interviewed. I talked about this already regarding how technical test interviews are broken and about interviewing technical testers more broadly. Is there … Continue reading
There’s a book I really enjoyed that I believe every tester should read. Actually, anybody who has to communicate should read it. The book is called Don’t Be Such a Scientist by Randy Olson. And it talks about the need … Continue reading
There is a relatively common sentiment that tester roles, as opposed to the testing activity, should disappear entirely. We see that a bit with descriptions of jobs like “Software Development Engineer in Test” (SDET) which basically just means “developer who … Continue reading
The title of this post indicates a sentiment you’ll often see. “Testing is the art of …” and then fill in some word or phrase. While I get the intent behind this, the word or phrase used to complete the … Continue reading
