Python 3 adoption

Posted Apr 17, 2015 9:52 UTC (Fri) by asaz989 (guest, #67798)
In reply to: Python 3 adoption by dlang
Parent article: Python 3 adoption

At my previous work, apt-get dist-upgrade was not something you just ran routinely - in fact, it is an Even Scarier Thing To Do than a code deploy, since often unit test environments don't test the base system. Hence, very very slow staged deployments.

Python 3 adoption

Posted Apr 17, 2015 23:58 UTC (Fri) by zlynx (guest, #2285) [Link] (1 responses)

This is why unit tests are good but not sufficient. They only show that code works the way that the testers think it does.

I especially hate mock objects, because now the code is being tested against a pretend version of the real thing and the mock probably has bugs.

So without integration tests on real libraries, services and hardware, the code has not really been tested at all.

Python 3 adoption

Posted Apr 18, 2015 7:25 UTC (Sat) by cortana (subscriber, #24596) [Link]

Why not both? Unit tests are still useful for testing how your code will react when a collaborator behaves in a way that is documented, but is difficult to reproduce in a test environment.