— Viola Korte (@vioble) March 24, 2017
— Ministry of Testing (@ministryoftest) March 24, 2017
<eyebrow /> I have never been called an umbilical cord before, nor could I be more honoured. Thank you, Prof. Harry Collins. #testbash
— Michael Bolton (@michaelbolton) March 24, 2017
— Martin (马丁) Hynie (@vds4) March 24, 2017
"oooh, look at these lovely story points… thanks so much for making them" – no customer ever
— Gojko Adzic (@gojkoadzic) March 21, 2017
The more I learn about cryptography, the more I think Alice and Bob should probably just talk in person.
— Paul Reinheimer (@preinheimer) March 13, 2017
@KentBeck what happens if you shift focus from "accurate estimation" to fulfilling your customers' needs?
— [object Object] (@sleepyfox) March 10, 2017
When Hacker News commenters say "I could build that app in a weekend!" I think of this chart of how Slack decides to send a notification. pic.twitter.com/LopicAyzkL
— Matt Haughey (@mathowie) March 3, 2017
When I see "They don't get testing", I rarely see enough critical thinking applied to understanding the valid reasons for the perception gap
— Martin (马丁) Hynie (@vds4) February 27, 2017
#Testers, one tweet please. What did you do before testing? What's the most significant difference (in any respect) between that and now?
— James Thomas (@qahiccupps) February 18, 2017
— sharath byregowda (@sharathb) February 15, 2017
— James Thomas (@qahiccupps) February 10, 2017
Something's _technically_ wrong. As opposed to… actually wrong? Really wrong? Not wrong? pic.twitter.com/OfE65chCdO
— Alastair Smith (@alastairs) February 9, 2017
— Neil Younger (@norry_twitting) February 7, 2017
— Mike Talks (@TestSheepNZ) January 30, 2017
Breaking: Programmer accused of writing unreadable code refuses to comment.
— Bruce Lawson (@brucel) January 16, 2017
The Big List of Naughty Strings (strings likely to cause issues as input) https://t.co/HZNswX2GfY
— Hacker News (@newsycombinator) January 15, 2017
State what (sometimes why) is expected in automated check assert messages; not how/why you think it may fail in the future. #TestAutomation
— Ben Simo (@QualityFrog) January 10, 2017
I got 99 problems but I'll write a test for each one.
— Tom Oram (@tomphp) January 8, 2017
Two rules of being a great team member:
1. Don't be a dick
2. Assume positive intent on the part of your team mates
— Geoff Watts (@geoffcwatts) January 7, 2017
A: "But if all of our programmers are pairing, won't they write half as much code?"
B: "No, hopefully they'll write even less than that"
— Ben Rady (@benrady) January 6, 2017
We'd like to get 50 awesome articles and guides published this year, can't do that without you. Come help us. https://t.co/aA5WBQkVNo
— Ministry of Testing (@ministryoftest) January 3, 2017