[afandian]

> I don't think even the most undisciplined of developers just writes code and assume that it works.

What does 'works' mean? Implements this narrow bit of functionality / change? Or doesn't break all the other features it's piled on top of?

It's not a question so much of whether a developer thinks they're testing, so much as what they're trying to achieve.

[collyw]

The same as writing a test that "passes". It appears to do what is expected for the set of inputs given.