Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Quality Does not Belong with
the Tester!
Maaret Pyhäjärvi
Email: <maaret@iki.fi> | Twitter: maaretp
Maaret Pyhäjärvi
Nimeä...
HIGH
EXPECTATIONS
DIFFERENT
FROM BETTER
TO WORSE
Adding a Tester Can Make Things
Worse
• Perception change: from everyone’s work to
one person’s specialty
– Same work twic...
Quality and the Developer
• From slap in the face to shared insight of
first experience through pairing
• Learning to thin...
Summary
• I’m not responsible for production quality,
developers are
– I help but my efforts are easy to attenuate with
wh...
TestBash: Quality Does Not Belong With the Tester!
Upcoming SlideShare
Loading in …5
×

TestBash: Quality Does Not Belong With the Tester!

742 views

Published on

Talk from TestBash 2015.

Published in: Software
  • Be the first to comment

  • Be the first to like this

TestBash: Quality Does Not Belong With the Tester!

  1. 1. Quality Does not Belong with the Tester! Maaret Pyhäjärvi Email: <maaret@iki.fi> | Twitter: maaretp Maaret Pyhäjärvi Nimeä | Attribution (Finland) http://creativecommons.org/licenses/by/1.0/fi/ http://creativecommons.org/licenses/by/1.0/fi/deed.en
  2. 2. HIGH EXPECTATIONS
  3. 3. DIFFERENT
  4. 4. FROM BETTER TO WORSE
  5. 5. Adding a Tester Can Make Things Worse • Perception change: from everyone’s work to one person’s specialty – Same work twice: the developer and the tester? – Slap in the developer’s face with different results • Feedback did not work well with lack of design & programming skills – F ear and Consequences of not getting good enough • The fixing backlog – More developer work
  6. 6. Quality and the Developer • From slap in the face to shared insight of first experience through pairing • Learning to think of connected concepts, not just connected code both before and after implementation • Relying on ‘own testing’ and skipping tester-testing as experiment • Making testing a programming problem: automation
  7. 7. Summary • I’m not responsible for production quality, developers are – I help but my efforts are easy to attenuate with what the developers do • Working with the culture of collaboration makes a huge difference – Experiments with a reluctant team – Avoiding clear roles keeps everyone alert – Nobody is “just” something these days

×