Skip to main content

The tester's syndrome


After being a software tester for seven years, I've developed a condition I call the Tester's syndrome. I'm not sure what leads to this, and how specific it is to testers, but I am sure I didn't have it before I became one.

What happens when you suffer from Tester's syndrome is, that you are continuously finding and mentally reporting bugs on the stuff that is happening around you. Yesterday I reported a few when using the elevator mainly regarding the bad usability of the GUI (my colleague also apparently suffers from this condition as he spotted and vocally reported a security issue in the elevator access control system). In toilets I often have to report a few bugs, regarding bad design leading users to be exposed to germs after washing their hands (I'm also a germaphobic btw). In waiting lines I see performance issues. At home... better not to say anything in case my wife is reading. But you get the point.

This may sound like a terrible disease to have, but there are some positive spins to it. The bug reports ease off the irritation these things may cause to me, because as a tester I understand that there are many reasons why bugs happen, and that the reasons are not to intentionally make my life harder. And as a tester I'm also happy to find problems (look to your heart, you know it's true).

So fellow disordered testers, it's ok to log all these bugs, as it is just a condition caused by the hours put into the craft. But be careful to remember that all bugs noticed are not worth telling forward. As we anyway are professional testers, not professional complainers.

And that should be a huge difference.
Labels:

Comments

  1. UnknownSeptember 1, 2015 at 9:56 AM

    Elevators for home use ar simple to put in and succinctly designed for area potency. Residential elevators are incorporated with easy controls and advanced safety options such as:

    • Non-skid platform
    • Electro-mechanical door lock
    • Slack chain safety device
    • Telephone system
    • Emergency stop button
    • Emergency alarm and light
    • Battery lowering device: for use in case of power failure
    • Pressure relief valve to avoid platform overload
    • Lockable control panel
    • Open door sensor
    • Key lock to prevent unauthorized access
    • Continuous pressure buttons to operate the unit
    • Fully automatic operating controls
    • Over speed governors
    • Final and ultimate limit switches
    • Handrails
    • Interlocks for hoistway


    elevator access control

    ReplyDelete
  2. UnknownSeptember 13, 2015 at 4:07 PM

    Elevator Access Control systems allow people access to certain floors within a scheduled time frame. The system can control one or more elevator controllers in a
    system. It provides a range of system authority for users.
    DT4 – Elevator Access Control – Motherboard Controller – Controls and monitor up to eight (8) floors, expandable to forty (40) floors. Net-workable to support up to twenty (20) elevators.

    To know more details lease vsit us-

    elevator access control

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers doing test automation - is that the most important thing for you to do right now?

I've been thinking quite a lot about tester's moving to do test automation.  Lately beause of these three things: 1.  European testing conference , a great testing conference I attended couple of weeks ago. It is very cool due to many things; the way the speakers get compensated, the focus on the conferring side of conferences making it very easy for people to discuss stuff, the way the talks are chosen, and because there are also a lot of developers joining. So anyway when I was talking with several of the attendees, it was a bit strange how it was easier for me to talk about the product development as a whole with the developers, where as with the testers it more naturally moved into talk of automation and tools. Also on the open space, I think the majority of the topics pitched was automation or tool related. And quite little on the process or on the customer facing side of product development.  2. In my company there are a lot of different products and...
3 comments
Read more

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.
3 comments
Read more

Six reasons why testers should do code reviews

I have had quite a lot of discussions about code reviews. Quite many also with testers, by which I have understood that many do not do those. I will not start arguing here on whether code reviews are good/important or not. But I will list a few things why I think testers would benefit of doing them. 1. Code is the only documentation that is up to date . If you really want to know how something really functions, you want to be able to see and read the code. 2. Knowing more about the thing done enables you to do better testing . You can spot things that you should definitely test, and things that you probably don't need to test that much. Like extra things added by coder, usage&modifications of existing functions, data types, etc. And to arguments thinking that one loses their "independence" as a tester by knowing too much, I would worry a lot less about that than about testing stuff that you have no idea on how it has been built. 3. Improve logging . I obse...
2 comments
Read more