“Identifying code smells”
Code smells occur in the source code of an application and can indicate deeper problems that are not apparent at first glance. Identifying and fixing these issues helps tremendously in securing and future-proofing the application under development and allows developers and testers to better understand, maintain, extend, and test the code.
Recognizing code smells can help in estimating the effort required for certain tasks, assessing the quality of work, and making informed decisions about refactoring. It can also aid in identifying potential risks and bottlenecks early in the development cycle, thereby saving time and resources in the long run.
In this session I will go through the different categories of code smells and explain each one with example code. Also, I will explain why it is good to know and be able to name different code smells even if you don’t do any programming yourself.
Bio
After 15 years of being a software developer and trainer, Benjamin transitioned to test automation in 2016. Currently, he works as a Test Automation Engineer at Trivago N.V. in Düsseldorf, Germany. There, he focuses on backend and frontend test technologies and pipelines. Benjamin authored the book “Writing API Tests With Karate” and maintains some test related open source projects. He is a regular conference speaker and also writes blog posts about testing, automation and software craftsmanship on his website, softwaretester.blog.
Social networks
- -> Github
- -> softwaretester.blog