3 ms·
I, very recently, began writing a suite of tests to go along-side a complex mobile app. During a stand-up meeting I (somewhat) proudly announced that for a part
by alexc05 11y ago
I, very recently, began writing a suite of tests to go along-side a complex mobile app. During a stand-up meeting I (somewhat) proudly announced that for a particularly onerous piece of business logic, I had 100% coverage with tests that run in less than a second.
The project manager in the room was worried about the time it was going to take. All the developers in the room piped up to say "oh, no, this actually saves time"
The next day, I found myself in a private meeting room with the project manager and my line manager.
Both were trying to tell me that unit tests are not part of the scope of the project, not were they approved and, that I was to stop writing them.
Manual QA was the way to go at the end of the project.
Yesterday, I was in the office from 10am to 2am on a national holiday addressing issues arising from QA.
It was unproductive to spend the day wondering how many of those defects I'd have been able to catch months ago if I'd been writing tests all along.
When you're the only one on your team who respects the tests, the world feels like a very bleak place.
- douche 11y agoIt does suck how much of the time you wind up in the situation that, to make any progress, you have to work in secret behind some smokescreen of other less useful work, to keep the micromanaging and the hemming and hawing from consuming any improvements. It's not uncommon that orders of magnitude more time wasted in debate and FUD'ing round on things than it takes to actually do them.
- chris_wot 11y agoSkunk works the tests. Maintain a private branch that management never sees and run them anyway. When they fail, fix the issue. You'll possibly seen as a genius, but you certainly won't be working on public holidays.