When reading a blog, generally you want to know a couple of things about the one writing it, don’t you? Well, as much as I dislike talking about myself, I feel you have the right to know who I am and what qualifies me for this blog.  My name is Gabriela and I am a QA Engineer since 2014. My experience in the testing field includes Web Pages and Data Warehouse reports, and various technologies like Linux, SQL, PL/SQL, SAP Business Objects,  Informatica, maybe some other that I won’t mention now. My experience is centered on manual testing, but I would like to improve my automation skills too, somewhere in the future. 

About the software testing process I can tell you that QA is not only about browsing some web pages, but also about investigating, understanding, communicating and tracking. I always feel like a small detective every time I try to find the root cause of a problem. Cause that’s what QA is. Finding the problem and trying to find the source. 

I have experienced various testing environments, like Telecom and eCommerce web platforms, Data Warehouse reports and even Windows servers (working as a technical support is, in my oppinion at least, the precursor of QA). 

I would also remind about game testing. Everyone thinks that games testing is just playing games at work. Until a certain point it is, but is also about finding vulnerabilities, about performing load tests, interruption tests, saving tests and even security tests.  Because yes, security is important. You don’t want all your game items to be cracked. I still remember that “The Big Bang Theory” episode when Sheldon Cooper called the police because someone cracked his World of Warcraft accound and stoled him enchanted weapons, vicious gladiator armour, wand of untainted power and all his gold. You honestly don’t want that in a game, do you?

Lessons I have learned in my career as a tester?

  1. Never underestimate a problem, cause it might kick back pretty hard
  2. Never investigate an issue superficially. Always try to get to the bottom of the problem and see the bigger picture
  3. Never ever say that you understood the problem unless you are positive that you did. Otherwise people won’t always be willing to explain the second time what you said you understood. 
  4. Try to see beyond the surface. Don’t resume only to finding the problem, but try to get to the bottom of the cause. It will greatly improve your skills and your managers will be more prone to trust you and take you into account for an eventual promotion. If you don’t, others will and you will lose this train 

Testing isn’t hard, but it isn’t easy also. Patience is the key to success in this domain. You won’t be a QA guru all of the sudden. And to quote something that my school teacher told me: “If you made it, go on. If you didn’t, go on”.

I have dedicated this blog to a dear friend of mine who had the ambition to try the QA world and learn something new. He inspired me and gave me the courage to do something I wanted to do long time ago. Thank you! 🙂

That being said, I invite you all to find answers to your questions or feel free to ask, whether you do it in a comment or in an email.

%d bloggers like this: