[sametmax]

I can imagine many more types of bugs:

- fatigue bugs

- inattention bugs

- typo bugs

- unknown unknown bugs

- bad merge bugs

- upgrade bugs

- multiple teams or devs screwing up together bugs

I mean, you can always stretch the meaning of "assumption" to match any of those. But to me realistically "assumption" is more about when you conscientiously suppose things.

After all "unexpected outcome of the emergent behavior of basic rules" could be pretty much be applied to anything. And when your definition can be applied to anything, it's not that much of a definition.

[williamdclt]

I suppose most of those could/should be tested against, and bring back every bug under "assumption bug". But yeah, I agree with you, this definition is not wrong it's just unhelpful

[eevilspock]

- copy-n-paste bugs

[OJFord]

That's more obviously an assumption failure though - the copy-paster has assumed that the top hit or similar-looking thing is going to work, without properly understanding it and modifying it as necessary.