Automation now permeates almost every aspect of product development, from ideation to release. We spoke with Nikita Klimov, a Senior QA Engineer at ADP Inc., to understand how automation is reshaping testing processes, which tools are worth adopting, and whether it’s possible to automate without coding knowledge. Nikita also shared his rapid journey to the Senior role and discussed trends shaping the future of testing automation.
Tell us about your career in IT and the projects you’re currently working on.
The most significant milestones in my professional growth were my roles at Restaurant Brands International (RBI) and ADP Inc. At RBI, we worked on a global point-of-sale system for Burger King, occasionally branching into projects for Popeyes and Tim Hortons. Our team was distributed, with the office based in Miami but most team members were located across Brazil, Mexico, Canada, and India.
One of the key challenges was coordinating across multiple time zones. For instance, when our day began, the team in India was wrapping up their work and handing over tasks that had been completed overnight. I focused on streamlining these processes to minimize disruptions for management.
Additionally, every second Friday, we conducted learning sessions to share problem-solving insights with remote teammates, helping them enhance their skills.
During this time, we implemented numerous features for the point-of-sale systems at Burger King and Popeyes. These included kiosk configuration, software for digital menu boards, and biometric fingerprint scanners for employee access.
Currently, I serve as a Senior QA Engineer at ADP Inc., a leading provider of HR solutions. My team and I work within the GPT-South (Global Product & Technology) unit, primarily focusing on benefits systems, such as insurance plans for our clients’ employees.
One notable cross-team project I’ve contributed to is the Year Round (YR) initiative. The YR initiative supports the enrollment process outside of the open enrollment window, which is beneficial for new hires or during new client implementation and helps to eliminate some complex manual processes and avoid potential undesirable retroactive corrections.
You quickly advanced to a Senior position. What advice can you offer QA professionals aiming for career growth, and what skills are essential?
Start by assessing your current competencies. I began by analyzing the skill set required for senior roles and subsequently identifying gaps in my own expertise. This led me to create a personal roadmap for self-improvement.
Certifications can be incredibly helpful—consider programs like Scrum Master, SAFe Agile, and Six Sigma Lean Thinking. Automation skills are also critical for Senior roles; I learned Python to strengthen my technical abilities. Take on diverse tasks to expand your skill set. For instance, I delved deeply into API usage and database testing.
I also recommend tackling challenging assignments and embracing new opportunities—they are the stepping stones to organic career growth.
What trends in QA and automation excite you the most? What stands out in the current landscape?
Life increasingly gravitates toward simplicity. Consider photography: once an intricate art requiring technical expertise, it’s now accessible to anyone with a smartphone.
The same is true in QA. No-code tools now allow testers to automate processes without needing programming knowledge. In my experience, only 20% of cases require custom code, and low-code solutions can cover most scenarios effectively.
Prominent examples include MABL and Tricentis Tosca. MABL integrates Playwright for testing, Appium, and Postman for API testing, among other tools. Tricentis Tosca is more widely known and even offers certifications. While these tools are paid, their cost is often lower than hiring or training a dedicated automation engineer.
How do AI and machine learning influence testing automation?
For now, their impact is modest. AI-powered testing tools exist but aren’t yet as reliable as one might hope. For instance, MABL includes an AI feature that adjusts automated tests when the code changes.
However, it often misses updates or applies incorrect algorithms. My colleagues and I frequently discuss AI trends and agree that neural networks need more time to mature before they can provide consistent and reliable support.
That said, there’s no need to worry about AI replacing testers. Projections suggest that AI will impact only about 4% of QA jobs. AI lacks critical thinking and the creativity required to identify unconventional solutions, so it won’t be able to fully replicate a tester’s role.
One useful AI tool we rely on is Copilot, which assists with code review by quickly identifying errors and suggesting fixes. However, even Copilot cannot write complete code autonomously.
Which cutting-edge tools for testing would you recommend exploring in the coming years?
I’d encourage QA professionals to explore low-code tools. Another promising framework is Playwright, which stands out for being open-source. Unlike MABL and Tosca, it’s free, making it accessible to anyone interested in learning and practicing.
Playwright supports multiple programming languages, including JavaScript, Python, Java, and C#, making it highly versatile. Developed by Microsoft, it is well-supported and has extensive documentation.
These tools will help QA professionals remain competitive in the market for years to come.
