Code Quality Basics - What Are Code Smells?


Image


In this article, we have a closer look at code smells. We see what they are, and what you should do about them.

You will learn

  • What Are Code Smells?
  • What are the typical code smells?
  • How do you identify code smells?
  • How do you react to code smells?

Free Courses - Learn in 10 Steps

Article Series

This is the sixth article in a series of eight articles on Code Quality

What Are Code Smells?

A code smell refers to a certain pattern in the code that signals there could be a defect lurking somewhere.

Static analysis tools are very good at detecting code smells. They analyze the patterns, and then see if they could lead to a problem.

For example, if you assign a variable in Java a null value, and then immediate call a method on it, a NullPointerException would result. That is nothing but a code smell!

If you do static analysis of that part of code, the tool would indicate there is a high chance of a defect in the code at that point.

Choosing static analysis tools is the best way to detect code smells in your application:

image info

SonarQube has great tools for detecting code smells. what we see in the snapshot above are the rules for Java, and a profile where there are 194 code smells present.

Typical Code Smells

What are examples of typical code smells? Let’s take the example of Java programs:

  • You make use of a deprecated method definition, that is annotated by @Deprecated
  • You make use of a for loop, but do not increment/decrement the loop counters
  • You access a static member using an instance variable
  • You make use of a switch statement, but do not have a default clause
  • You have a switch statement with just two case clauses
  • You call toString() on a String object
  • In a situation where you need to use a while loop, you use a for loop
  • You name a class as Exception, but do not extend the built-in Exception class, or a subclass of it
  • You throw an exception in the finally clause
  • You throw very generic exceptions
  • You use a try-catch block, where a try-with-resources might be a better option
  • You have unused private methods

When you see instances of such smells, you conclude that the developer does not fully understand what he/she was trying to do. Such situations could cause hidden bugs to exist in the code.

Other Kinds Of Code Smells

Other kinds of code smells could exists, especially in your JUnit code. These include:

  • Ignored unit tests
  • Empty test case
  • Test case without asserts

Handling Code Smells

Make sure that having zero code smells is an integral part of your Definition Of Done.

It is important that you do static analysis and manual code review on a regular basis.

Static analysis should be part of continuous integration build.

Do check out our video on the same topic:

image info

Summary

Code smells are patterns in code that could indicate hidden bugs. The two ways to detect code smells are static analysis, and manual code reviews. It is important to do both systematically, to keep the application free of code smells.

Best Selling Udemy Courses

Image
Image Image Image Image Image Image Image Image Image

Join 450,000 Learners and 30+ Amazing Courses

350,000 Learners are learning everyday with our Best Selling Courses : Spring Boot Microservices, Spring, Spring Boot, Web Services, Hibernate, Full Stack React, Full Stack Angular, Python, Spring Interview Guide, Java Interview, Java Functional Programming, AWS, Docker, Kubernetes, PCF, AWS Fargate and Azure


Do not know where to start your learning journey? Check out our amazing learning paths:
Learning Path 01 - Spring and Spring Boot Web Applications and API Developer,
Learning Path 02 - Full Stack Developer with Spring Boot, React & Angular,
Learning Path 03 - Cloud Microservices Developer with Docker and Kubernetes,
Learning Path 04 - Learn Cloud with Spring Boot, AWS, Azure and PCF and
Learning Path 05 - Learn AWS with Microservices, Docker and Kubernetes


Subscribe

FREE COURSES



Related Posts

Writing Integration Tests for Rest Services with Spring Boot

Setting up a basic REST Service with Spring Boot is a cake walk. We will go one step further and add great integration tests!

Integrating Spring Boot and Spring JDBC with H2 and Starter JDBC

Learn using Spring Boot Starter JDBC to connect Spring Boot to H2 (in memory database) using Spring JDBC. You will create a simple project with Spring Boot. You will add code to the project to connect to a database using Spring JDBC. You will learn to implement the basic CRUD methods.

JUnit Tutorial for Beginners in 5 Steps

JUnit Tutorial for Beginners in 5 Steps. Setting up a basic JUnit example and understanding the basics of junit.

JPA and Hibernate Tutorial For Beginners - 10 Steps with Spring Boot and H2

JPA and Hibernate in 10 Steps with H2 - Setting up a basic project example with Spring Boot and in memory database H2. Its a cake walk.

Spring Boot Tutorial For Beginners in 10 Steps

Introduction to Spring Boot in 10 Steps. Learn the basics of Spring Boot setting up a basic project example with Spring Boot.

Spring Framework Tutorial for Beginners - Your First 10 Steps

Learn the basics of Spring Framework setting up a very simple example.

JPA and Hibernate Tutorial using Spring Boot Data JPA

Complete journey starting from JDBC to JPA to Spring Data JPA using an example with Spring Boot Data JPA starter project. We use Hibernate as the JPA Implementation.

Creating a Web Application with Spring Boot with JSP

Setting up a basic web application with Spring Boot is a cake walk. We will create a simple web application using Spring Initializr and add JSP features to it.

What is Spring Boot Auto Configuration?

Auto Configuration is the most important feature in Spring Boot. In this tutorial, we will learn important concepts about Auto Configuration with a couple of examples.

Unit Testing Rest Services with Spring Boot and JUnit

Setting up a Basic REST Service with Spring Boot is a cake walk. We will go one step further and add great unit tests to our RESTful Service.


Search