4 ms·
If you have a good pipeline to prod, should be okay. You should hopefully have plenty of automated tests to ensure it doesn't get to prod if there are errors.
by lapser 4y ago
If you have a good pipeline to prod, should be okay. You should hopefully have plenty of automated tests to ensure it doesn't get to prod if there are errors.
- axelthegerman 4y agoshould be okay is definitely not enough for me to ship things to production. And while I do have automated tests, they might sometimes stub system calls as I'm mostly testing my code to keep things stable and fast. I'd rather explicitly declare my dependencies and use the same container for development, test and production to feel much more confident that it includes actually everything that's needed.
- bigpod 4y agowith good pipeline and knowledge about your app you should be able to ensure it works without much of a problem
- Volundr 4y agoI think a "good pipeline to prod" with sufficient automated tests to ensure nothing is broken is the exception not the rule. Even in places that think/say they have a "good pipeline to prod". It's something that takes a shocking amount of engineering effort to do well, and tons of discipline to maintain.
- lapser 4y agoTotally agree. I've joined companies where there was literally zero test coverage. All tests were done manually. But then if you have bad test coverage, then you shouldn't be using something like this.
- EddySchauHai 4y agoHire a test engineer to manage all of that - it’s a full time job but an important one!