Karlo Smid July 18, 2012 Testing in 140 characters (or less) #2 learn testing Scientists don’t like anomalies in the same way devs and testers don’t like bug – @c_wiedemann #CAST2012— Anand and Komal (@testinggeek) July 17, 2012 Software testing is boring – for non-testers. We have to find ways to expose effects of testing & make ppl aware of it. @mgaertne #cast2012— lisacrispin (@lisacrispin) July 17, 2012 Everybody is a tester; it just happens that we’re really good at it. @testobsessed #CAST2012— Markus Gärtner (@mgaertne) July 17, 2012 I believe testers “make stuff up” a lot less than testers uncover and make explicit things that have been latent and implicit. #CAST2012— Michael Bolton (@michaelbolton) July 17, 2012 Saying “programmers can’t test” is silly; they do it all the time. Like everyone else, they can’t see ALL errors in their own work. #testing— Michael Bolton (@michaelbolton) July 17, 2012 @michaelbolton We uncover ways in which value is destroyed, in ways that have often not been considered— Iain McCowatt (@imccowatt) July 17, 2012 @imccowatt Yes. I’d say s/destroyed/threatened, though; the latter encompasses the former. Oracles aren’t perfect; testers aren’t judges.— Michael Bolton (@michaelbolton) July 17, 2012 @imccowatt Yes; not judge and jury, but exercising judgment about requirements, interpretations, risks, value,…— Michael Bolton (@michaelbolton) July 17, 2012 Note every tester should code. We end up taking awesome testers and turn some into awful programmers @testobsessed #CAST2012— Michael Larsen (@mkltesthead) July 17, 2012 @mkltesthead At least as bad, maybe worse: starting with an awful programmer and turning him into an awful tester. @testobsessed— Michael Bolton (@michaelbolton) July 17, 2012 Previous Article Croatian character on trip to Guadalajara Next Article Testing in 140 characters (or less) #3 Leave a Comment Leave a Reply Cancel replyYou must be logged in to post a comment.