Mandisa Ndlovu from A-impact recently had the pleasure of interviewing Omphile Matheolane, Technology Lead at Nedbank.
Mandisa: What are some of the biggest challenges you’ve faced as a tester in a
DevTestOps environment?
Omphile: In my experience as a technical lead and software developer, one of the
most persistent challenges in a DevTestOps environment has been balancing delivery speed with quality. The pressure to deploy rapidly, especially in agile and DevOps-driven teams, often creates tension between delivering features and ensuring they are production-ready.
Testing can sometimes be perceived as a bottleneck, yet skipping or rushing it leads to downstream failures that cost exponentially more to fix.
Another challenge I’ve encountered is maintaining consistency in test environments. Modern applications are often distributed, cloud-based, and reliant on a web of microservices. If the test environment isn’t an exact replica of production, bugs can slip through unnoticed. Managing infrastructure as code and containerized environments has been crucial in addressing this gap.
But perhaps the biggest challenge is cultural. Encouraging developers to embrace testing as an integral part of software development, not just a final checkpoint, requires a mindset shift. A true DevTestOps approach means integrating quality practices into the development lifecycle from the very first line of code.
Mandisa: How do you handle the pressure to deliver high-quality testing in a
fast-paced, agile environment?
Omphile: In fast-paced environments, the key is to work smarter, not harder. I’ve
found that automation is the single most effective way to balance speed with quality. Every code commit should trigger a robust suite of automated tests, including unit tests, integration checks, security scans, and performance evaluations, ensuring rapid feedback loops and early detection of defects.
Bill Gates once said, “I choose a lazy person to do a hard job. Because a lazy person will find an easy way to do it.” While I wouldn’t call it laziness, the most effective teams I’ve worked with are those that seek efficient solutions, leveraging AI-driven test execution,
optimizing test cases for maximum coverage, and eliminating redundant processes.
Handling pressure comes down to staying adaptable, agile environments are unpredictable, and the ability to pivot, reassess, and optimize testing strategies in real-time is crucial. Teams that embrace a flexible, problem-solving mindset, rather than rigidly following
predefined testing plans, are the ones that thrive under pressure. The goal isn’t just to test effectively but to continuously refine how testing is done, ensuring that as development speeds up, quality keeps pace without becoming a roadblock.
Mandisa: What strategies do you use to stay up-to-date with the latest
technologies and testing techniques?
Omphile: Technology evolves rapidly, and staying up-to-date requires one to be
intentional and proactive in continuous learning. In my experience as a technical lead and software developer, keeping pace with emerging trends isn’t just about consuming information, it’s about actively engaging with the tech community. I do this by attending industry conferences, participating in technical forums, and following Thought Leaders on
LinkedIn who are driving innovation in software quality, scalability, and security. This not only keeps me informed but also exposes me to real-world challenges and innovative solutions being implemented across the industry.
However, reading and listening can only take one so far, to truly understand something comes from hands-on experience. Whenever I come across new software quality methodologies or tools, I explore it firsthand. Whether it’s AI-driven test automation, contract testing for microservices, or chaos engineering for resilience testing, I’ve found
that applying new concepts in real-world scenarios is the most effective way to understand them. Experimentation, proof-of-concepts, and pilot implementations help bridge the gap between theoretical knowledge and practical application.
One of the most unexpected yet valuable ways I’ve stayed ahead is through mentoring and coaching. Explaining concepts forces me to refine my understanding, and often, discussions with peers and mentees uncover fresh perspectives that I might not have considered otherwise.Knowledge-sharing not only strengthens my expertise but also encourages
an environment where continuous learning becomes a collective effort.
Mandisa: How do you facilitate collaboration and communication between
testers, developers, and other stakeholders in the DevTestOps process?
Omphile: In my experience, collaboration in a DevTestOps environment is more
about culture than process. The most efficient teams I’ve worked with have embraced transparency and shared ownership of quality. When developers, testers, and operations teams operate in silos, misunderstandings arise, and defects slip through the cracks. Breaking down these barriers is essential.
One technique I’ve found effective is conducting “Three Amigos” sessions, which bring together developers, testers, and product owners before development even begins to align on requirements, define acceptance criteria, and preempt potential issues. This proactive
approach ensures that testing isn’t an afterthought but a fundamental part of the development cycle.
I also advocate for real-time visibility into quality metrics.
Dashboards that track test coverage, defect trends, and release readiness provide stakeholders with a clear picture of the software’s health. Automated notifications for failing tests help teams respond immediately, keeping everyone aligned and engaged in the quality assurance process.
Mandisa: What techniques or tools do you use to ensure that testing is
integrated into the overall development process?
Omphile: Over the years, I’ve seen testing transform from a standalone phase to
an embedded practice within the software development lifecycle. A robust
CI/CD pipeline is at the heart of this transformation. When every commit
automatically triggers a series of tests, ranging from unit and API
tests to security scans and performance benchmarks, quality becomes an
integral part of the development cycle rather than a gatekeeping step.
For distributed systems reliant on microservices, I’ve found contract
testing with tools like Spring Cloud Contract to be invaluable. This ensures that microservices interact correctly without requiring large-scale integration tests, making the process both faster and more reliable.
Additionally, observability tools like AppDynamics and Dynatrace provide insights beyond pass/fail test results. They allow teams to monitor system behavior in real time, identifying anomalies before they escalate into major issues. In combination with feature flags and canary releases, this creates a safety net where changes can be deployed
gradually, tested in production-like conditions, and rolled back if needed, without affecting the entire user base.
Mandisa: Can you share an example of a successful collaboration between
testers and developers that resulted in improved quality or efficiency?
Omphile: In my past experience, one of the most impactful changes in improving
quality and efficiency came from adopting DevTestOps and shifting testing left in the development lifecycle. Traditionally, testing was a siloed, post-deployment activity, often treated as a final gate rather than an ongoing process. This reactive approach meant defects were caught too late, leading to delays, costly rework, and production issues. It also created friction between developers and testers, as developers were focused on delivering features, while testers were tasked with identifying defects; two goals that often felt misaligned.
By embracing DevTestOps, testing became a continuous and collaborative
effort, embedded into every stage of development rather than a last-minute hurdle. Testers worked alongside developers, ensuring that quality considerations were built into planning, design, and coding from the start. The shift-left mindset fostered faster feedback loops,
automated quality gates, and early defect detection, allowing teams to address issues proactively instead of reacting to failures late in the process. Rather than serving as gatekeepers, testers became quality enablers, working hand in hand with developers to prevent defects instead of merely detecting them.
This transformation not only improved software reliability and release speed but also reshaped team dynamics, fostering a culture of shared ownership over quality. With testing becoming an integral part of the development process, last-minute surprises were minimized, and quality became an inherent part of software delivery rather than a box to check at the end
