(https://sphotos-a.xx.fbcdn.net/hphotos-prn1/540109_10151013930811816_707326686_n.jpg)
You really need to look at this certification program: http://www.codinghorror.com/blog/2007/03/the-works-on-my-machine-certification-program.html
what is this "Development" thingie you guys are talking about...
Quote
...Cause one code path in the code you're checking in to be executed. The preferred way to do this is with ad-hoc manual testing of the simplest possible case for the feature in question. Omit this step if the code change was less than five lines, or if, in the developer's professional opinion, the code change could not possibly result in an error.
Well, YEAH, trust us, it's a minor change and should not impact anything, we're PROFESSIONALS, you gotta know our opinion is solid!
http://www.codinghorror.com/blog/2008/03/the-first-rule-of-programming-its-always-your-fault.html
LIES! Damn lies! (Unless you're one of these guys (http://www.codinghorror.com/blog/2010/02/the-nonprogramming-programmer.html). Or these guys (http://www.codinghorror.com/blog/2007/02/why-cant-programmers-program.html). :shudder: )
You have no idea how many times I've flipped out over people only doing happy path testing, that's where coverage tools kick a little ass (before I kick a lot of ass).
Too bad they suck up so many resources *disable* lol
Man, that's a hilarious caption for that picture.