During his university years, Márk Keresztúri already knew that a career in software testing awaited him. Since then, he has participated in numerous projects, proving himself even as a sole tester, and today he confidently navigates both manual and automated testing. In this interview, you will learn how he continuously develops his skills and why he considers the role of a tester crucial.
Q: In your opinion, what skills and personality traits are essential for becoming a successful software tester?
M: I believe the most important skill for a successful software tester is critical thinking. In fact, it is often advantageous to approach problems from "unusual" perspectives. This is crucial because it helps identify hidden or unexpected bugs that many might not even think could occur but would inevitably surface in real-world environments.
I also consider continuous self-improvement essential. Even in my free time, I strive to learn about new, useful, or simply interesting technologies and tools. This way, I stay up to date and can adapt more easily to the ever-evolving world of testing.
Q: What does a software tester do in their daily work? What steps do you go through in a testing project?
M: My software testing process always begins with reviewing and understanding the specifications. Then, I create a test plan and define test cases. Close collaboration with developers is key. For instance, we follow a two-phase testing approach: if I find bugs in the first testing phase, I verify the system again after they are fixed.
For test documentation, execution, and coverage measurement, I mainly use TestNavigator, but Postman is also a frequent companion. Regarding automated testing, I have worked with Cucumber and Pytest and am currently using Playwright.
The biggest challenge usually arises when working on multiple projects simultaneously — I am currently handling three at once. However, this is not an obstacle; rather, it requires thorough planning and continuous communication with the team to ensure everything is completed on time and with the required quality.
Q: TestNavigator was recently introduced in your team. What are your experiences with the system so far?
M: Since implementing TestNavigator, we have evaluated the system from several perspectives. The initial impression is that the interface is intuitive, and tracking tests has become more transparent. A significant advantage is the automated reporting capabilities and the easier tracking of test statuses.
The Test Advisor Score is particularly valuable as it provides an objective overview of the testing process and helps us execute only the necessary tests, saving time and effort.
This is especially useful for a tester working on multiple projects simultaneously, as well as for management, as it provides a tangible overview of the testing status.
Additionally, regression test management has become more structured, and API test integration is now smoother, contributing to more efficient testing workflows.
Q: Do you prefer automated or manual testing?
M: The clear advantage of automated testing is that while it requires a significant initial investment of time and resources, it later streamlines and accelerates the testing process considerably. In contrast, manual testing heavily relies on detailed documentation (test cases, reports), which must be updated whenever specifications change, requiring repeated manual execution of tests. Ultimately, the choice depends on project size, available resources, and long-term goals. In cases where rapid turnaround and frequent modifications are needed, automation is more beneficial. However, for smaller or simpler projects, a manual approach can often be more efficient.
Q: What role does software testing play in the success of development projects?
M: Software testing is indispensable for the success of development projects. Identifying and fixing bugs early significantly reduces future risks, time investment, and costs. If we test continuously from the early stages of a project, even minor issues are discovered in time, preventing them from escalating into critical system-wide failures. This approach is crucial for both user and client satisfaction, as a well-tested software product is more reliable and stable.
If testing is neglected or initiated too late, critical defects may remain hidden, leading to unpleasant surprises for end users or clients. As a result, negative feedback becomes more likely, and the project's reputation may suffer. Therefore, it is advisable to start test planning and continuous verification as early as the development phase to ensure the highest possible software quality.
Q: What methods and tools do you use to develop your professional knowledge and skills?
M: I frequently participate in online courses, particularly on platforms like Udemy. These courses help me stay informed about emerging or trending technologies, methodologies, and new features of already familiar tools.
I believe that continuous learning, combined with hands-on experience in different projects, enables me to efficiently understand and work with even the most complex systems, ensuring successful quality assurance.
Q: How do you effectively collaborate with developers and other team members?
M: Over the past two and a half years, I have not encountered major conflicts or disagreements, as everyone in our team naturally treats each other with respect.
As a tester, I always strive to communicate problems or questions as efficiently as possible — often opting for direct discussions or online meetings when necessary, especially when team members are working remotely. In my role as a Scrum Master, I regularly conduct Scrum meetings, which help the team stay informed about all tasks and potential challenges.
Since I often work as the sole tester on projects, I bear full responsibility for all quality assurance tasks. This makes it essential to coordinate effectively with all team members, whether they are developers or other stakeholders. I believe there is no special secret: the key is to approach each other as people and communicate openly, even under tight deadlines or when unexpected issues arise.
Q: What common misconceptions or stereotypes do you encounter about software testing?
M: In non-IT environments, I often hear the misconception that a tester’s job is merely "clicking around," as if the role were nothing more than playing a game. In reality, the testing process is far more complex—it involves verifying functionality, usability, and uncovering deep-seated defects.
In development projects, this misunderstanding is less common, as everyone understands the tester's critical role in ensuring software quality. Interesting situations can arise when developers and testers interpret specifications differently, requiring precise discussions to clarify the expected system behavior.