Are quality engineers still needed in modern ages?
“We don’t need quality engineers - we write automated tests ourselves.” How often have you heard this yourself?
Even though quality is a team responsibility, developers automating tests without the customer’s point of view could end up only ensuring that your code logic is correct. Exploring the customer’s perspectives raising different inputs, and discussing the business problem that we are trying to solve demonstrate that automation is not everything, and there is a lot more to look out for.
Quality is more than simply automating tests, because you can’t test quality into a product; it must be built in. To be able to do so, quality engineers being part of the team create a mental model of your customers including their perspective, their needs and their user experience.
In this talk, I will reveal common misconceptions about the QA role in development teams, showing how Quality Assurance Engineers are fundamental and why they should be an active part of the process to achieve the goals of your product.
Common misconceptions about the QA role in development teams
How QAs help to build a quality mindset inside teams
The importance of QAs to raise customer’s point of view
Clarissa Rodrigues is graduated by University of Vale dos Sinos (UNISINOS), specialist in Software Engineering by Federal University of Rio Grande do Sul (UFRGS) and master student in Applied Computing by UNISINOS. With more than 10 years of IT experience, she has been working in different roles and companies, such as a Business Analyst at SISPRO, Test Leader at ADP and most current Quality Specialist at SAP. On her journey, she has been advocated for quality inside QAs work to make sure goods and services are designed, developed, and made to meet or exceed customers’ expectations and requirements.