I tweeted a quote today that I found to be very insightful.
A poignant reminder of why I'm here. pic.twitter.com/H9Nkbnm4Qt
— Jon Kruger (@JonKruger) April 8, 2014
You could take this two different ways. I take it to mean that I need to just the right amount of testing in order to be confident that my code works and will continue to work.
You could also see it another way, as pointed out by some others:
@JonKruger I think the line which follows that quote is also important; as an industry, that level of confidence might not bee too high.
— Steven Harman (@stevenharman) April 8, 2014
@JonKruger #coding pic.twitter.com/CV98xQuKDe I admire KBeck but disagree.. Absent good #Tests coder confidence is myth.. #OverConfident = Bugs
— SeattleFan4Dan4 (@TJWilk_WA) April 8, 2014
There are those out there that think that testing is a waste of time and I could see some of them taking a quote like this and saying, “I’m a good enough developer that I don’t need tests in order to write code that works!” (I heard someone say those exact words once, sadly.)
@JonKruger Most developers do the same thing… they just have way too much confidence in their coding skills. ;)
— jared richardson (@jaredrichardson) April 8, 2014
The discrepancy is due to what the word “confidence” means in this quote. If it’s just confidence that it works now, then you might be fine without tests, but if it’s confidence that your code will still be working a year from now after someone else has had to modify it, then you probably want tests. (Heck, I want tests so that I can change my own code tomorrow!) I find that the problem is that on many teams, developers define confidence as “good enough that QA can look at it” and then achieving true “confidence” is someone else’s problem.
Maybe we should change the pronouns.
We (the team) get paid for code that works, so our philosophy is to tests as little as possible to reach a given level of confidence.
Now this changes things. What’s the best way to test as little as possible? Automate all the tests that should be automated. Let QA spend time doing valuable things like exploratory testing instead of doing loads of manual regression tests. Funny how you can turn everything on it’s head when you take what is perceived to be an individual’s problem and make it everyone’s problem!
Leave a Comment