As Sr. Director of Engagement, Rajini Padmanaban leads the engagement and relationship management for some of QA InfoTech's largest and most strategic accounts. She has more than twelve years of professional experience, primarily in the software quality assurance space. Rajini actively advocates software quality assurance through evangelistic activities including blogging on test trends, technologies and best practices, providing insights on software testing to analyst firms such as Gartner, IDC. She is also an active speaker in the Star conferences run by SQE and was recently a keynote speaker at the QAI STC. Her writings continue to be featured in TechWell, Sticky Minds and Better Software Magazine amongst others. She can be reached at [email protected].
The role of evangelist is often not very well known—or even if it is, it is not well understood in terms of its differentiation from closely associated functions, such as sales and marketing. But when understood and implemented well, it is a very powerful role. What does evangelism mean in terms of software quality?
Testers have always been advocates for the end-user. But there are now more opportunities to be that advocate, including emotional intelligence-based testing and role-based testing, which form a critical part of empathetic testing. Building empathy into our software engineering process ends up benefiting everyone.
AI is a double-edged sword. When it's being used in situations involving sensitive personal data, such as health care, banking and finance, and real estate, security is of the utmost importance—and so are ethical implications. It’s up to testers to mitigate risks and make sure AI is used responsibly.
Just as debt can be good and bad in everyday life (such as a home mortgage), debt in the engineering world can also be good and bad. This applies to quality engineering as well—with good and bad test debt. As testers, how do we create a balance and stay at the right test-debt quotient?
Artificial intelligence (AI) is an ongoing trend today. However, the picture is not all rosy—even for the insiders who are heavily invested in this space. They are being cautiously optimistic about the potential it holds and the potential adverse impact if the threshold is exceeded.
In the current dynamics of product development and confirming quality in the agile world, the definition (both narrow and broad), significance, and scope of integration testing have increased manifold. Rajini Padmanaban highlights the changing facets of integration testing that teams need to make note of.
It is a common belief that testers should think like end-users by going beyond the defined requirements, seeing if the application under test addresses end-user expectations, and evaluating how it fares against competition. But with security testing, testers have to think not only like end-users, but also like hackers.