JUnit: Фреймворк для тестирования Java приложений

Java testing framework

JUnit is a test automation framework for the Java programming language. JUnit is often used for unit testing, and is one of the xUnit frameworks. JUnit is linked as a JAR at compile time. The latest version of the framework, JUnit 5, resides under package Previous versions JUnit 4 and JUnit 3 were under packages and , respectively. A research survey performed in 2013 across 10,000 Java projects hosted on GitHub found that JUnit (in a tie with slf4j api) was the most commonly included external library. Each library was used by 30.7% of projects.

Every JUnit test class usually has several test cases. These test cases are subject to the test life cycle. The full JUnit Life Cycle has three major phases:
Setup phase This phase is where the test infrastructure is prepared. Two levels of setup are available. The first type of setup is class level setup in which a computationally expensive object, such as a database connection, is created and reused, with minimal side effects. Class level setup is implemented using the annotation. The other type is setup before running each test case, which uses the annotation. Test execution This phase is responsible for running the test and verifying the result. The test result will indicate if the test result is a success or a failure. The annotation is used here. Clean up phase After all posttest executions are performed, the system may need to perform cleanup. Similar to class level setup, there is a corresponding class level clean up. The annotation is used to support class level clean up. The annotation allows for cleanup after test execution.

JUnit 5 integrates a number of tools, such as build tools, integrated development environments (IDE), continuous integration (CI) tools and many more.

JUnit supports Apache Ant, Apache Maven and Gradle build tools, which are the most widely used project build tools. Build tools are vital for automating the process of building the project.

Apache Ant, also known as Ant, is one of the build tools with the highest degree of versatility, and has the longest history out of the three build tools listed above. Ant centers around the build. xml file, used for configuring the tasks necessary to run a project. Ant also has an extension called Apache Ivy, which helps deal with dependency resolution. The project dependencies can be declared in the ivy. xml file. Ant can integrate with JUnit 5 by configuring the Java code coverage tools (JaCoCo), for the ivy. xml file. The ivy. xml can then be configured with the java platform console and junit platform runner dependencies to integrate with JUnit 5.

In contrast to Ant, Apache Maven, also known as Maven, uses a standardized and unified approach to the build process. Maven follows the paradigm of "convention over configuration" for managing its dependencies. The Java source code (or "src") can be found under the src/main/java directory, and the test files can be found under the src/test/java directory. Maven can be used for any Java Project. It uses the Project Object Model (POM), which is an XML based approach to configuring the build steps for the project. The minimal Maven with the pom. xml build file must contain a list of dependencies and a unique project identifier. Maven must be available on the build path to work. Maven can integrate with JUnit 5 using the jacoco maven plugin plugin which supports out of box functionality for JUnit 5 tests. Different Maven goals can be specified to achieve these tasks.

Gradle is a build tool that borrows many concepts from its predecessors, Ant and Maven. It uses the file to declare the steps required for the project build. Unlike Ant and Maven, which are XML based, Gradle requires the use of Apache Groovy, which is a Java based programming language. Unlike Ant and Maven, Gradle does not require the use of XML. Gradle still adheres to Maven's "convention over configuration" approach, and follows the same structure for and directories. Gradle can integrate with JUnit 5 by configuring a plugin alongside the junit platform plug in given by the JUnit 5 team in the build file.