The Thinking Tester, Evolved
Upcoming SlideShare
Loading in...5

The Thinking Tester, Evolved



Keynote for CAST2012

Keynote for CAST2012



Total Views
Views on SlideShare
Embed Views



9 Embeds 2,676 2541 66 41 10 5 5 4 3 1


Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

The Thinking Tester, Evolved The Thinking Tester, Evolved Presentation Transcript

  • The Thinking Tester EvolvedElisabeth HendricksonBlog: testobsessed.comTwitter: @testobsessedAvailable from: Last updated July 17, 2012
  • Image courtesy of The Tire Zoo Under Creative Commons Attribution
  • Changes: Business Approaches Build MeasureLearn
  • Changes: Technology Product ArchitectureCloud Mobile Infrastructure Tools Test &CI Environment Operations Management Automation
  • Changes: the Pace of Change Source: Wikimedia Commons, courtesy of Ray KurzweilSee
  • Changes: Development Cycles Then: Phased Cycles. specialists in silos. Months or Years Between Releases Analyze Design Implement Test RELEASE!Now: Short iterations. Cross functional teams collaborating. Release cycles measured in days, weeks.
  • Changes: Tester Jobs A survey of job advertisements: In 2010: we examined 187 ads. Of those, 112 (60%) required programming skills. Another 39 (20%) listed programming as a nice to have. That’s 80%. In 2011: we examined 164 ads. 102 (62%) required programming. Another 38 (23%) listed it as a nice to have. That’s 85%. In 2012: Anecdotally, 100% of the 4 ads on the job board at this conference (as of this AM) either required or desired programming. Conclusion: testing as a profession is changing.
  • Re-frameImage courtesy of greckor Under Creative Commons Attribution
  • any activity that yields aboutthe extent to which our , our , and the are .
  • Tested = Checked + Explored
  • A variation on Brian Marick’s Agile Testing Quadrants  Confirm Investigate Risks toBusiness Business-facing Internal expectations Quality Attributes Risks to Tech- Technology- Internal nology facing Quality expectations Attributes
  • The Thinking Tester Analytical,Relentlessly curious, Observant, Skeptical, Empiricist, Critical thinking Investigator.
  • We’re not “just” testers Product Programmer owner Projectarchitect manager … Technical writer
  • Image courtesy of Brian Snelson Under Creative Commons Attribution
  • Testing is so importantthat everyone does it. Intentions ?? Implementation Actual Need ?
  • The Thinking Tester, EvolvedSees testing as a team activitySeeks to contribute & supportthe team in gathering empiricalevidence along all dimensionsApplies testing skills inperforming any activityPushes for earlier testing andtighter feedback loopsMeets their stakeholders wherethey live
  • New PathsImage courtesy of Nana B Agyei Under Creative Commons Attribution