View of the bug(test version 1.0)

Finding a bug is success not for everybody around me. Coworkers from different departments have different view to the bug of the system.

When I found issue, bug or defect - it's a good day for me. And more I found, better I feel that day.

And there are guys from fulfillment - for them bugs are problem why they can't send hardware for client, or something not that critical but still an issue. Other times just problem we discuss about, sometimes we find solution, or I just register their problems as defects or enhancements. But overall it is not such a big deal and can be managed easily.

But horror begins then issue is found by support, or to be more exact - by customer. Then ten same issues are registered, clients are angry, support are angry and exhausted. And I understand them, to deal with issues were everything is on your back and often fix doesn't come in week or two or even month. Like an issue exist at the moment for certain clients - in iPad footer appears red line with warning and it can be closed or turned off and under it hides buttons and it is really annoying while working with it. If app is killed it helps for several hours but after that red line appears again. And complains for this bug are coming and coming.

And with stuff like this and sometimes even worst, guys need to deal every day, and they aren't happy as I am then bug is founded.

After I read what crap I have written, I understood that this post need to be rewritten, because i just scratched surface of just couple of types of coworkers and how I see - how they see bugs. But I will not rewrite this post, i will expand it in couple posts with more details. Or even create series about "How other people see bugs", of course from my perspective. 

Your friendly neighborhood Tester

Everything need to be registered

Doing my everyday work I often came to the days when I can't find any bug or defect. Sometimes it is frustrating to do job without any success. But other days, mostly then starting new project, with joy I am registering new issues. And often i doesn't matter if it is actual bug or my misunderstood of what I am dealing with. But from my point of view is better to register everything and sleep peacefully at nights.

Yea- sometimes this bugs registration brings some confusion for developer or product manager, but it is easier to close it, then pay for man-hours for managing it. But in this method I see some pluses - first of all - a lot of bugs registered on your name. Deeper understanding of product - even closed bugs will have info why it is not actual bug or at least how to prevent it. To save your self from angry management, support or any body else how maybe affected of missed thing which was known about.
I'm trying to do job as good as I can. Register all the issues, defects and other stuff which looks important to me. But I am just a ordinary person - who makes mistakes, and a lot of them. 

I miss bugs very often, and sometimes very obvious ones. Very good example is from company I worked before. Situation seems very simple - on opening new account, fee is payed from money which are adding to account. Situation goes out of hand then accounts is opened in foreign currency. Because fee is in local currency, amount of fee need to be calculated with exchange rates from database. To check if amount is greater then fee, data is send to database, calculations done there and final amount and calculated fee is returned. From final amount fee is subtract and account with double fee taken is opened. I hope it was easily to fallow and understand how much shitload came to me - then every teller needed to write explanations for every account they open in foreign currency.

Every case should be registered, but not today. Today was boring day, and nothing new or interested happened. I hoping everybody has days like it. After they pass days with a lot of bugs will come, and day will be not boring.

Yours friendly neighborhood Tester.

Beginning

Who am I?
I'm tester, quality assurance engineer, QA analyst or anything I need to be at the moment - who I need to be at the moment.
To my self I'm person who is still a child playing and breaking all the toys all the time - and "I loving it". Just my toys are expensive and not always possible to touch. Sometimes it is printer, sometimes part of software, or just a string in description. Anything can be tested, and most of the times need to be tested. And I am doing it all the time.
I think I became tester long ago I came to testing area. While I was still kid and I don't remember I went to school jet or not, but I remember very clearly how I busted my toys and often checking that is in side and how they work. Even now I remember how I destroyed quite expensive toy train just to look how electronic motor is spinning its wheels, it was nice toy and still regretting I did that, but it is a part of me. I broken a lot of things in my life, but that helped me to understand how they work and sometimes how to fix them. But I am here writing not about fixing but about braking, destroying or simply testing. Fixing is a part of my job too, and maybe later i will write or include in posts about it.
I begin this journey couple years ago. Most of the stories still in my head, other almost fade away. But other are just coming to me. And i hope to share them all.

Yours friendly neighborhood Tester.