3 ms·
Writing tests, if you have to mock everything each time because you can't duplicate the production, isn't really hard. It's long and boring. If I have to ballp
by orwin 3y ago
Writing tests, if you have to mock everything each time because you can't duplicate the production, isn't really hard. It's long and boring.
If I have to ballpark an estimate on a tool/project, I say upfront something like: it'll take me 6 days olus a day for very limited tests, so 7. Twice as much with almost complete coverage. But each time we'll have to improve/refractor, a bit of that time will be recovered.
Basically I ask how important the new project will be,without asking that (because 99% of the time the response is 'very').
I'm realizing I just say I was managing my managers. Should I ask for senior devops position now? :)
- tdeck 3y agoIt's interesting, I often find the tests take me twice as long as the implementation. 1/6 of the effort would be a dream.
- orwin 3y agoI was unclear, I apologize. The 'quick testing' isn't really testing imho. (basically no unit test, small integration tests with the data I could steal from the prod DB). It takes around 20% of the time (or 1/6 in my example taken from my last project). The 80% coverage that include mocking and unit test double that time. I am always extremely clear with my estimates being just that, estimates, and that a complete testing double dev time. Most of the time I'm told 'we don't care right now', but on some projects, management accept longer dev time for more stability and less bugs (we build internal tools).