Anybody form the API team has to say anything about the below mentioned points made by me? Any comment will be appreciated.
Haha, nice one avidCoder , I like the "software detective" title, it's indeed a better description.
Why do you enjoy your work?
For me testing always was a link between business and IT. I started in the banking industry as an employee of a bank, but after a year I wanted to leave because I became too frustrated with the shortcomings of the applications we had to work with.
As a tester, you should know the business logic even better than the business people, as you as tester need to come up with the edge cases that makes them scratch their head. Also, as a tester you cannot just be apathic towards IT, as you need to dig deep, understand the way something is build in order to be able to break it. It's always a mixed feeling when detecting a bug. On the one hand you know that release targets might not be met due to this, on the other hand those bugs proof your needed. It's always important to be tactful as those same bugs might proof (or feel like proof) that the developers did a lousy job. But in the end, everyone in a team needs to understand those dynamics and that all those efforts are bundled to deliver a (nice) piece of software or application! A go-live is always a proud moment.
What was the most interesting/unusual bug you’ve found?
Specific for API testing it was interesting to see that an authentication failed whenever there was a certain load. During load customers could see the data of other customers, which is ofcourse something you want to avoid at any cost. Outside API testing: One customer could logon to an application to see his contact details. For 1 customer (test data was a scrambled copy of production) the number of contact details was that big that he page crashed when he visited it... But not only did it crash for him, but any other customers who wanted to load that page afterwards could no longer reach his/her contact details anymore. So one person was able to make somthing crash for all other customers!
What do you laugh about at work?
I guess what often happens is: As a team you look for "outside" enemies to bound and feel united. Might be another vendor, or other project team....you may laugh at their bad code implementations for instance. Or it may even be "those people from business", that do not have a clue how a computer works. All in good fun ofcourse.
