Rajini Padmanaban
Member for
13 years 7 monthsAs Vice President Testing Engagements, Rajini Padmanaban leads the engagement and relationship management for some of QA InfoTech's largest and most strategic accounts. She has more than seventeen 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 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].
As Vice President Testing Engagements, Rajini Padmanaban leads the engagement and relationship management for some of QA InfoTech's largest and most strategic accounts. She has more than seventeen 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 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].
All Articles by Rajini Padmanaban
All Stories by Rajini Padmanaban
|
Accessibility Testing 101: Getting Started and Catching UpAs with any other quality attribute, it is ideal for accessibility to be incorporated in the early stages of design and engineering. But organizations that didn’t initially take accessibility into account can still address it now—it’s better late than never. Here are the main attributes you should consider from the design, development, and testing angles, whether you're building accessibility in from the beginning or adding it now. |
|
Testing in Production: A Double-Edged Sword Testing in production gives more realistic opportunities to test, increases application transparency between the core product team and users, and supports the idea of continuous development through continuous testing. It's a good technique to embrace in your testing process—but it should not be entered into unprepared. Learn the advantages and pitfalls here. |
|
Why You Shouldn’t Do What You Love Saying you shouldn’t do what you love sounds crazy, doesn’t it? After all, isn’t the best-case scenario to turn your passion into a career? Not necessarily. There is an important difference between doing what you love and loving what you do. Rajini Padmanaban explains why you should keep your hobby separate from your career. |
|
Accepting the Tester into the DevOps Fold Today’s tester has moved upstream, along with the test processes, where he is involved right from the product design stages. This can create great opportunities for the team to bond, but if not handled well, it can become a breeding ground for strained relations. Adopting DevOps means promoting collaboration. |
|
Want More Innovative Testing? Put on a Different Thinking CapTesters commonly face challenges around one-dimensional thinking, limited ideas, and communication issues. Sometimes, all you need to break out of a comfort zone or come up with better approaches is a fresh perspective. Putting on a different “thinking cap” can help you innovate solutions in a whole new way. |
|
New Ideas for Effective Localization Testing Practices in an Agile Cycle While practices in localization testing have been suggested for every environment, it is becoming even more important to have such practices for an agile localization test effort. This is a list of ideas to help ensure on-time, on-cost product releases, synchronized efforts for releases in all languages, and good collaboration among team members. |
|
The New Gives and Takes in a Software Tester’s Role As champions of product quality, software testers have an increasing responsibility in empowering the team to understand and own quality themselves. Testers need to optimize their efforts by giving away some tasks to others on the product team and taking on newer tasks to align with a more focused approach. Read on to realize what you should give up or take on. |
| The Dotted Line in Role Delineation between a Developer and a Tester While collaboration has measurable benefits—faster issue resolution, better understanding of the product and its features,load sharing of team responsibilities (in systems such as kanban)—it also introduces ambiguity around the team members' roles and responsibilities. Of specific interest to us here is the boundary around a tester’s role and its delineation from a developer's role. |