Need testing support? Check our Quality Assurance services.
See also
- 10 technology trends for 2025 that every CTO needs to know
- 4 key levels of software testing - An expert
- 5G and 6G - How will ultrafast networks change business applications?
The emergence and rapid popularization of agile methodologies (Agile) and DevOps culture and practices have revolutionized the way modern organizations around the world approach the process of developing, delivering and maintaining software. The emphasis on short, iterative development cycles, close, day-to-day collaboration among all team members, comprehensive automation of repetitive tasks, and continuous, seamless delivery of real business value to end users has become the new, widely accepted standard in the IT industry. In this highly dynamic, rapidly changing environment, where responsiveness and adaptability are key, some observers and practitioners have begun to ask a fundamental question: in a world dominated by Agile and DevOps, is there still a place for traditionally understood quality assurance (QA)? Are dedicated testing roles and QA processes inadvertently becoming a bottleneck, u
ecessarily slowing down rapid release cycles and stifling innovation? At ARDURA Consulting, based on our years of experience and numerous projects implemented in these methodologies, the answer to this question is unequivocally and emphatically: **the role of QA in an agile, automated world is not only not disappearing, but on the contrary - it is becoming even more crucial, strategic and influential, although it is undoubtedly undergoing a fundamental, exciting transformation **.
Evolution of QA - From Controller to Quality Architect at ARDURA Consulting
“Good testing is a challenging intellectual process. It requires skill, knowledge, and creativity.”
— James Bach, Lessons Learned in Software Testing | Source
Gone is the era when quality assurance specialists were seen mainly as an isolated team operating at the very end of the manufacturing process, acting as a kind of quality controllers on the production line. At the time, their task was primarily to catch defects and errors just before the symbolic “shipment” of the finished product to the customer. Such a reactive approach, often referred to as a “quality gate” (quality gate), where QA acts as the last filter before deployment, is completely incompatible with the spirit and fundamental principles of Agile philosophy and DevOps culture. This is because these modern approaches assume a seamless, uninterrupted workflow, elimination of competence silos and, most importantly, shared, indivisible responsibility of the entire, interdisciplinary team for the quality and success of the delivered product. In a modern, agile model, which we successfully implement and promote at ARDURA Consulting, **The QA specialist ceases to be merely a passive “bug catcher” or late-stage test enforcer. He or she becomes an active, fully integrated and highly influential member of the scrum or product team **. He works side-by-side with developers, business analysts, UX/UI designers and Product Owner on a daily basis, being actively involved in every stage of the software development lifecycle - from initial concept and requirements analysis, through design and implementation, to deployment and monitoring. His mission becomes to proactively build quality into the product from the very beginning, not just verify it at the end. He becomes the architect and guardian of quality, not just its inspector.
The twilight of traditional QA: Why doesn’t the “quality gate” model work in Agile and DevOps?
To fully understand the depth of the transformation of the QA role, it is worth pausing for a moment to consider the limitations of the traditional sequential QA model, often associated with waterfall methodologies. In this approach, QA testing and verification activities were typically relegated to the final phase of the project following the completion of development. This led to a number of systemic problems and inefficiencies. First of all, defects detected at such a late stage were extremely costly to fix, as their removal often required significant changes to code already written and sometimes even to the system architecture. Second, long test cycles at the end of a project significantly delayed product delivery and slowed the flow of user feedback. Third, such a model often led to an unhealthy “us vs. them” atmosphere between the development team and the QA team, where testers were seen as the ones “spoiling the fun” by finding bugs in the developers’ work, which could lead to conflicts and mutual blame. The Agile philosophy, with its emphasis on iterative development, short cycles, rapid feedback and close collaboration, fundamentally challenged the wisdom of such an approach. In Agile, the expectation is to deliver working, valuable software at the end of each short iteration (sprint). Waiting until the very end of a sprint, much less the end of an entire project, to test is simply impossible and nullifies the basic tenets of agile. Similarly, the DevOps culture, which promotes automation, continuous integration (CI), continuous delivery (CD) and shared responsibility for the entire application lifecycle (from idea to production and maintenance), also does not tolerate bottlenecks and silos. The traditional QA model, operating as a separate “gateway,” would become a major inhibitor in such an environment, preventing the achievement of the fluidity, speed and reliability that are the hallmarks of mature DevOps implementations. It therefore became necessary to fundamentally redefine the role and place of QA in the manufacturing process, shifting the responsibility for quality “to the left” (shift-left testing), that is, as close as possible to the moment of code creation and requirements definition.
Modern QA Specialist at ARDURA Consulting: key roles and responsibilities in an agile team
So what are the key tasks, roles and areas of responsibility of the modern QA specialist on ARDURA Consulting’s agile, dynamic project team? His or her influence and involvement is evident throughout the software development lifecycle, and his or her role is multidimensional and vital to the success of the product. First and foremost, the modern QA specialist serves as an unwavering guardian of the end-user perspective and a tireless advocate for superior quality throughout the project team. Already at the sprint planning stage, during backlog refinement sessions or defining detailed requirements for individual functionalities (often in the form of User Stories), the QA specialist actively participates in discussions with the Product Owner, analysts and developers. He asks insightful questions, tries to identify potential ambiguities, specification gaps or hidden risks associated with proposed solutions. His goal is to help define Acceptance Criteria for any new functionality with precision, clarity and, most importantly, testability. With his analytical, often more skeptical outlook and ability to anticipate potential problems and edge scenarios, he helps ensure that the requirements being formulated are complete, consistent, understood by the entire team and verifiable, significantly preventing many costly errors later in development.
An extremely important aspect of the work of a modern QA is to work closely and in partnership with developers on a daily basis throughout the sprint or development cycle. The QA specialist no longer waits passively for a “finished,” fully implemented piece of code to be tested at the very end of an iteration. Instead, he or she often collaborates with developers already at the implementation stage of individual tasks. This can take the form, for example, of joint pair testing sessions, where the developer and tester explore and verify newly developed code fragments together at a single computer, or by organizing quick, informal verification sessions for small, completed pieces of functionality before they are integrated into the rest of the system. The QA specialist also actively assists in defining automated testing strategies, designing and creating effective unit and integration tests, ensuring that code is adequately covered by these tests and promoting good practices in this area to developers. Such early, almost immediate feedback on the quality of the resulting code allows bugs to be instantly detected and relatively inexpensively fixed before they can grow into serious, complex problems that are difficult to diagnose and costly to fix at a later stage. This synergy between QA and developers transforms the traditionally perceived confrontation into a genuine collaboration toward a common goal.
Of course, traditional functional testing is still an important and integral part of a QA specialist’s job, but in an agile, dynamic approach it often takes a slightly different, more flexible form. In addition to the systematic execution of planned, precisely defined test cases (which are increasingly common and automated, especially in the area of regression testing), a very strong emphasis is placed on intelligent exploratory testing. Under this technique, the tester, relying on his deep knowledge of the system, intuition, experience and creativity, freely explores the application, trying to discover unexpected problems, flaws in business logic, usability issues or unusual system behavior under non-standard conditions. A QA specialist on an agile team is also responsible for coordinating and often partially performing non-functional testing, such as usability testing, digital accessibility testing in accordance with current standards (e.g. WCAG), or basic early performance and security testing, often in collaboration with specialists dedicated to these more specialized areas. His role is to ensure that these key aspects of quality are addressed from the outset, rather than treated as an add-on at the end of the project.
Quality Engineering in the DevOps era: QA as a contributor to automated CI/CD pipelines
In an environment where DevOps culture and practices dominate, and automation is the absolute key to achieving speed, reliability and repeatable processes, the traditional role of QA is evolving even more rapidly, often into advanced Quality Engineering (QE). QA specialists, actually already quality engineers, are becoming active, key participants and contributors to the entire process of building, maintaining and continuously improving automated CI/CD (continuous integration and continuous deployment/delivery) pipelines. Their responsibility extends far beyond manual testing. It includes the strategic design and implementation of the automated test architecture, the integration of the different levels of these tests (such as unit tests, component and service integration tests, API tests, user interface tests - E2E) into the relevant stages of the application building and deployment process. Quality engineers configure and manage tools to automatically run tests, collect and transparently report the results of these tests, and continuously monitor key product and process quality indicators. Thanks to their work, the entire development team receives almost instant, fully automated feedback (fast feedback) on the state of product quality after every, even the smallest, change made to the code. This makes it possible to instantly detect regressions and other problems, which is fundamental to the implementation of Continuous Testing and allows new versions of the application to be safely and securely deployed to the production environment even several times a day, without worrying about reducing its quality or stability. In this model, the quality engineer becomes a key player in ensuring the smoothness and reliability of the entire value delivery pipeline. He also works closely with DevOps engineers to build and maintain stable, repeatable test environments (often using Infrastructure as Code), manage test data, and ensure the overall reliability and performance of the entire CI/CD pipeline.
Competencies of the Future: Profile of a versatile QA Specialist at ARDURA Consulting
To effectively and efficiently perform this modern, multifaceted and highly responsible role in ARDURA Consulting’s agile teams, today’s QA specialist must possess a broad, interdisciplinary array of competencies that go far beyond traditional testing skills. Of course, solid fundamentals, such as knowledge of classic test design techniques (e.g., equivalence classes, boundary value analysis, decision tables), the ability to effectively manage the defect lifecycle, and the ability to create clear test documentation, remain extremely important. However, an in-depth knowledge and practical understanding of the principles and ceremonies of agile methodologies (such as Scrum or Kanban), as well as the ability to actively and effectively participate in the scrum team, are becoming equally essential. Also key are highly developed **soft skills, primarily in effective communication, active listening, assertiveness, teamwork skills and constructive conflict resolution **. Analytical, critical and systems thinking is also essential, allowing for a deep understanding of complex systems, identifying potential risks, anticipating unusual scenarios and conducting thorough root cause analysis of problems. Increasingly, QA professionals are also expected to possess solid core technical skills, often referred to as T-shaped skills. These include, but are not limited to, a working knowledge of test automation tools and frameworks at various levels (e.g., Selenium, Cypress, Playwright for UI testing, REST Assured or Postman for API testing, JUnit/TestNG for Java unit testing, PyTest for Python, etc.).), the ability to write basic automation scripts, proficiency with version control systems (such as Git), basic knowledge of working with relational and non-relational databases, the ability to test and debug APIs (e.g., using browser developer tools or specialized API clients), and, in the context of cloud applications, an understanding of the basics of cloud platforms (AWS, Azure, GCP) and containerization technologies (Docker, Kubernetes). Above all, however, a modern QA specialist must be a proactive, autonomous person , extremely curious about the world of technology around him, constantly looking for new ways to improve the QA process, increase the efficiency of his work and bring real value to the team and the product. This is a person who is not afraid to ask questions, challenge the status quo and constantly learn.
In summary, the role of the Quality Assurance (QA) specialist in ARDURA Consulting’s modern agile development teams is far from being merely a passive “brakeman” of the manufacturing process or an isolated “quality controller” acting at the end of it. It is a **highly dynamic, proactive, broadly competent and extremely important function that involves working closely with the entire interdisciplinary team on a daily basis to consciously and systematically build the highest quality into the software under development at every, even the earliest, stage of its creatio **. The modern QA specialist is not just a tester, but first and foremost a quality engineer, a strategic partner to developers, analysts and business representatives, a tireless advocate of end-user needs and perspectives, and an absolutely key player in the entire process of delivering valuable, reliable, secure and usable software, at the fast, iterative pace imposed by today’s Agile methodologies and DevOps culture. At ARDURA Consulting, we are proud of our QA professionals and their contribution to the success of our clients’ projects.
Do you want to build software in agile methodologies, but are unsure how to effectively integrate QA into the process? Are you looking for a partner who understands the modern role of QA and can deliver specialists ready to work in a dynamic Agile/DevOps environment? Contact ARDURA Consulting. We will share our experience and show how an integrated approach to QA can become a key factor in the success of your agile projects.