No please tell me, how did you learn to write unit test which cover all the crazy data configurations users are able to come with.
Boundary value analysis? Machine state transitions testing? Equivalence partitioning?
There are heaps of techniques one can use to identify which data points and combinations are useful to test. Some of these techniques even take a peek at your code to highlight the possible pain points.
LOL! You think someone who's drunk the unit testing kool-aid has even heard of any of that?
You have to start somewhere. If I have to choose between a world where people never test and one where they test but aren't very good at it yet, I'll definitely take the latter.
Of course, I'm still filled with rage when I find a cargo-cult suite of unit tests. But it's so much easier to convince those people to write smarter tests than it is to deal with the team that has no time to write tests because they're spending all their time debugging.
By being able to design software that doesn't need or allow crazy data configurations.
My whole mantra is don't manage complexity: avoid it.
You nailed it - thanks for the absolutely spot on comment.
Design is the key word here. It requires thought, it requires intelligence and it requires multiple people's input.
Re:How Facebook Ships Code
by TazeTSchnitzel on Thursday July 05, 2012 @07:15AM
(#4202577)
You're right.
Now that I think about it, I doubt Facebook is that careful, considering how often they break things.
It just works.
In the last 5 years, we've never hooked a debugger to production instance or given access to a developer.
In that time, we've pushed approximately 912 billion SQL transactions through the system and 24 billion page hits (most of our stuff is backend non OLTP).
That's how it's done.