Testing Blog

How Google Tests Software - Part Seven

Thursday, May 26, 2011
Share on Twitter Share on Facebook
Google
Labels: James Whittaker

16 comments :

  1. VISHALMay 26, 2011 at 10:39:00 PM PDT

    That's a nice piece of information and guidance for the TE, helping TE to examine his much needed skills and to incorporate if missing some.

    ReplyDelete
    Replies
      Reply
  2. Ganesh SahaiMay 27, 2011 at 12:41:00 AM PDT

    on the similar lines there could be 'DE' development engineers.

    ReplyDelete
    Replies
      Reply
  3. furzedoMay 27, 2011 at 5:21:00 AM PDT

    Hi James,

    Thanks for sharing information about how the TEs add value to Google products. This is the post I have been waiting since you started this series about how Google tests software.

    I am trying to build a team of software quality assurance people and the skills set of a Google's TE is what I am looking for in the people I hire. However, at least here in Brazil, this is something REALLY hard to find. The market is full of "classic style" testers though.(By classic style tester I meant people who are more comfortable with writing and manually running long test scripts, that will be out of date as soon as the product is released).

    Does Google also face any kind of issue when hiring TEs? Any hints for me?

    Thanks again!

    ReplyDelete
    Replies
      Reply
  4. BrunoMay 27, 2011 at 10:05:00 AM PDT

    Great post James!

    Does this mean that TEs change projects more usually than SETs? [since they should go through different projects at later parts of the development lifecycle] this seems a better title for an SDET more focused on E2E testing.

    Keep the posts comming!

    ReplyDelete
    Replies
      Reply
  5. UnknownMay 27, 2011 at 1:19:00 PM PDT

    Love your post! I'm surprised to see "many of the top test managers in the company come from the TE ranks". I thought Google's management were dominated by developers.

    ReplyDelete
    Replies
      Reply
  6. James WhittakerJune 1, 2011 at 7:03:00 AM PDT

    @Weining: At Google, testers report to testers, not to developers.

    @Bruno: I don't have any data on job changes by title but my suspicion is that it is *easier* for TEs to change projects because they serve the users and not the code base.

    ReplyDelete
    Replies
      Reply
  7. deccandudeJune 2, 2011 at 11:00:00 AM PDT

    Great and very informative post, James. I also have got your book on Exploratory Testing and enjoyed it. It must be cool to work with folks like you and learn at the feet of the masters, so to speak.

    ReplyDelete
    Replies
      Reply
  8. SalilJune 2, 2011 at 1:43:00 PM PDT

    Nice read. I always have leaned towards/pitched for getting folks like TE's involved earlier as then they have higher chances of influencing functionality or feature set, and taking a swipe at the broader big picture problems - like interop with other products. (I would imagine that would lie outside the charter of SWT's?) If they come in later when a large part of the spec and usability has been baked in, aren't we really limiting their chances of success and if there is any impact unearthed by them, further risking release schedule?

    Thoughts?

    Regardless, Loved how you laid down the fluidity of the role of a TE and the leadership aspect! It is something very fundamental for a good TE to stand up and effect change where needed! TE's who are customer advocates are priceless!

    ReplyDelete
    Replies
      Reply
  9. RaghavJune 9, 2011 at 9:18:00 AM PDT

    Hey James,

    Awaiting your post on SETs - the continuation of part 6.

    Thanks,
    Raghav.

    ReplyDelete
    Replies
      Reply
  10. mitsuakimaruyamaJune 12, 2011 at 7:28:00 PM PDT

    Thank you for your always great posts.

    Generally the test engineers with extensive experience and broad perspective like TEs
    leave the test execution, and dedicated themselves to the test management.
    But such a career path, in some cases, narrow their perspective and dull their intuition.

    It seems that TEs activities include leading to a better place products and services.
    These activities may strongly dependent on individual ability and experience.
    For global products and services, It may be necessary to support to their activities by some systems.

    ReplyDelete
    Replies
      Reply
  11. R and The BoyzJune 14, 2011 at 12:17:00 PM PDT

    I am pleased to read that the Google Test Engineering department is once again appreciating the value of having Test Engineers on their projects. As one of the original group of Test Engineers at Google, I understand the value that a great exploratory tester with creativity, curiosity and good communication skills can add to the success of a project's deployment. You can run automation all day long and of course you will find issues and bugs in the code, but it takes a person to find those edge cases or issues that the actual end user might find. Ultimately we want the user to be happy and not frustrated with the product. Having a Test Engineer give it a once-over, based on extensive knowledge of testing techniques and how to exercise the code in ways that the developer never intended, is the best way to assure the success of the product for Google or any other company.

    ReplyDelete
    Replies
      Reply
  12. AnairdaJune 16, 2011 at 8:46:00 AM PDT

    Thank you for the "tutorial", it was very useful :)

    ReplyDelete
    Replies
      Reply
  13. hanumanJuly 22, 2011 at 1:23:00 AM PDT

    Thanks for the update.
    I am so happy to hear that google has introduced the TE role.
    Please post the information on eligible criteria to apply for the TE position in google.
    I am working as TE in a software firm.

    ReplyDelete
    Replies
      Reply
  14. Younus PoonawalaJuly 25, 2011 at 12:05:00 AM PDT

    Amazing article, it seems that here at Directi, India we also believe in more or less similar strategy. The TE's involve in later phases and analyse the break-points before shipment of a product.

    ReplyDelete
    Replies
      Reply
  15. Pekka MarjamäkiAugust 13, 2011 at 2:27:00 PM PDT

    Hi, James!

    What I wonder is that you refer to Exploratory testing with "exploratory testing with little to no planning". This confuses me as in exploratory approach the testing IS planned, but made less rigid and more reactive. Do you have exploratory experts as TEs? Do all TEs do exploratory testing? Do they do it RIGHT (according to your specification of Exploratory testing something is wrong)? But nonetheless fachinating to see the aspects of TE's jobs you have at Google. We are doing the same role clarification in our company so this is very enlightning.

    BR, Pekka

    ReplyDelete
    Replies
      Reply
  16. UnknownSeptember 12, 2011 at 4:15:00 AM PDT

    Thanks James for sharing the series. One question - how do you generally plan the swe:set:te ratio when forming a team? Is there some thumb rule?

    ReplyDelete
    Replies
      Reply
Add comment
Load more...

The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments.

  

Labels


  • TotT 104
  • GTAC 61
  • James Whittaker 42
  • Misko Hevery 32
  • Code Health 31
  • Anthony Vallone 27
  • Patrick Copeland 23
  • Jobs 18
  • Andrew Trenk 13
  • C++ 11
  • Patrik Höglund 8
  • JavaScript 7
  • Allen Hutchison 6
  • George Pirocanac 6
  • Zhanyong Wan 6
  • Harry Robinson 5
  • Java 5
  • Julian Harty 5
  • Adam Bender 4
  • Alberto Savoia 4
  • Ben Yu 4
  • Erik Kuefler 4
  • Philip Zembrod 4
  • Shyam Seshadri 4
  • Chrome 3
  • Dillon Bly 3
  • John Thomas 3
  • Lesley Katzen 3
  • Marc Kaplan 3
  • Markus Clermont 3
  • Max Kanat-Alexander 3
  • Sonal Shah 3
  • APIs 2
  • Abhishek Arya 2
  • Alan Myrvold 2
  • Alek Icev 2
  • Android 2
  • April Fools 2
  • Chaitali Narla 2
  • Chris Lewis 2
  • Chrome OS 2
  • Diego Salas 2
  • Dori Reuveni 2
  • Jason Arbon 2
  • Jochen Wuttke 2
  • Kostya Serebryany 2
  • Marc Eaddy 2
  • Marko Ivanković 2
  • Mobile 2
  • Oliver Chang 2
  • Simon Stewart 2
  • Stefan Kennedy 2
  • Test Flakiness 2
  • Titus Winters 2
  • Tony Voellm 2
  • WebRTC 2
  • Yiming Sun 2
  • Yvette Nameth 2
  • Zuri Kemp 2
  • Aaron Jacobs 1
  • Adam Porter 1
  • Adam Raider 1
  • Adel Saoud 1
  • Alan Faulkner 1
  • Alex Eagle 1
  • Amy Fu 1
  • Anantha Keesara 1
  • Antoine Picard 1
  • App Engine 1
  • Ari Shamash 1
  • Arif Sukoco 1
  • Benjamin Pick 1
  • Bob Nystrom 1
  • Bruce Leban 1
  • Carlos Arguelles 1
  • Carlos Israel Ortiz García 1
  • Cathal Weakliam 1
  • Christopher Semturs 1
  • Clay Murphy 1
  • Dagang Wei 1
  • Dan Maksimovich 1
  • Dan Shi 1
  • Dan Willemsen 1
  • Dave Chen 1
  • Dave Gladfelter 1
  • David Bendory 1
  • David Mandelberg 1
  • Derek Snyder 1
  • Diego Cavalcanti 1
  • Dmitry Vyukov 1
  • Eduardo Bravo Ortiz 1
  • Ekaterina Kamenskaya 1
  • Elliott Karpilovsky 1
  • Elliotte Rusty Harold 1
  • Espresso 1
  • Felipe Sodré 1
  • Francois Aube 1
  • Gene Volovich 1
  • Google+ 1
  • Goran Petrovic 1
  • Goranka Bjedov 1
  • Hank Duan 1
  • Havard Rast Blok 1
  • Hongfei Ding 1
  • Jason Elbaum 1
  • Jason Huggins 1
  • Jay Han 1
  • Jeff Hoy 1
  • Jeff Listfield 1
  • Jessica Tomechak 1
  • Jim Reardon 1
  • Joe Allan Muharsky 1
  • Joel Hynoski 1
  • John Micco 1
  • John Penix 1
  • Jonathan Rockway 1
  • Jonathan Velasquez 1
  • Josh Armour 1
  • Julie Ralph 1
  • Kai Kent 1
  • Kanu Tewary 1
  • Karin Lundberg 1
  • Kaue Silveira 1
  • Kevin Bourrillion 1
  • Kevin Graney 1
  • Kirkland 1
  • Kurt Alfred Kluever 1
  • Manjusha Parvathaneni 1
  • Marek Kiszkis 1
  • Marius Latinis 1
  • Mark Ivey 1
  • Mark Manley 1
  • Mark Striebeck 1
  • Matt Lowrie 1
  • Meredith Whittaker 1
  • Michael Bachman 1
  • Michael Klepikov 1
  • Mike Aizatsky 1
  • Mike Wacker 1
  • Mona El Mahdy 1
  • Noel Yap 1
  • Palak Bansal 1
  • Patricia Legaspi 1
  • Per Jacobsson 1
  • Peter Arrenbrecht 1
  • Peter Spragins 1
  • Phil Norman 1
  • Phil Rollet 1
  • Pooja Gupta 1
  • Project Showcase 1
  • Radoslav Vasilev 1
  • Rajat Dewan 1
  • Rajat Jain 1
  • Rich Martin 1
  • Richard Bustamante 1
  • Roshan Sembacuttiaratchy 1
  • Ruslan Khamitov 1
  • Sam Lee 1
  • Sean Jordan 1
  • Sebastian Dörner 1
  • Sharon Zhou 1
  • Shiva Garg 1
  • Siddartha Janga 1
  • Simran Basi 1
  • Stan Chan 1
  • Stephen Ng 1
  • Tejas Shah 1
  • Test Analytics 1
  • Test Engineer 1
  • Tim Lyakhovetskiy 1
  • Tom O'Neill 1
  • Vojta Jína 1
  • automation 1
  • dead code 1
  • iOS 1
  • mutation testing 1


Archive


  • ►  2025 (1)
    • ►  Jan (1)
  • ►  2024 (13)
    • ►  Dec (1)
    • ►  Oct (1)
    • ►  Sep (1)
    • ►  Aug (1)
    • ►  Jul (1)
    • ►  May (3)
    • ►  Apr (3)
    • ►  Mar (1)
    • ►  Feb (1)
  • ►  2023 (14)
    • ►  Dec (2)
    • ►  Nov (2)
    • ►  Oct (5)
    • ►  Sep (3)
    • ►  Aug (1)
    • ►  Apr (1)
  • ►  2022 (2)
    • ►  Feb (2)
  • ►  2021 (3)
    • ►  Jun (1)
    • ►  Apr (1)
    • ►  Mar (1)
  • ►  2020 (8)
    • ►  Dec (2)
    • ►  Nov (1)
    • ►  Oct (1)
    • ►  Aug (2)
    • ►  Jul (1)
    • ►  May (1)
  • ►  2019 (4)
    • ►  Dec (1)
    • ►  Nov (1)
    • ►  Jul (1)
    • ►  Jan (1)
  • ►  2018 (7)
    • ►  Nov (1)
    • ►  Sep (1)
    • ►  Jul (1)
    • ►  Jun (2)
    • ►  May (1)
    • ►  Feb (1)
  • ►  2017 (17)
    • ►  Dec (1)
    • ►  Nov (1)
    • ►  Oct (1)
    • ►  Sep (1)
    • ►  Aug (1)
    • ►  Jul (2)
    • ►  Jun (2)
    • ►  May (3)
    • ►  Apr (2)
    • ►  Feb (1)
    • ►  Jan (2)
  • ►  2016 (15)
    • ►  Dec (1)
    • ►  Nov (2)
    • ►  Oct (1)
    • ►  Sep (2)
    • ►  Aug (1)
    • ►  Jun (2)
    • ►  May (3)
    • ►  Apr (1)
    • ►  Mar (1)
    • ►  Feb (1)
  • ►  2015 (14)
    • ►  Dec (1)
    • ►  Nov (1)
    • ►  Oct (2)
    • ►  Aug (1)
    • ►  Jun (1)
    • ►  May (2)
    • ►  Apr (2)
    • ►  Mar (1)
    • ►  Feb (1)
    • ►  Jan (2)
  • ►  2014 (24)
    • ►  Dec (2)
    • ►  Nov (1)
    • ►  Oct (2)
    • ►  Sep (2)
    • ►  Aug (2)
    • ►  Jul (3)
    • ►  Jun (3)
    • ►  May (2)
    • ►  Apr (2)
    • ►  Mar (2)
    • ►  Feb (1)
    • ►  Jan (2)
  • ►  2013 (16)
    • ►  Dec (1)
    • ►  Nov (1)
    • ►  Oct (1)
    • ►  Aug (2)
    • ►  Jul (1)
    • ►  Jun (2)
    • ►  May (2)
    • ►  Apr (2)
    • ►  Mar (2)
    • ►  Jan (2)
  • ►  2012 (11)
    • ►  Dec (1)
    • ►  Nov (2)
    • ►  Oct (3)
    • ►  Sep (1)
    • ►  Aug (4)
  • ▼  2011 (39)
    • ►  Nov (2)
    • ►  Oct (5)
    • ►  Sep (2)
    • ►  Aug (4)
    • ►  Jul (2)
    • ►  Jun (5)
    • ▼  May (4)
      • How Google Tests Software - Part Seven
      • GTAC 2011 Open for Submission
      • How Google Tests Software - A Break for Q&A
      • How Google Tests Software - Part Six
    • ►  Apr (3)
    • ►  Mar (4)
    • ►  Feb (5)
    • ►  Jan (3)
  • ►  2010 (37)
    • ►  Dec (3)
    • ►  Nov (3)
    • ►  Oct (4)
    • ►  Sep (8)
    • ►  Aug (3)
    • ►  Jul (3)
    • ►  Jun (2)
    • ►  May (2)
    • ►  Apr (3)
    • ►  Mar (3)
    • ►  Feb (2)
    • ►  Jan (1)
  • ►  2009 (54)
    • ►  Dec (3)
    • ►  Nov (2)
    • ►  Oct (3)
    • ►  Sep (5)
    • ►  Aug (4)
    • ►  Jul (15)
    • ►  Jun (8)
    • ►  May (3)
    • ►  Apr (2)
    • ►  Feb (5)
    • ►  Jan (4)
  • ►  2008 (75)
    • ►  Dec (6)
    • ►  Nov (8)
    • ►  Oct (9)
    • ►  Sep (8)
    • ►  Aug (9)
    • ►  Jul (9)
    • ►  Jun (6)
    • ►  May (6)
    • ►  Apr (4)
    • ►  Mar (4)
    • ►  Feb (4)
    • ►  Jan (2)
  • ►  2007 (41)
    • ►  Oct (6)
    • ►  Sep (5)
    • ►  Aug (3)
    • ►  Jul (2)
    • ►  Jun (2)
    • ►  May (2)
    • ►  Apr (7)
    • ►  Mar (5)
    • ►  Feb (5)
    • ►  Jan (4)

Feed

  • Google
  • Privacy
  • Terms