Testing in 140 characters (or less)

In this blog post I will put all important testing tweets. My plan is to use this blog post as repository of testing tweets. All those tweets are important for every tester to become even better tester. I am using "embed this tweet" tweeter feature.




The first principle of critical thinking: things could be different. That's a core principle in #testing, too. No coincidence.
— Michael Bolton (@michaelbolton) July 14, 2012


RT @jamesmarcusbach "Testers need to know the difference between observing a phenomenon and knowing the whole truth about it." #testing
— Michael Bolton (@michaelbolton) July 14, 2012

Usabliity BASICS: the user wants to accomplish tasks, NOT exercise functions in your product. Learn and honour the difference. #testing
— Michael Bolton (@michaelbolton) July 14, 2012


"It is necessary to relax your muscles when you can. Relaxing your brain is fatal--Stirling Moss, British racing driver #thinking
— Gerald Weinberg (@JerryWeinberg) July 15, 2012

Arrange software teams so that most of the communication necessary to develop a feature happens within a single team.
— Dale Emery (@dhemery) July 15, 2012



Arrange software teams so that each team is downstream from its own work.
— Dale Emery (@dhemery) July 15, 2012

@adamgoucher - first heuristic - build your own framework and tool chain because problem is specific to the project #CAST2012
— Anand and Komal (@testinggeek) July 16, 2012



Selecting tool set and language which make sense - don't use same language as development for the sake of it - @adamgoucher #CAST2012
— Anand and Komal (@testinggeek) July 16, 2012




Turn off all the third parties components / tests in functional test environment - explore feature switch / toggle @adamgoucher #CAST2012
— Anand and Komal (@testinggeek) July 16, 2012




Refresh machine, get VMs and run tests on different machines to identify if it's too much attached to machine @adamgoucher #CAST2012
— Anand and Komal (@testinggeek) July 16, 2012




Start with study, not plan. #CAST2012 keynote
— Markus Gärtner (@mgaertne) July 16, 2012




Tripp Babbitt: "A focus on costs always increases them."Me: Still, *consider* /opportunity cost/.#CAST2012 #testing
— Michael Bolton (@michaelbolton) July 16, 2012




Surely the people doing the work are those who should design the work. If so, managers' role is to test & tune the work; remove blocks.
— Michael Bolton (@michaelbolton) July 16, 2012

















Labels: