{"id":18626,"date":"2021-10-19T09:29:07","date_gmt":"2021-10-19T09:29:07","guid":{"rendered":"https:\/\/arobs.com\/?p=18626"},"modified":"2024-02-19T10:23:20","modified_gmt":"2024-02-19T10:23:20","slug":"being-a-qa-engineer-and-dealing-with-difficult-clients","status":"publish","type":"post","link":"https:\/\/arobs.com\/en\/blog\/being-a-qa-engineer-and-dealing-with-difficult-clients\/","title":{"rendered":"Being a QA Engineer and dealing with difficult clients"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
AROBS Transilvania Software development<\/span><\/a><\/span><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Being a QA Engineer and dealing with difficult clients<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Custom\u00a0<\/em>software development<\/em><\/a> is about creating a product that responds to the client\u2019s needs. But from concept to final deployment, there\u2019s a process in which a QA Engineer is essential.\u00a0<\/em><\/p>

Especially when we\u2019re talking about <\/em>life sciences<\/em><\/a>\u00a0and e-pharma, where the data collected through the software must be accurate and compliant with the highest standards.<\/em><\/p>

That\u2019s one of the reasons a QA Engineer has an important responsibility in making sure the software product meets requirements. Nevertheless, working with big pharma companies and clients can be a pressure, both in executing and maintaining a good relationship with them.<\/em><\/p>

Alexandru S. <\/strong>is one of our best QA Engineers. <\/strong>He’s been part of AROBS for eight years, and currently working in the Life Sciences division team. <\/strong>Thus, he has a lot of QA wisdom to share. Read his article below.<\/em><\/p>

Keywords<\/strong>: testing, QA Engineering, customer service, teamwork, automation testing.<\/em><\/p>

When I started working as a tester back in 2012, I wasn\u2019t quite aware of the depth of my job and the impact it has on the quality of the product. There\u2019s a big difference between a tester and a QA Engineer. As I grew into the role of a QA Engineer, it became clear that there were more complexities involved than just clicking buttons, including close collaboration between the client, development, testing, production, and support teams. An entire cycle that has to work.<\/p>

Every software tester\u2019s goal should be to deliver great results. For that to happen, we must think and use the product like an end-user while at the same time understanding the processes that take place in the background. Doing this is not an easy job but, what if you also have to deal with a difficult client?<\/p>

Let\u2019s first focus on three things we, as software testers, can do to deliver a great client experience.<\/p>

\u00a0<\/h2>

A QA Engineer should understand the users<\/strong><\/h2>

Curiosity is one of the tester\u2019s greatest assets. Before starting to test, there are some basic questions any tester has to ask himself, like \u201cWho is using the product?\u201d, \u201cWhy do they use it?\u201d or \u201cWhen or where do they use it?\u201d. These are fundamental questions to help us understand the context and to create a testing strategy.<\/p>

The easiest way to get answers is to ask your client to use the product. It is a great way to understand your client and his requirements, giving you the opportunity to determine priorities, understand pain points, set up your tests and get better results.<\/p>

\u00a0<\/h3>

Teamwork<\/strong><\/h3>

As a QA Engineer, you have to be cooperative. Speak with your team members, understand their ambitions, goals, what they like or don\u2019t like, professional and personal. The more you get to know your team members, the more trust you create. Once you know your team, you can communicate and collaborate better, even conflicts will be solved with ease. Working together as a team is better than going at it alone!<\/p>

\u00a0<\/h3>

Don\u2019t get trapped in a loop<\/strong><\/h3>

There is no limit in creating test scripts or finding ways to break them. We can find an infinite number of ways to use the product and just as many bugs to uncover. When you feel stuck in a loop testing the same functionalities, try automation. And break out of the loop.<\/p>

\"\"\u00a0Remember, quality and speed are two indispensable ingredients for success in agile environments.<\/span><\/p>

Working and interacting with people is often harder than anything. Other than that, business relationships tend to be more consuming than personal ones. Why? Because there is a lot at stake. Our professional image, the fact that we represent the company we work for, and we also have to care about our client and his needs. And it\u2019s not always fun and games.<\/p>

Sometimes we run into difficult clients and, regardless of how we do our work, there will always be good days and bad days.<\/p>

\u00a0<\/h3>

How can we manage the \u201cbad days\u201d?<\/strong><\/h3>