2 ms·
To me, the big hurdle is more likely to be culture than a lack of resources. It's a team that doesn't find value in writing tests. That may be due to the way de
by brudgers 10y ago
To me, the big hurdle is more likely to be culture than a lack of resources. It's a team that doesn't find value in writing tests. That may be due to the way deadlines are structured, management assigned priorities, low incentives for pursuing the potential benefits of writing more tests, or unfamiliarity with testing practices.
It's only in the last case that resources are on the critical path to change. And all the other potential causes come before the point where changing the culture is practical.
My advice: as the new person on the team it might be better to approach changing the culture as a mid-term to long term objective. A hard sell 'everybody [meaning you] need to start writing tests' has an air of 'you are doing it wrong' about it.
Now the team may be doing it wrong and it is logically possible a new member might show everyone the light. The odds of that happening in any given case are probably very very low, human nature being what it is and it being 2016. By which I mean that if a team isn't already pushing for more tests, then there's either a good reason or a bad reason and neither is likely to change over night.
A longer term approach is to show people the benefits of tests. Write tests yourself and high quality code to go with them and demonstrate the benefits directly. Or to put it another way, show that your time writing tests makes your life and other people's lives easier and do it because it's the right thing and despite other people not writing tests and don't tell people the should write tests. Let them come to it on their own.
Good luck.