Reflections of a QA

Sofía Acher, IT Copywriter
Matías Angio, Quality Assurance Analyst
https://www.linkedin.com/in/sofia-acher/
https://www.linkedin.com/in/matiangio/

The following text is a summary of the original one. To read the full article, visit our blog at www.onetree.com

Have you ever reflected about your role in your company? How could you do better? Why does your position have a certain work dynamic? In this article we aim to reflect about the role of the Quality Assurance Analyst, question certain aspects and make a self-criticism about it.

Matías Angio’s experience, and what makes him reflect and write about it, is based on team work in which physical space is shared, working for a project which is not in production yet. Work methodologies used are based on Agile Methodology, some of them use continuous development practice and others are based on traditional release processes. Beyond differences, the central idea applies to everything.

The first and most important aspect QAs should keep in mind is attitude. Having a positive attitude towards the team and the client is imperative. We are what we emit, and how our mood impacts others is more than verified. Moreover we ought to accept criticism and improvement recommendations we receive, directly or indirectly, from our coworkers or superiors. Only when we accept them, without value judgments or taking it personal, will we be able to talk with others openly and suggest improvements in an honest way, so as to avoid offending anyone and being misinterpreted as arrogance or meddling in someone else’s work.

We need to be proactive. Our job should not start when we receive a task to test. There are many things we can do before and during the time we are testing: create test cases, analyze requirements, test other functionalities, think and look for improvements on workflows of products in development, raise and impose doubts on the team such as “What if…?”, among others.

The more unnoticed QAs go, the better. The fact that we report bugs again and again does not make us better testers. If we detect that something is going to fail or could look bad from early stages, communicating it beforehand is the optimum path; instead of waiting for it to be developed to find and point out the mistake. Prevention is better than cure.

The text above is a summary of the original one. To read the full article, visit our blog at www.onetree.com

We help clients grow their businesses by making creativity, flexibility, and talent converge into software development and UI/UX design. We are passionate and committed to take on challenges that can drive your business forward.
We combine our experience in Ecommerce, mobile, and web across various industries such as retail, wholesale, healthcare, government, and entertainment. This way, we work closely with you as a team in order to collaborate towards successful implementations. See more at www.onetree.com