Do you delight in finding fault?
Well, Yes. We do think analytically on how to make an application fail. Exhausting all other scenarios aside from scenarios that are on only a good path is vital.
Sometimes we feel nervous whenever something seems right, perhaps it might be because one is overthinking. We cannot deny the fact that we usually double check and reevaluate things, right?
Tony Robbins says “Every problem is a gift. Without them we wouldn’t grow”. Faults are inevitable whether we like it or not. The more we realize it then the more we are able to find joy in dealing with them.
What do developers think of us?
They can think of us as a blessing or a curse at the same time. Blessings in a sense that we help them double check the software in order to meet the standard of the client. However, sometimes they consider us as a curse because we are responsible of breaking it. (which makes us happy).
Nevertheless, we all want the best output before they get to production that is why developers and QAs work hand in hand in shaping the future of the software.
Is SQA an easy job?
Once and for all there is no easy job. Being SQA requires a lot of soft and hard skills. You must be able to ensure that products delivered meets the standards. And as SQA, the approval of the product depends on you. You should think outside the box, exhaust other ways to find flaws on the product. Analyzation is important for you to better understand what software you are dealing. And if you have a good technical skills you can easily relate to developers. Also, communication skills, is one thing that will help SQA express there self in conveying his point of the issue or defects. Efficiency in work is highly a plus factor because sometimes critical task that must be performed efficiently to produce best output. And last is the attitude towards work, you can have all this skills but if you are poor in character then it would be useless.