Skip to content

Latest commit

 

History

History
58 lines (47 loc) · 4.31 KB

IntroductionOfTesting.md

File metadata and controls

58 lines (47 loc) · 4.31 KB
Raw

Introduction of Testing

Overview

This document provides an overview of the testing strategies

Aspect Unit Tests Integration Tests End-to-End (E2E) Tests
Scope Individual components or functions in isolation. Multiple components interacting together. The entire application as a whole.
Focus Single classes (e.g., services, utilities). Interactions (e.g., between services & database, controllers & services). Full user scenarios (UI, API, database, external services).
Characteristics - Fastest to run.
- Use mocks/stubs for dependencies.
- High number, more detailed.		 - Slower than unit tests.
- Use real instances of classes and often a real or in-memory database.
- Moderate number, cover interaction scenarios.		 - Most comprehensive.
- Mimic real user interactions.
- Slowest, fewer in number.
- Closest to production environment.
Tools & Annotations - JUnit or similar.
- @MockBean, @InjectMocks for mocking.		 - @SpringBootTest, @WebMvcTest.
- MockMvc, TestRestTemplate.		 - @SpringBootTest with WebEnvironment.RANDOM_PORT or DEFINED_PORT.
- TestRestTemplate, WebTestClient, Selenium.
Purpose Verify correctness of specific code parts. Validate integration of different application layers. Ensure overall functionality and user experience.

Running Tests with Gradle Kotlin Script

In a Gradle Kotlin DSL (build.gradle.kts), you can set up tasks to run different types of tests. Below is an example script that defines tasks for running unit, integration, and E2E tests:

tasks {
    test {
        useJUnitPlatform {
            includeTags("unit")
        }
    }

    register<Test>("integrationTest") {
        useJUnitPlatform {
            includeTags("integration")
        }
        mustRunAfter("test")
    }

    register<Test>("e2eTest") {
        useJUnitPlatform {
            includeTags("e2e")
        }
        mustRunAfter("integrationTest")
    }
}

In this script:

The test task is configured to run tests tagged with unit. integrationTest and e2eTest tasks are defined for running tests tagged with integration and e2e, respectively. mustRunAfter ensures a proper sequence of test execution. To use this setup, you would annotate your test classes in your project with @Tag("unit"), @Tag("integration"), or @Tag("e2e") depending on the type of test.

To run the tests, use the following commands in the terminal:

./gradlew test            # Run unit tests
./gradlew integrationTest # Run integration tests
./gradlew e2eTest         # Run E2E tests

Additional Resources