Testing your code is an important part of the software development process. This is to confirm that your code behaves the way you want it to. It also allows you to find and fix bugs early on before they have a chance to cause problems in production. In this article, we'll go over why testing your code is important. There are many different ways of testing your code, and we'll cover the most important way -- unit testing. Always Test Your Code Before we talk about the , let's talk about the . What is code testing? . Easy as that. why's what This is to ensure your code works the way you want it to work Now, why should you bother testing your code? Imagine you have a program with a single module. It's responsible for one thing and one thing only. Testing it might seem like overkill (but I recommend always testing your code). Now imagine your program has five modules that all do different things. Additionally, the modules communicate with each other. Your program now has many possible states and testing all states manually will take up a lot of your precious time. By testing your code, you also protect yourself against breaking features when you add new code. You want to write quality code, right? It's not possible without testing it. Instead, you should write tests to confirm the behavior! Unit Testing Your Code There are various types of tests that you can run on your code, but unit tests are the most important. They allow you to test individual units of code in isolation. Let's look at this JavaScript function. const incrementByOne = input => {
  if (input < 0) {
    return 0;
  }

  return input + 1;
}; Now let's write some tests. I would like to start by testing the "happy path". test('should increment by 1', () => {

  const input = 9;

  const actual = incrementByOne(input);
  const expected = 10;

  expect(actual).toBe(expected);
}); And then for the fun part: the edge cases! test('should return 0 when negative input', () => {

  const input = -1;

  const actual = incrementByOne(input);
  const expected = 0;

  expect(actual).toBe(expected);
}); We've now tested everything, and have 100% test coverage. And are we happy, ? or are we I chose JavaScript because it's , and we're allowed to pass any type into our function ( ). dynamically typed psst! This is a good reason to instead use TypeScript What happens if we pass a ? string test('should increment by 1', () => {

  const input = 'my-string';

  const actual = incrementByOne(input);
  const expected = ???;

  expect(actual).toBe(expected);
}); The function will return because the operator works between types in JavaScript. This is not what we want, so let's fix it. my-string1 + Let's update the function to handle this case. const incrementByOne = input => {
  if (typeof input !== 'number') {
    throw new TypeError('Only number type allowed');
  }

  if (input < 0) {
    return 0;
  }

  return input + 1;
}; Now let's add another test to our test suite. test('should throw when non-number input', () => {

  const input = 'my-string';

  const expected = new TypeError('Only number type allowed');
  expect(() => incrementbyOne(input)).toThrowError(expected);
}); This was a simple example. Websites and programs are never trivial though, and I hope you can see the value of testing your code now. Testing your code is a crucial part of delivering high-quality software. It should be a fundamental part of your software development process! Unit testing is not a silver bullet, and it is not a substitute for other forms of testing, such as system testing and user acceptance testing. However, unit testing is an important part of the software testing process and should not be ignored. Conclusion When it comes to code, testing is key to avoiding bugs and ensuring that your code runs as expected. By taking the time to test your code, you can avoid costly mistakes and ensure that your code is ready for prime time. Connect with me on Twitter @prplcode Also published at https://prplcode.dev

Mozilla

Twitter

4 Reasons That Will Make Vim Your Favorite Editor

The Benefits of Writing in English (as a Non-Native Speaker)

Support Me on Coil

Portfolio

Nominated for 2022 - HackerNoon Contributor of the Year - Productivity

Nominated for 2022 - Remote Work Warrior

Nominated for Super Career Strategist of 2022

Nominated for 2022 - HackerNoon Contributor of the Year - Software Engineering

Nominated for 2022 - Software Developer of the Year

Nominated for 2022 - HackerNoon Contributor of the Year - Email

Nominated for 2022 - HackerNoon Contributor of the Year - Github

Nominated for 2022 - HackerNoon Contributor of the Year - Future Of Work

Too Long; Didn't Read

Make resilience your competitive advantage

Basics of Unit Testing in Software Development

Basics of Unit Testing in Software Development

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Write Git Commit Messages That Your Colleagues Will Love

The Noonification: The Metaverse is a Sh*tshow (11/2/2022)

The Noonification: The Four Horsemen of Flaky Tests (10/24/2023)

11 Best Automation Testing Tools to Try in 2021

12 Common Software Testing Misconceptions Debunked

Write Git Commit Messages That Your Colleagues Will Love

The Noonification: The Metaverse is a Sh*tshow (11/2/2022)

The Noonification: The Four Horsemen of Flaky Tests (10/24/2023)

11 Best Automation Testing Tools to Try in 2021

12 Common Software Testing Misconceptions Debunked

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps