"Fossies" - the Fresh Open Source Software Archive

Member "junit5-r5.5.2/documentation/src/docs/asciidoc/user-guide/appendix.adoc" (8 Sep 2019, 6508 Bytes) of package /linux/privat/junit5-r5.5.2.tar.gz:

As a special service "Fossies" has tried to format the requested source page into HTML format (assuming AsciiDoc format). Alternatively you can here view or download the uninterpreted source code file. A member file download can also be achieved by clicking within a package contents listing on the according byte size field.


Dependency Metadata

Artifacts for final releases and milestones are deployed to {Maven_Central}, and snapshot artifacts are deployed to Sonatype’s {snapshot-repo}[snapshots repository] under {snapshot-repo}/org/junit/[/org/junit].

JUnit Platform

  • Group ID: org.junit.platform

  • Version: {platform-version}

  • Artifact IDs:


    Common APIs and support utilities for the JUnit Platform. Any API annotated with @API(status = INTERNAL) is intended solely for usage within the JUnit framework itself. Any usage of internal APIs by external parties is not supported!


    Support for discovering and executing tests on the JUnit Platform from the console. See [running-tests-console-launcher] for details.


    An executable JAR with all dependencies included is provided in Maven Central under the junit-platform-console-standalone directory. See [running-tests-console-launcher] for details.


    Public API for test engines. See [launcher-api-engines-custom] for details.


    Public API for configuring and launching test plans — typically used by IDEs and build tools. See [launcher-api] for details.


    TestExecutionListener implementations that generate test reports — typically used by IDEs and build tools. See [launcher-api-listeners-reporting] for details.


    Runner for executing tests and test suites on the JUnit Platform in a JUnit 4 environment. See [running-tests-junit-platform-runner] for details.


    Annotations for configuring test suites on the JUnit Platform. Supported by the JUnitPlatform runner and possibly by third-party TestEngine implementations.


    Provides support for executing a test plan for a given TestEngine and then accessing the results via a fluent API to verify the expected results.

JUnit Jupiter

  • Group ID: org.junit.jupiter

  • Version: {jupiter-version}

  • Artifact IDs:


    JUnit Jupiter aggregator artifact that transitively pulls in dependencies on junit-jupiter-api, junit-jupiter-params, and junit-jupiter-engine for simplified dependency management in build tools such as Gradle and Maven.


    JUnit Jupiter API for writing tests and extensions.


    JUnit Jupiter test engine implementation; only required at runtime.


    Support for parameterized tests in JUnit Jupiter.


    Support for migrating from JUnit 4 to JUnit Jupiter; only required for support for JUnit 4’s @Ignore annotation and for running selected JUnit 4 rules.

JUnit Vintage

  • Group ID: org.junit.vintage

  • Version: {vintage-version}

  • Artifact ID:


    JUnit Vintage test engine implementation that allows one to run vintage JUnit tests on the JUnit Platform. Vintage tests include those written using JUnit 3 or JUnit 4 APIs or tests written using testing frameworks built on those APIs.

Bill of Materials (BOM)

The Bill of Materials POM provided under the following Maven coordinates can be used to ease dependency management when referencing multiple of the above artifacts using Maven or Gradle.

  • Group ID: org.junit

  • Artifact ID: junit-bom

  • Version: {bom-version}


Most of the above artifacts have a dependency in their published Maven POMs on the following @API Guardian JAR.

  • Group ID: org.apiguardian

  • Artifact ID: apiguardian-api

  • Version: {apiguardian-version}

In addition, most of the above artifacts have a direct or transitive dependency on the following OpenTest4J JAR.

  • Group ID: org.opentest4j

  • Artifact ID: opentest4j

  • Version: {ota4j-version}

Dependency Diagram

skinparam {
    defaultFontName Open Sans

package org.junit.jupiter {
    [junit-jupiter] as jupiter
    [junit-jupiter-api] as jupiter_api
    [junit-jupiter-engine] as jupiter_engine
    [junit-jupiter-params] as jupiter_params
    [junit-jupiter-migrationsupport] as jupiter_migration_support

package org.junit.vintage {
    [junit-vintage-engine] as vintage_engine
    [junit:junit] as junit4

package org.junit.platform {
    [junit-platform-commons] as commons
    [junit-platform-console] as console
    [junit-platform-engine] as engine
    [junit-platform-launcher] as launcher
    [junit-platform-reporting] as reporting
    [junit-platform-runner] as runner
    [junit-platform-suite-api] as suite_api
    [junit-platform-testkit] as testkit

package org.opentest4j {

package org.apiguardian {
    [apiguardian-api] as apiguardian
    note bottom of apiguardian #white
        All artifacts except
        opentest4j and junit:junit
        have a dependency on this
        artifact. The edges have
        been omitted from this
        diagram for the sake of

jupiter ..> jupiter_api
jupiter ..> jupiter_params
jupiter ..> jupiter_engine

jupiter_api ..> opentest4j
jupiter_api ..> commons

jupiter_engine ..> engine
jupiter_engine ..> jupiter_api

jupiter_params ..> jupiter_api
jupiter_migration_support ..> jupiter_api
jupiter_migration_support ..> junit4

console ..> launcher
console ..> reporting

launcher ..> engine

engine ..> opentest4j
engine ..> commons

reporting ..> launcher

runner ..> launcher
runner ..> suite_api
runner ..> junit4

testkit ..> opentest4j
testkit ..> launcher

vintage_engine ..> engine
vintage_engine ..> junit4