All of the projects I've done over the last few years have been "agile" - the company I work for actually offers agile training. Officially, all projects are w

All of the projects I've done over the last few years have been "agile" - the company I work for actually offers agile training. Officially, all projects are written using TDD, and all estimates for all tasks should include time to write Acceptance and Unit following the suggestions in "Growing object oriented software guided by tests", along with any integration tests with external software that may be required. Even unofficially, I've never seen anyone consider a story "complete" until there's sufficient automated tests for it, and there's been at least some manual testing. Another thing we strongly encourage (and do) as part of Agile is regular retrospective meetings on our software development process. If our testing strategy (or lack thereof) was causing Fear during refactoring, prod bugs, or difficulty during maintenance, this would be bought up during such a meeting and addressed. I'm not saying you're not "doing Agile", but your experience very strongly does not match mine.