Yes, no design, no documentation, minimal testing. Just working software. Yeah, right.
That isn't Agile!
Agile simply asks you to prioritise working software over complete documentation. Nowhere does it say that the documentation should be absent, nor does it place anything other than working software above documentation.
It should be patently obvious to all that failing to go through a conventional design process never produces anything of value; it becomes development-by-evolution, and almost all evolutionary experiments become extinct.
An old colleague of mine had a wonderful phrase: "A week's worth of keyboard-bashing can sometimes preclude the need for an hour's thought". That pretty much describes the approach of so many people who claim to be "Agile" (and clearly aren't).