Testing Blog

The Plague of Boredom

Tuesday, July 21, 2009
Share on Twitter Share on Facebook
Google
Labels: James Whittaker

5 comments :

  1. Flash SheridanJuly 21, 2009 at 1:27:00 PM PDT

    I mostly agree, except for the title: Boredom isn’t a plague, it’s nature’s way of telling you that you’re not using your head. Perhaps I’ve just been lucky in having enough test autonomy to be able to dodge this plague, but I think a good methodology which avoids some of the other plagues (e.g., the false sense of thoroughness and premature automation) will also avoid this one. As you’ve noted elsewhere, you’ve got to avoid automated testing as a complete substitute for (rather than supplement to) manual testing. But you need to avoid the other extreme as well, and boredom is a clue when you’re not.
    I confess that my test approach is often more a craft than a science: Get to know the territory, keep an eye out for bugs that you notice in normal use, and an ear out for complaints from other users. Then figure out a process which would have found those bugs, generalize it, and automate it once it gets boring.

    ReplyDelete
    Replies
      Reply
  2. prashantJuly 21, 2009 at 9:50:00 PM PDT

    I couldn't agree more.

    It is very frustrating to see bright guys getting off to a great start in testing and then, after a year or two, getting completely disillusioned about it. I personally know of many test engineers who sought escape in either development or automation.

    I recently interviewed more than a dozen candidates for a senior QA position. I was very disappointed to see that many of them took pride in how they learnt some automation tool on their own, or how they solved some very specific automation problem. Very few of them seemed to have given serious thought to the tests they were automating - about how one would design them so as to minimize the number of important bugs that reach the end user. I DO understand the importance of automation, but I think it is a tool to achieve the goal and not the goal itself.

    Yes, the strategic aspects of testing ARE very difficult, but I don't see why we, the QA community, should give up on it.

    ReplyDelete
    Replies
      Reply
  3. PetersenJuly 22, 2009 at 2:03:00 AM PDT

    I have been a Developer since years and then moved to Testing/QA. Just because I love it. No wonder you get bored, if your Job as Tester remains there where he/she started, clicking on GUIs, filling up Reports etc for weeks or even months months.

    I just dont understand why Prashant is so frustrated!! When Charles Babbage invented the mechanical Computer he just wanted to bring down the errors in calculating and save people from the same boring job of counting using Pen, Paper and logarithmic tables.

    So, if you come across the same tests almost every day, then you should automate it. The benefits are:
    1) Lesser Manual errors caused
    2) Requires lesser Testing/Release time
    3) The tests are repeatable, can be even used as Regression Tests later
    4) The Computer now does the "boring job", the Tester can concentrate on other Assignments or dig deeper into other complex Problems.

    I first start testing manually. Then I use my skills to automate every possible Tests with suitable tools, skripts or any Programming language. Periodically I inspect my Tests and Results/Reports and tune them. When a new Problem is found, I include that case in my Automated Tests. In this way the Quality of the Software we as a Team deliver improves every day. And everything starts to become "green"!! And it really motivates me to do more.

    After all, Testing is not just finding loads of bugs as fast as you can and scapegoat the developers for all that "bad software". It is all about improving the quality of the software system as a Team.

    Last but not least, it is the Job of the Test Dept. Manager to motivate the "bright guys" and show them that he/she can really learn more about all the different facets of QA and the processes every day.

    You did'nt opt to work in IT to do same routine work every day!! Its the same case with Testers also.

    ReplyDelete
    Replies
      Reply
  4. Amar AmteJuly 23, 2009 at 6:02:00 PM PDT

    Any job as a matter of fact will lead you to same feeling if you are following same process every day, no wonder there is a term called "rut"

    If QA Engineers, QA with set process and they are tend to get bore, no question about it. To avoid this I give my engineers enough lead to do exploratory testing and do not stress on writing test plan in initial phase of any tests, I know I will be contradicting with many people, but that's fact, if you want engineers to break it and say," let me see what happens" then you are half way there as well as you are keeping testers interest in the game.

    Now to avoid rut, definitely we have to avoid repeated procedures by making use of flexible and light weight automation.

    Keep giving team members ownership and freedom to work on their component, coz with freedom comes responsibility, which keeps no room for boredom.

    ReplyDelete
    Replies
      Reply
  5. Tom ScheichensteinJuly 24, 2009 at 4:35:00 AM PDT

    Testing is not (only!) about finding bugs or improving quality - where maybe the thrill of hunting gets lost over time - it’s about measuring quality. Think about those QA people who check aircrafts, cars or buildings. They won’t directly improve the quality of their project, they will inform the project what’s the actual status of the application under test. That’s what they are there for, to bring (all) positive or negative aspects to light, so that the project can stir into the right directions, based on their reports and results.
    So the defect as such is just the instrument to harden your judge, and it’s the team's job to bring the defects to light, but never forget to focus on the big picture which is “testing” with all aspects.
    On the other hand it can’t be that boring nowadays, because with our tight resources, especially within test, there is not much room for a lot of redundancies or maybe a high demand in changing test strategy to fulfil new requirements to softwaretest.

    Further, boredom is in my opinion a subject which hits every unit during the software development lifecycle, especially the developers. Think of recurring code fixing, always the same class which won't work after each release - bad QA guys throw the release always back to me.. :).
    Or simple maintenance bug fixing. It could be very frustrating to jump back to the "old" project over and over again to do fixing - and stop your creative process in the new one... or some would say… boring…
    When I talk to "creative" developers, they always bring the documentation topic, which they find very boring... (being highly creative in their coding one the one hand and comment or write it down on the other hand - some kind of stopping their flow – always writing the same preformatted text, the same diagrams and graphics..).

    So I think boredom hits every person some times (also don’t forget the subjectiveness within this topic), and it should be a chance (as said in the comments before) to start thinking into another direction to prevent it from frustrating you and as a consequence hopefully improve your doing on a daily basis - cause no one likes redundancy.

    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)
    • ►  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)
      • How to think about OO
      • Call for Attendance: Google Test Automation Confer...
      • The Plague of Blindness
      • Update! GTAC Keynote Speakers: Niklaus Wirth and A...
      • The Plague of Homelessness
      • Blog Stats
      • The Plague of Boredom
      • Blog Editor: Moderating Comments
      • The Advantages of Unit Testing Early
      • Software Testing Categorization
      • The Plague of Amnesia
      • Update! Google Test Automation Conference: Website...
      • Old habits die hard
      • Why are we embarrassed to admit that we don't know...
      • Separation anxiety?
    • ►  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