If you provided a little context for the remark, maybe people could agree or disagree more coherently. For example, if you contended that some agile teams overemphasize checking at the expense of testing (or the opposite), maybe we could talk about that. Maybe if you were to say, “for me, more traditional methods reduce the uncertainty that agile development teams address by writing unit checks,” then we could share experiences that were or were not consistent with yours. As it stands, I think most of us would be at a loss as to what you're talking about here.

Regards,

—Michael B.

The agile manifesto does not even cover software testing nor states how much testing is needed or in what form your testing should be in. Agile is meant to be fluid.

And on the converse, just because you write a ton of tests does not even remotely make you agile.

I think this is a common misconception.