Clean Code - Testing Practice

Quiz

Writing tests for code is essential for maintaining its quality and catching bugs and errors early. Testing is not an extra thing you do when code is done in clean code practices; its considered an integral part of the development process which is necessary. Good tests always improve the quality of code also it makes code more reliable and maintainable. Also, makes it easier for you to refactor your code or if you want to add new features without breaking the existing functionality of the code. Here we will understand different aspects of writing clean, effective tests that help keep your codebase better and easy to work with.

Why Write Tests?

Tests ensure that the code behaves exactly how you expect it to behave. It is not only about catching bugs or finding errors, though thats an important and huge part of it, but it also keeps you free from worries while making changes to the codebase. If tests are written in your codebase, you have a safety net, so when you change something or add new features, you can be confident that if something breaks, the tests will let you know right away and you can fix that particular part of code. Good tests also act like a living documentation of the codebase, showing how different parts of the system are expected to behave.

Types of Testing

There are various kinds of tests you can write, and each serves its own purpose in covering different areas of your code. Its good to understand what type of testing you will need in your code according to your needs. Here are some of the main types of testing that you often come across or end up using them:

Unit Testing: Unit tests focus on individual components or functions, testing them in isolation, it doesn't mix them up with other code. The main goal of unit testing is to ensure that each function works as expected without depending on other parts of the codebase. Think of it like testing one Lego block at a time to make sure each block fits right before building a big Lego castle./li>
```
 // Unit test for adding two numbers
 function add(a, b) {
    return a + b;
 }
 console.assert(add(2, 3) === 5, 'Adding 2 and 3 should be 5');
```
Integration Testing: Integration tests check if different parts or modules of the code work together as expected or not. These test cases help us to make sure that all the parts and functions work fine together. Just like Lego blocks fit together correctly and the castle doesnt fall apart when one piece is added to another. Integration tests are best for catching issues that arise when different parts of the system interact with each other and work together.

// Integration test for user authentication
async function authenticateUser(userId, password) {
   let isAuthenticated = await checkPassword(userId, password);
   if (isAuthenticated) {
      return generateSessionToken(userId);
   }
   throw new Error('Invalid credentials');
}
console.assert(await authenticateUser('user123', 'password') !== null, 'User should be authenticated');

End-to-End Testing (E2E): End-to-end tests what real users use and check the whole system rather than one part or multiple. Instead of testing only the backend or testing only the frontend, These tests interact with the actual environment, including the frontend, backend, database, and network requests, to make sure that the entire application behaves correctly from start to finish and does not cause problems to the user. Its like testing the whole Lego castle by shaking it around a bit to see if any pieces fall off.

// End-to-end test for logging in
describe('Login Page', () => {
   it('should allow user to log in with valid credentials, () => {
      browser.url('/login'); $('#username').setValue('testuser'); $('#password').setValue('password123'); $('#loginButton').click(); expect($('#welcomeMessage')).toBeDisplayed();
   });
});

Writing Clean Tests

Writing clean tests follows many of the same principles as writing clean code. Its about making tests easy to read, maintain, and understand, even for someone who wasnt involved in writing them or anyone who doesn't have a clue about code. The tests should also be reliable and consistent, which means they should pass or fail for the right reasons and not because of flaky and wrong test setups. There are some guidelines for writing tests that follow clean code principles those are:

Use Descriptive Names: The name of the test should make it very clear what its checking for. Its like giving the test a little description so that anyone can understand what is that test for without needing to look into the test code. Descriptive makes it easy to identify test cases right away.
Keep Tests Short: A test should be focused and test one thing at a time instead of covering multiple things at a time. Long, complicated tests become a pain to maintain and understand, just like a giant run-on sentence would be hard to read and understand.
Avoid Hard-Coding Values: Instead of hard-coding values, use constants or variables in your tests. It makes your tests more flexible and easier to update if the requirements change. Like if you are checking the login platform, don't hard-code username and password directly into the code. It may arise a problem when the username or password expires, also it compromises the security.
Dont Repeat Yourself: Use helper functions or setup methods to keep your test code DRY (Dont Repeat Yourself). Like if you need the same code for testing multiple features or parts just don't write it again and again. Make distinct functions for each functionality. Duplicating code across multiple tests can make maintenance more difficult.

// Example of using a helper function in tests
function createUser(username) {
   return {
      username: username,
      createdAt: new Date()
   };
}
console.assert(createUser('john').username === 'john', 'User should have correct username');

Mocking and Stubbing

When writing tests, if you dont always want to use real data or connect to actual services. Mocking and stubbing can really help you in this case. They let you pretend parts of the system, such as network requests or database queries so that you can test your code in isolation without depending on external factors or real data and services.

Mocking: Mocking is about creating a fake version of an object that behaves just like the real thing. Its useful for testing how different parts of your code interact without relying on the actual implementations, which could be slow, unreliable, or hard to control in a test environment. This helps us to test easily.

// Example of mocking a function
let mockFunction = jest.fn(() => 'mocked value');
console.assert(mockFunction() === 'mocked value', 'Mock function should return mocked value');

Stubbing: Stubbing is the same as mocking but it involves replacing a function or method with a predefined response. Its useful when you need to pretend certain scenarios, like a network request returning an error or something.

// Example of stubbing a function
let stubFunction = sinon.stub().returns(42);
console.assert(stubFunction() === 42, 'Stub function should return 42');

Test Coverage

Test coverage measures how much of your code is being covered by tests. The higher the coverage, the less likely you are to have untested bugs hiding in the code. Always aim for high coverage, but dont try to hit 100%. Focus more on covering the critical parts of your code that are most likely to have bugs or are more complicated. Testing important functions and features is helpful.

Code Coverage Tools: Tools like Jest, Mocha, or Istanbul can be used to measure code coverage in JavaScript projects. And we have other tools for another language. These tools show you which parts of your code are being tested and which are not, which gives you an idea of where you might need to add more tests.

Testing Best Practices

Write Tests First: Try to practice Test-Driven Development (TDD), where you write the tests before implementing the actual code. It forces you to think about the requirements first and helps in writing better code. Its like setting the rules before playing the game.
Test Both Positive and Negative Scenarios: Make sure youre testing not just the "happy path" where everything goes smoothly, but also edge cases, errors, and unexpected inputs. That way, you will be Always prepared for real-world situations.
Run Tests Regularly: Make testing a part of your development process you can say a routine. Run your tests whenever you make changes to the code, and set up automated tests to run on every commit.
Keep Tests Independent: Tests should not rely on each other to pass. Each test should be able to run on its own without needing any setup from other tests.

Conclusion

Testing is not just a side or an extra activity in clean coding; its an important practice that makes your code more reliable and easier to maintain. Writing clean tests requires the same principles as writing clean code: simplicity, consistency, and readability are a must. Use mocking and stubbing wherever necessary, make sure to aim for meaningful test coverage, and follow testing best practices to ensure your code remains strong bug-free, and error-free.

Print Page

Save or share this article