Always easier to start as an individual. I managed to retrain myself over the years from being a cowboy coder. Since I'm one of the lead developers, I just sta

Always easier to start as an individual. I managed to retrain myself over the years from being a cowboy coder. Since I'm one of the lead developers, I just started practicing what I preached. Every new system I build has unit tests, and every time I integrate with a legacy system or another system someone works on, I write tests for it. I also work with that engineer to see if they need to add tests on their end. Anytime something written in the cowboy days in production breaks, I check if I should write a test. (Normally I need to.) This way it spread "virally" from me. For mass adoption among the team, try to get your test workflow down so it's easy to explain and pickup.