kora-testing-junit-java

Kora Testing JUnit (Java)

Kora sub-skill — obey the kora-v1 meta rules on every task: R0 ensure .kora-agent/ docs+examples are cloned · R1 read this sub-skill before writing code · R2 Kora APIs only — no Spring/Micronaut/Quarkus, no invented annotations or config keys · R3 journal any incorrect Kora usage. Add comments/Javadoc only if asked.

In-process JUnit 5 tests for Java Kora services. @KoraAppTest builds a trimmed version of your compile-time dependency graph, then injects the components you ask for with @TestComponent. The same code that runs in production is exercised in the test; selected dependencies can be replaced by mocks or test-only components.

Kora supports three test levels:

• Component test — one component plus the dependencies needed to build it.
• Inter-component test — several real components interacting.
• Integration test — real components plus external systems (PostgreSQL, Kafka) via Testcontainers.

For end-to-end confidence the Kora maintainers also recommend black-box testing of the packaged image (see the kora-testing-blackbox skill).

---

Quick Start

Dependencies

dependencies {
    koraBom platform("ru.tinkoff.kora:kora-parent:1.2.19")

    annotationProcessor "ru.tinkoff.kora:annotation-processors"

    testImplementation platform("org.junit:junit-bom:5.13.4")
    testImplementation "org.junit.jupiter:junit-jupiter"
    testImplementation "ru.tinkoff.kora:test-junit5"
    testImplementation "org.mockito:mockito-core:5.18.0"
}

test {
    useJUnitPlatform()
    testLogging {
        showStandardStreams(true)
        events("passed", "skipped", "failed")
        exceptionFormat("full")
    }
}

The kora-parent BOM pins every ru.tinkoff.kora:* artifact — never set their versions individually. The annotation processor is mandatory: without it the @KoraApp graph is never generated and @KoraAppTest has nothing to load.

Component test (real graph)