[tetonraven]

I would suggest committing to just try it. If you give an honest try at putting quality and testing center-stage in your development, I think you'll start to see the value and eventually get hooked on it. Start with unit tests and grow from there. There was a time when I thought unit tests were a "nice-to-have-sometimes" sort of thing. Now, I fully embrace TDD and writing tests (first) is an integral part of my development. This has grown into a comprehensive test strategy with automation at various levels. Maybe it sounds simplistic, but just start with forcing yourselves to write unit tests for all new code and see where it takes you. Be sure you are writing good tests, though, otherwise you'll reinforce a non-test approach by seeing poor outcomes; there are a lot of sources on how to write good unit tests.