What is integration test

Project Source Code

Get the project source code below, and follow along with the lesson material.

Download Project Source Code

To set up the project on your local machine, please follow the directions provided in the README.md file. If you run into any issues with running the project source code, then feel free to reach out to the author in the course's Discord channel.

Table of Contents

This lesson preview is part of the Pain Free Mocking with Jest course and can be unlocked immediately with a \newline Pro subscription or a single-time purchase. Already have access to this course? Log in here.

This video is available to students only
Unlock This Course

Get unlimited access to Pain Free Mocking with Jest, plus 70+ \newline books, guides and courses with the \newline Pro subscription.

Thumbnail for the \newline course Pain Free Mocking with Jest

  • [00:00 - 00:14] In this lesson, we'll be discussing integration testing and how it differs from unit testing. Integration tests play a crucial role in ensuring the availability and functionality of our applications.

    [00:15 - 00:27] Before we delve into integration testing, let's take a look at the testing pyramid. The testing pyramid is a visual representation that illustrates the different layers of testing in software development.

    [00:28 - 00:42] At the base of the pyramid, we have unit tests, followed by integration tests, and finally at the top we have end-to-end tests. Now let's focus on integration testing and how it differs from unit testing.

    [00:43 - 00:56] Integration tests have a broader scope compared to unit tests, while unit tests focus on testing individual components or units of coding isolation. Integration tests verify how these components work together as well.

    [00:57 - 01:07] Integration tests provide a higher level of confidence in the reliability and functionality of our application. Integration tests are made up of units just like unit tests.

    [01:08 - 01:29] However, the units in this case are larger and include multiple components such as API endpoints, database interactions, and external services. For example, in a REST API application, the controller functions will qualify for integration testing as they handle the integration between the incoming HTTP requests and the underlying business logic.

    [01:30 - 01:53] Since integration tests involve multiple components and interactions, we can utilize them to perform less smoking. This means that we can test the actual behavior of our code without extensively simulating or smoking external dependencies or services. Integration testing offers a broader scope and a higher level of reliability guarantee compared to unit tests.

    [01:54 - 02:08] By testing the interaction between different components without extensive smoking, we can gain confidence in the functionality of our applications. Remember, integration tests are an essential part of a comprehensive testing strategy.