Karlo Smid July 29, 2012 Testing in 140 characters (or less) #3 learn testing Reading Time: < 1 minute@QualityFrog That’s true; /a performance/ doesn’t pass or fail. A performance focuses attention on interesting stuff. @testobsessed— Michael Bolton (@michaelbolton) July 19, 2012 My eye saw ‘profs’ at first. RT @jamesmarcusbach: “Testing cannot demonstrate the absence of bugs. NOTHING can do that, not even proofs.”— Michael Bolton (@michaelbolton) July 21, 2012 “What we see depends mainly on what we look for.”-John Lubbock #testing #quality ow.ly/cpEg1— Gerald Weinberg (@JerryWeinberg) July 22, 2012 @imccowatt Taleb says that failure prevention is never noticed, and that’s “monstrously unfair”.— Michael Bolton (@michaelbolton) July 23, 2012 @imccowatt @paulholland_twn Exactly: oracles can be used generatively, in the moment, or retrospectively. #testing— Michael Bolton (@michaelbolton) July 23, 2012 The implicit theme of Rapid Software #Testing is: testing work doesn’t have to suck, neither in the doing nor the results. @jamesmarcusbach— Michael Bolton (@michaelbolton) July 25, 2012 If you’re worried about regression, ramp up review, research, pairing, refactoring, #testing, investigation. Checks alone won’t do. #agile— Michael Bolton (@michaelbolton) July 27, 2012 Worry about regression implies worry about weak knowledge of the code, excessive speed, sloppiness. Consider fixing those. #agile #testing— Michael Bolton (@michaelbolton) July 27, 2012 Related Posts:An Example Of Exploratory Testing Vasca da Gama Charter By…Testing From Trenches, Copy Paste Message At My Bank ATMTesting From Trenches, Example Of Wrong Definition For Black… Previous Article Testing in 140 characters (or less) #2 Next Article My contribution in spreading what is software testing Leave a Comment Leave a Reply Cancel replyYou must be logged in to post a comment.