3 ms·
You don't need "sophisticated testing frameworks" to validate code quality. TDD should be caked into your culture. Even if it's not as detailed as some larger c
by semerda 13y ago
You don't need "sophisticated testing frameworks" to validate code quality. TDD should be caked into your culture. Even if it's not as detailed as some larger companies.
Pushing code to production should be an automated task that anyone can setup these days using something as simple as Fabric. Heck, code in reverse release scripts too.
And if you have few boxes in your farm/lb then push to half of them, monitor and if all good push to the rest. You should have 0 downtime in this model. Even with 2 instances under a load balancer.
All this requires some initial time expenditure but over the long term saves you a ton of time, headaches, lost sleep etc and allows you to push at anytime of the day.
- kirillzubovsky 13y agoI definitely agree on the long-term benefits. At the moment, I think we are still changing too many things too fast to keep a non-core set of tests. We are actually using our friends from RainforestQA to do a bulk of testing, which has been really helpful, but some things still fall through the cracks. Like an ajax script failing due to a new caching implementation, that only starts to fail after enough events have taken place. That's when it's really helpful to know that a large number of your users is offline, and they are not all going to trip up at the same time.