The agile approach remains a significant trend in software development, where the role of the tester is gradually pushed out of agile teams. On the contrary, the role of the developer within the agile team is expected to extend it to the area of testing, and thus to take over the tasks of the tester.

There is an effort that the people working on the project are both developers and testers and have the so-called developerˈs skills and testerˈs mindset.


However, it remains a well-known fact that the mindset of the developer and the tester are different from each other, which can be observed in each phase of SDLC (Software Development Life Cycle). While the developer asks questions: ˈHow would I program it? How to make it work? ˈ, the tester asks: ˈWhat can go wrong? Where there may be vulnerabilities? ˈ and views the product from the user's perspective.

The reduction in the number of people in teams and the limited time devoted to testing often result in software testing being done only superficially. The developer lacks the space for more thorough testing.

With lower testing requirements, product quality decreases and the number of bugs and bug fixes during one sprint increases. Subsequently, project managers begin to realize the need for quality improvement and specialized testers are invited to the project. Thanks to their creative approach, practical product grasp and logical thinking, qualified testers will ensure independent quality control at the output, even during agile development.

While the developer carries out as priority Unit tests and tests small fragments, the tester focuses on functional testing and integration testing. He tests rather procedurally. He understands customer requirements, context and the product as a whole.

Deploying independent testing before putting the product into production minimizes risk, detects and filters errors, determines the suitability of software for production, and thus saves time and money.

Accepting differences in the thinking of developers and testers is essential for well-functioning teams. Different approaches help to find the best solutions and lead to the delivery of a reliable product that meets the customer's requirements. Only cooperation hand in hand between the tester and the developer, mutual understanding and objective feedback guarantee the best product quality.


The ideal solution, division of roles and number of people in the team are still being sought. It depends on the quality of the people working on the project and the time limits - to what extent the developers can ensure the delivery of the final product in sufficient quality. However, it can be said with certainty that manual testing and the role of the tester is important and cannot be ruled out even with AGILE approaches.