From Newsgroup: comp.programming

The Big List of Naughty Strings is an evolving list of strings
which have a high probability of causing issues when used as
user-input data. This is intended for use in helping both automated
and manual QA testing; useful for whenever your QA engineer walks
into a bar.

<https://github.com/minimaxir/big-list-of-naughty-strings>

The “walks into a bar” reference is to this <http://www.sempf.net/post/On-Testing1>:

QA Engineer walks into a bar. Orders a beer. Orders 0 beers. Orders
999999999 beers. Orders a lizard. Orders -1 beers. Orders a
sfdeljknesv.

Because that’s what testing is all about...
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.programming

On Thu, 4 Sep 2025 01:19:26 -0000 (UTC), I wrote:

The “walks into a bar” reference is to this <http://www.sempf.net/post/On-Testing1>:

QA Engineer walks into a bar. Orders a beer. Orders 0 beers. Orders
999999999 beers. Orders a lizard. Orders -1 beers. Orders a
sfdeljknesv.

Because that’s what testing is all about...

Why did that suddenly come to mind? Because I just read about this
incident where someone got the AI at a fast-food drive-through to
accept an order for 18,000 cups of water <https://www.zdnet.com/article/someone-ordered-18000-cups-of-water-at-an-ai-drive-thru-now-fast-food-chains-are-reconsidering/>.

Debugging actual human-written code is hard enough; how do you debug
an AI?
--- Synchronet 3.21a-Linux NewsLink 1.2