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.

Comments

  1. 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. 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

I don't report bugs

I don't report bugs . Bug is such a loaded word that people understand very differently, that instead of using it and explaining what I mean by it I rather just use other words. Like observations, thoughts, surprises, ideas, alternatives, or something similar. (And no I don't use fault, defect, or error either). Bug has also quite a negative connotation. "Reporting a bug" is kind of like telling someone that they've been served. And as we are actually giving away the gift of information, why wrap it in such a nasty package? And maybe more importantly it is very likely that whatever you might have to say is wrong. If not plain wrong, then at least incomplete. So I like to approach the kind of situations with the assumption that I am probably wrong. Cutting off anything that might sound arrogant makes stuff quite a lot easier. Especially after you realise later on that you have been wrong. I leave plenty of observations unreported . I don't want to waste

Testers of past be the IT stars of the future?

Been noticing two a bit conflicting themes lately. 1. Testers getting (or pushed) to be more technical and write test automation code 2. Articles listing future IT core skills as widely non-technical So whereas many testers are moving to work more on test automation, the vital skills of the future may be such as: - Creativity -  Analytical (critical) thinking  -  Activ e  learning  with a growth mindset   -  Judgment and decision making -  Interpersonal communication skills - Complex Problem Solving Which sounds almost like a list of vital skills needed for an exploratory tester.  So we should perhaps remind the ones starting a testing career or moving away from it, that also these skills are something that can be quite valuable in the future as well. Maybe even the most valuable.

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.