Code review is an important stage in the test automation lifecycle. In a team I was leading, we had discussions about our code review process. People raised concerns about inconsistencies, noting that some reviewers were overly strict, hindering task completion, while others allowed everything to merge. I will illustrate how we addressed and resolved this issue using both good and bad examples.
– Importance and impact of code review in the software test life cycle.
– Tips for an impactful code review
– Anti-patterns, Test Smells
– Summary & QA
Talk Takeaways
Mesut has 15+ years of experience in Industrial Automation, IoT platforms, SaaS/PaaS and Cloud Services, the Defense Industry, Autonomous Mobile Robots, and Embedded and Software applications. Along with having proficiency in CMMI and Scrum & PMP experiences under his belt, he has taken various roles as (Quality Owner, Hiring Manager, and Chapter Lead) in multinational projects.
He has expertise in test automation and integration to CI/CD platforms supporting continuous testing. Besides, he has been facilitating test processes and building the test strategy and lifecycle of the projects.
He is a frequent international speaker, the best presentation award winner, and a various program committees member: https://drive.google.com/file/d/1lKTxhk1KEhXBw4kJRTBnHrfusn1S6-Yi/view?usp=share_link
