Every day, in some discussion about testing, someone talks about the need for “balance between automated testing and manual testing”. This seems to me to be a supremely unhelpful way to think about testing work. First, and once again, testing is neither manual nor automated. No one in any other cogntive, intellectual, investigative domain talks about their work that way; and no one in any such domain allows other people … Read more
This is a lightly-edited version of a post I made on LinkedIn, which in turn was a followup to the previous post. “We have to run a full regression test suite on every build!” First: you don’t have to do anything. There is no law of nature, nor any human regulation, that says you must repeat any particular test. You choose to do things. (You don’t have to automate. You … Read more
This post picks up on a small LinkedIn essay from a few months back. There’s a fair amount of preamble here before I talk about regression testing as such. Be careful; you might have heard about testing and checking from people who don’t talk about it the ways we do in Rapid Software Testing (RST). If you’re familiar with RST, maybe you’re fine jumping here. If you’re not so familiar … Read more
This is a lightly-edited excerpt from a longer blog post that you’ll find here. I recommend you read it too, but if you’re short on time, here’s the core of it. If you care about understanding the status of your product, you’ll probably care about testing it. You’ll want testing to find out if the product you’ve got is the product you want. If you care about that, you need … Read more
“Language models” is typically interpreted as a compound noun, something that models language. A model is an idea in your mind, an activity, or an object (such as a diagram, a list of words, a spreadsheet, a role play, a person, a toy, an equation, a demonstration, or a program…) that represents (literally! re-presents!) another idea, activity, or object (such as something complex that you need to work with or … Read more
There’s a significant mistake that people might make when using LLMs to summarize a requirements document, or to produce a test report. LLMs aren’t all that great at summarizing. That’s definintely a problem, and it would be a mistake to trust an LLM’s summary without reviewing the original document. The bigger mistake is in believing that the output, the artifact, is the important thing. We might choose to share a … Read more
One of the reasons that software development and testing are screwed up is because people often name things carelessly. Jerry Weinberg was fond of pointing out that “floating point” was the kind of math where the decimal point stayed in the same place, where in “fixed point”, the decimal point moves around. People talk about “serverless computing”, when they really mean “computing using someone else’s servers”. “No-code testing tools”… well, … Read more
This is a lightly-edited version of a repost on LinkedIn. The original post contained a photo of a conference talk. The presenter was a dude in a Spiderman costume. (I’ve always wondered how many Spiderman costumes we’d see at meetings of doctors, or journalists, or theoretical physicists. But I digress.) The screen displayed a slide “Everyone cares about User Experience, but no one cares about Developer Experience.” Spiderman outfit notwithstanding, … Read more
Code is created by people. HTML elements are code, which is created by people. As part of developing those elements, people can tag them with attributes (including but not limited to “id”) that make them easy to find, via tools, for testing purposes. This can be done deliberately and consciously, or automatically as part of the creation of the element. When that doesn’t happen, testers and developers have difficulty locating … Read more
Yet another post plucked and adapted from the walled garden of LinkedIn “What the large language models are good at is saying what an answer should sound like, which is different from what an answer should be.” —Rodney Brooks, https://spectrum.ieee.org/gpt-4-calm-down Note for testers and their clients: the problem that Rodney Brooks identifies with large language models applies to lots of test procedures and test results as well. People often have … Read more