JarCastingТестирование компонентов
Последняя версия: 3.11.2
Дата:Последняя версия: 7.4.0
Дата:
JUnit 5 (Bill of Materials)
org.junit : junit-bomThis Bill of Materials POM can be used to ease dependency management when referencing multiple JUnit artifacts using Gradle or Maven.
Последняя версия: 5.8.0-M1
Дата:
Последняя версия: 3.11.2
Дата:
mockito-inline
org.mockito : mockito-inlineMockito preconfigured inline mock maker (intermediate and to be superseeded by automatic usage in a future version)
Последняя версия: 3.11.2
Дата:
JUnit Jupiter Engine
org.junit.jupiter : junit-jupiter-engineModule "junit-jupiter-engine" of JUnit 5.
Последняя версия: 5.8.0-M1
Дата:
Последняя версия: 2.3.10
Дата:
Последняя версия: 5.8.0-M1
Дата:
Последняя версия: 2.0.2-beta
Дата:
Последняя версия: 3.0.8
Дата:
JUnit Jupiter Params
org.junit.jupiter : junit-jupiter-paramsModule "junit-jupiter-params" of JUnit 5.
Последняя версия: 5.8.0-M1
Дата:
JUnit Vintage Engine
org.junit.vintage : junit-vintage-engineModule "junit-vintage-engine" of JUnit 5.
Последняя версия: 5.8.0-M1
Дата:
OPS4J Pax Exam Driver JUnit4
org.ops4j.pax.exam : pax-exam-junit4Pax Exam Integration testing framework for Modern Java Platforms.
Последняя версия: 4.13.4
Дата:
Последняя версия: 2.0.9
Дата:
Apache Groovy
org.codehaus.groovy : groovy-test-junit5Groovy: A powerful, dynamic language for the JVM
Последняя версия: 3.0.8
Дата:
Последняя версия: 2.0.9
Дата:
Последняя версия: 1.7.4
Дата:
JUnit Platform Launcher
org.junit.platform : junit-platform-launcherModule "junit-platform-launcher" of JUnit 5.
Последняя версия: 1.8.0-M1
Дата:
Последняя версия: 5.8.0-M1
Дата:
Arquillian TestRunner JUnit Container
org.jboss.arquillian.junit : arquillian-junit-containerJUnit Container Implementation for the Arquillian Project
Последняя версия: 1.7.0.Alpha10
Дата:Последняя версия: 1.1.9
Дата:
Testcontainers :: JUnit Jupiter Extension
org.testcontainers : junit-jupiterIsolated container management for Java code testing
Последняя версия: 1.16.0
Дата:
OPS4J Pax Exam JUnit Probe Invoker
org.ops4j.pax.exam : pax-exam-invoker-junitPax Exam Integration testing framework for Modern Java Platforms.
Последняя версия: 4.13.4
Дата:jmock-junit4
org.jmock : jmock-junit4Sonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Последняя версия: 2.12.0
Дата:
Последняя версия: 6.11.0
Дата:
Последняя версия: 3.11.1
Дата:
Camel :: Test :: Spring:: JUnit5
org.apache.camel : camel-test-spring-junit5Camel unit testing with Spring and JUnit 5
Последняя версия: 3.11.1
Дата:
Camel :: Testcontainers :: JUnit 5
org.apache.camel : camel-testcontainers-junit5Camel support for testcontainers with JUnit 5
Последняя версия: 3.11.1
Дата:
Arquillian TestRunner TestNG Container
org.jboss.arquillian.testng : arquillian-testng-containerTestNG Container Implementation for the Arquillian Project
Последняя версия: 1.7.0.Alpha10
Дата:
JUnit Platform Engine API
org.junit.platform : junit-platform-engineModule "junit-platform-engine" of JUnit 5.
Последняя версия: 1.8.0-M1
Дата:
Последняя версия: 2.0.9
Дата:
OPS4J Pax Exam - JUnit Support
org.ops4j.pax.exam : pax-exam-junitOPS4J Pax Exam - Integration testing framework for OSGi. Detailed information to be found at http://wiki.ops4j.org/display/ops4j/Pax+Exam.
Последняя версия: 1.2.4
Дата:
Camel :: Testcontainers :: Spring :: JUnit5
org.apache.camel : camel-testcontainers-spring-junit5Camel unit testing with Spring, testcontainers and JUnit 5
Последняя версия: 3.11.1
Дата:
Последняя версия: 1.1.1
Дата:
Последняя версия: 1.2.6
Дата:
OPS4J Pax Exam - JUnit Extender Implementation
org.ops4j.pax.exam : pax-exam-junit-extender-implOPS4J Pax Exam - Integration testing framework for OSGi. Detailed information to be found at http://wiki.ops4j.org/display/ops4j/Pax+Exam.
Последняя версия: 1.2.4
Дата:Последняя версия: 2.25.4
Дата:
JUnit Jupiter Migration Support
org.junit.jupiter : junit-jupiter-migrationsupportModule "junit-jupiter-migrationsupport" of JUnit 5.
Последняя версия: 5.8.0-M1
Дата:
Последняя версия: 2.0.9
Дата:Apache ServiceMix :: Bundles :: junit
org.apache.servicemix.bundles : org.apache.servicemix.bundles.junitThis OSGi bundle wraps junit 4.13.2 jar file.
Последняя версия: 4.13.2_1
Дата:
junit-dataprovider
com.tngtech.java : junit-dataproviderA TestNG like dataprovider runner for JUnit
Последняя версия: 1.13.1
Дата:
Arquillian TestRunner JUnit Core
org.jboss.arquillian.junit : arquillian-junit-coreJUnit Implementation for the Arquillian Project
Последняя версия: 1.7.0.Alpha10
Дата:
Che Plugin :: Java Testing :: JUnit IDE
org.eclipse.che.plugin : che-plugin-testing-junit-ideProvides version of third parties artifacts to use in Codenvy platform projects
Последняя версия: 7.0.0-rc-3.0
Дата:
Che Plugin :: Java Testing :: TestNG IDE
org.eclipse.che.plugin : che-plugin-testing-testng-ideProvides version of third parties artifacts to use in Codenvy platform projects
Последняя версия: 7.0.0-rc-3.0
Дата:JGit - JUnit Utility Classes
org.eclipse.jgit : org.eclipse.jgit.junitUtility classes to support JUnit testing of JGit applications.
Последняя версия: 5.12.0.202106070339-r
Дата:
JUnit Platform Runner
org.junit.platform : junit-platform-runnerModule "junit-platform-runner" of JUnit 5.
Последняя версия: 1.8.0-M1
Дата:
Последняя версия: 2.0.9
Дата:
JUnit Platform Commons
org.junit.platform : junit-platform-commonsModule "junit-platform-commons" of JUnit 5.
Последняя версия: 1.8.0-M1
Дата:
OPS4J Pax Exam Driver TestNG
org.ops4j.pax.exam : pax-exam-testngPax Exam Integration testing framework for Modern Java Platforms.
Последняя версия: 4.13.4
Дата:
Последняя версия: 0.4.8
Дата:
Arquillian TestRunner JUnit Standalone
org.jboss.arquillian.junit : arquillian-junit-standaloneJUnit Standalone Implementation for the Arquillian Project
Последняя версия: 1.7.0.Alpha10
Дата:Issue Keeper JUnit Connector
link.bek.tools : issue-keeper-junitIssue keeper is a tracking tool which makes the tests skipped in advance when they are blocked by the open issues.
Последняя версия: 4.12.5
Дата:
Последняя версия: 2.23.2
Дата:RandomizedTesting JUnit4 Maven Plugin
com.carrotsearch.randomizedtesting : junit4-maven-pluginJUnit test runner and plugins for running JUnit tests with pseudo-randomness.
Последняя версия: 2.7.8
Дата:
weld-junit5
org.jboss.weld : weld-junit5Set of JUnit extensions to enhance the testing of CDI components.
Последняя версия: 3.0.0.Final
Дата:JUnit Platform Maven Plugin
de.sormuras.junit : junit-platform-maven-pluginLaunches the JUnit Platform
Последняя версия: 1.1.4
Дата:
kafka-junit5
com.salesforce.kafka.test : kafka-junit5This library wraps Kafka's embedded test cluster, allowing you to more easily create and run integration tests using JUnit against a "real" kafka server running within the context of your tests.
Последняя версия: 3.2.3
Дата:
JUnit Platform Console
org.junit.platform : junit-platform-consoleModule "junit-platform-console" of JUnit 5.
Последняя версия: 1.8.0-M1
Дата:
Последняя версия: 1.5.30-RC
Дата:
Arquillian TestRunner TestNG Core
org.jboss.arquillian.testng : arquillian-testng-coreTestNG Implementations for the Arquillian Project
Последняя версия: 1.7.0.Alpha10
Дата:
Helidon Microprofile Tests JUnit5
io.helidon.microprofile.tests : helidon-microprofile-tests-junit5Integration with Junit5 to support tests with CDI injection
Последняя версия: 2.3.2
Дата:
Che Plugin :: Java Testing :: JUnit Runtime
org.eclipse.che.plugin : che-plugin-testing-junit-runtimeProvides version of third parties artifacts to use in Codenvy platform projects
Последняя версия: 7.0.0-rc-3.0
Дата:
Che Plugin :: Java Testing :: TestNG Runtime
org.eclipse.che.plugin : che-plugin-testing-testng-runtimeProvides version of third parties artifacts to use in Codenvy platform projects
Последняя версия: 7.0.0-rc-3.0
Дата:
Che Plugin :: Java Testing :: JUnit Server
org.eclipse.che.plugin : che-plugin-testing-junit-serverProvides version of third parties artifacts to use in Codenvy platform projects
Последняя версия: 7.0.0-rc-3.0
Дата:
Che Plugin :: Java Testing :: TestNG Server
org.eclipse.che.plugin : che-plugin-testing-testng-serverProvides version of third parties artifacts to use in Codenvy platform projects
Последняя версия: 7.0.0-rc-3.0
Дата:
Quarkus - Test Framework - JUnit 5 Internal Test Framework
io.quarkus : quarkus-junit5-internalA runner for unit tests, intended for testing Quarkus rather than for end user consumption.
Последняя версия: 2.1.2.Final
Дата:Последняя версия: 1.10.11
Дата:
ActiveMQ :: JUnit Rule
org.apache.activemq.tooling : activemq-junitJUnit Rule for Embedded ActiveMQ Brokers
Последняя версия: 5.16.2
Дата:
OPS4J Pax Exam - JUnit Extender API
org.ops4j.pax.exam : pax-exam-junit-extenderOPS4J Pax Exam - Integration testing framework for OSGi. Detailed information to be found at http://wiki.ops4j.org/display/ops4j/Pax+Exam.
Последняя версия: 1.2.4
Дата:
Cucumber-JVM: JUnit Platform Engine
io.cucumber : cucumber-junit-platform-engineCucumber for the JVM
Последняя версия: 6.11.0
Дата:
Последняя версия: 3.0.0-M5
Дата:ActiveMQ Artemis JUnit Rules
org.apache.activemq : artemis-junitThe Apache Software Foundation provides support for the Apache community of open-source software projects. The Apache projects are characterized by a collaborative, consensus based development process, an open and pragmatic software license, and a desire to create high quality software that leads the way in its field. We consider ourselves not simply a group of projects sharing a server, but rather a community of developers and users.
Последняя версия: 2.18.0
Дата:
Последняя версия: 3.0.0-M5
Дата:JUnitBenchmarks
com.carrotsearch : junit-benchmarksA framework for writing performance micro-benchmarks using JUnit4 annotations.
Последняя версия: 0.7.2
Дата:
Infinispan Server JUnit 4.x Test Driver
org.infinispan : infinispan-server-testdriver-junit4Infinispan Server Test Driver for JUnit 4.x
Последняя версия: 13.0.0.Dev03
Дата:Последняя версия: 1.4.2
Дата:
JUnit-Interface
com.novocode : junit-interfaceAn implementation of sbt's test interface for JUnit 4
Последняя версия: 0.11
Дата:Последняя версия: 3.4.2
Дата:FEST Swing - JUnit 4.5 Extension
org.easytesting : fest-swing-junit-4.5JUnit 4.5-specific extension for FEST-Swing
Последняя версия: 1.2.1
Дата:jMock JUnit 3 Extension
org.jmock : jmock-junit3Sonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Последняя версия: 2.12.0
Дата:
Mockito Groovy Support
com.cyrusinnovation : mockito-groovy-supportA fix to allow you to use Mockito with Groovy
Последняя версия: 1.3
Дата:
Последняя версия: 2.14.0
Дата:Apache Directory JUnit Add-ons
org.apache.directory.junit : junit-addonsCustom build tools used by the Apache Directory project.
Последняя версия: 2.0.1
Дата:
Infinispan Server JUnit 5.x Test Driver
org.infinispan : infinispan-server-testdriver-junit5Infinispan Server Test Driver for JUnit 5.x
Последняя версия: 13.0.0.Dev03
Дата:
Последняя версия: 2.0.9
Дата:
weld-junit4
org.jboss.weld : weld-junit4Set of JUnit extensions to enhance the testing of CDI components.
Последняя версия: 3.0.0.Final
Дата:Последняя версия: 1.4
Дата:
Последняя версия: 2.0.0.0
Дата:mockito-configuration
org.opendaylight.yangtools : mockito-configurationDefault mockito configuration
Последняя версия: 7.0.4
Дата:Apache Sling Testing Sling Mock JUnit 4
org.apache.sling : org.apache.sling.testing.sling-mock.junit4Mock implementation of selected Sling APIs.
Последняя версия: 3.0.2
Дата:Последняя версия: 2.2.0
Дата:JUnit Toolbox
com.googlecode.junit-toolbox : junit-toolboxUseful classes for writing automated tests with JUnit
Последняя версия: 2.4
Дата:
PowerMock
org.powermock : powermock-module-junit4-rule-agentPowerMock support module for JUnit 4.x rules with Java agent
Последняя версия: 2.0.9
Дата:
JUnit Platform Test Kit
org.junit.platform : junit-platform-testkitModule "junit-platform-testkit" of JUnit 5.
Последняя версия: 1.8.0-M1
Дата:Transitional :: JUnit 4 stub
io.syndesis.transitional : junit4-stubStub used instead of JUnit 4 dependency. These classes are used only so that the class hiearchy can be maintained. Functionality of these classes is not used, that's why they're empty, but they're needed to successfuly compile 3rd party dependencies without introducing junit:junit (JUnit 4) dependency. For one such case see: https://github.com/testcontainers/testcontainers-java/issues/970#issuecomment-625044008
Последняя версия: 1.12.1
Дата:
JUnit Platform Suite API
org.junit.platform : junit-platform-suite-apiModule "junit-platform-suite-api" of JUnit 5.
Последняя версия: 1.8.0-M1
Дата:Последняя версия: 0.259.1
Дата:
Последняя версия: 1.5.30-RC
Дата:
Последняя версия: 6.11.0
Дата:JGit - JUnit Http Utility Classes
org.eclipse.jgit : org.eclipse.jgit.junit.httpUtility classes to support Http based JUnit testing of JGit applications.
Последняя версия: 5.12.0.202106070339-r
Дата:
docker-compose-rule-junit4
com.palantir.docker.compose : docker-compose-rule-junit4Palantir open source project
Последняя версия: 1.7.0
Дата:
Последняя версия: 350
Дата:OPS4J Pax Tipi - junit
org.ops4j.pax.tipi : org.ops4j.pax.tipi.junitThis OSGi bundle wraps junit-4.12
Последняя версия: 4.12.0.1
Дата:
bootique-junit5: unit/integration test framework for Bootique apps
io.bootique : bootique-junit5Provides a test framework on top of Bootique.
Последняя версия: 2.0.M1
Дата:
org-netbeans-libs-junit4
org.netbeans.api : org-netbeans-libs-junit4Apache NetBeans is an integrated development environment, tooling platform, and application framework.
Последняя версия: RELEASE124
Дата:
Последняя версия: 3.6.2
Дата:
Последняя версия: 3.6.2
Дата:Последняя версия: 1.6.0
Дата:
docker-proxy-rule-junit4
com.palantir.docker.proxy : docker-proxy-rule-junit4Palantir open source project
Последняя версия: 1.2.0
Дата:JGit - JUnit Ssh Utility Classes
org.eclipse.jgit : org.eclipse.jgit.junit.sshUtility classes to support Ssh based JUnit testing of JGit applications.
Последняя версия: 5.12.0.202106070339-r
Дата:Последняя версия: 1.3.1
Дата:
Последняя версия: 5.3.5
Дата:
JUnit Platform Surefire Provider
org.junit.platform : junit-platform-surefire-providerModule "junit-platform-surefire-provider" of JUnit 5.
Последняя версия: 1.3.2
Дата:
Последняя версия: 1.2.7
Дата:
Ajocado JUnit Integration
org.jboss.arquillian.ajocado : arquillian-ajocado-junitStarting point for integration Ajocado to JUnit test suites
Последняя версия: 1.0.0.CR2
Дата:
Последняя версия: 5.3.5
Дата:
Последняя версия: 2.9.0
Дата:
Последняя версия: 4.0.15-alpha
Дата:RandomizedTesting JUnit4 ANT Task
com.carrotsearch.randomizedtesting : junit4-antJUnit test runner and plugins for running JUnit tests with pseudo-randomness.
Последняя версия: 2.7.8
Дата:
Последняя версия: 1.5.30-RC
Дата:MyFaces Extensions-CDI JUnit-Support Module
org.apache.myfaces.extensions.cdi.test : myfaces-extcdi-junit-support-moduleThe MyFaces project is home of the first free open source JavaServer Faces implementation as well as some useful JSF component libraries and other convenient JSF stuff.
Последняя версия: 1.0.6
Дата:
Последняя версия: 4.0.16-alpha
Дата:
Последняя версия: 2.5.26
Дата:
bootique-jdbc-junit5-derby: JUnit5 helper classes for unit tests using in-memory Derby DB
io.bootique.jdbc : bootique-jdbc-junit5-derbyProvides JUnit5-based helper classes for unit tests using in-memory Derby DB
Последняя версия: 2.0.M1
Дата:Последняя версия: 4.7-201002261215
Дата:
PowerMock
org.powermock : powermock-module-testng-commonPowerMock module for TestNG. Common classes
Последняя версия: 2.0.9
Дата:
FluentLenium JUnit Jupiter
org.fluentlenium : fluentlenium-junit-jupiterJUnit 5.x Adapter for FluentLenium
Последняя версия: 4.8.0
Дата:
SureFire JUnitCore Runner
org.apache.maven.surefire : surefire-junit47SureFire JUnitCore (JUnit 4.7+) Runner
Последняя версия: 3.0.0-M5
Дата:
Scope Rule for JUnit4
com.undefinedlabs.scope : scope-rule-junit4Scope is a APM for tests to give engineering teams unprecedented visibility into their CI process to quickly identify, troubleshoot and fix failed builds. This artifact contains the classes to instrument the JUnit4 tests.
Последняя версия: 0.15.1-beta.2
Дата:junit-servers-jetty
com.github.mjeanroy : junit-servers-jettyAdd Jetty Embedded Server to your junit tests case.
Последняя версия: 2.0.0
Дата:
Последняя версия: 2.9.9
Дата:
BlockHound JUnit Platform Integration
io.projectreactor.tools : blockhound-junit-platformIntegrates the BlockHound Java agent to detect blocking calls in JUnit Platform-based tests.
Последняя версия: 1.0.6.RELEASE
Дата:
Apache Geode
org.apache.geode : geode-junitApache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high concurrency processing
Последняя версия: 1.13.4
Дата:
Scope Rule for JUnit5
com.undefinedlabs.scope : scope-rule-junit5Scope is a APM for tests to give engineering teams unprecedented visibility into their CI process to quickly identify, troubleshoot and fix failed builds. This artifact contains the classes to instrument the JUnit5 tests.
Последняя версия: 0.15.1-beta.2
Дата:
Scope Runner for JUnit5
com.undefinedlabs.scope : scope-runner-junit5Scope is a APM for tests to give engineering teams unprecedented visibility into their CI process to quickly identify, troubleshoot and fix failed builds. This artifact contains the classes to instrument the JUnit5 runner.
Последняя версия: 0.15.1-beta.2
Дата:
PowerMock
org.powermock : powermock-module-junit4-rulePowerMock support module for JUnit 4.x rules.
Последняя версия: 2.0.9
Дата:
Scope Runner for JUnit4
com.undefinedlabs.scope : scope-runner-junit4Scope is a APM for tests to give engineering teams unprecedented visibility into their CI process to quickly identify, troubleshoot and fix failed builds. This artifact contains the classes to instrument the JUnit4 runner.
Последняя версия: 0.15.1-beta.2
Дата:
Scope Rule for TestNG
com.undefinedlabs.scope : scope-rule-testngScope is a APM for tests to give engineering teams unprecedented visibility into their CI process to quickly identify, troubleshoot and fix failed builds. This artifact contains the classes to instrument the TestNG tests.
Последняя версия: 0.15.1-beta.2
Дата:
Scope Runner for JUnit4 PowerMock
com.undefinedlabs.scope : scope-runner-junit4-powermockScope is a APM for tests to give engineering teams unprecedented visibility into their CI process to quickly identify, troubleshoot and fix failed builds. This artifact contains the classes to instrument the PowerMock runner for JUnit4.
Последняя версия: 0.15.1-beta.2
Дата:
Последняя версия: 2.5.26
Дата:
Scope Runner for TestNG
com.undefinedlabs.scope : scope-runner-testngScope is a APM for tests to give engineering teams unprecedented visibility into their CI process to quickly identify, troubleshoot and fix failed builds. This artifact contains the classes to instrument the TestNG runner.
Последняя версия: 0.15.1-beta.2
Дата:
JUnit 3/4 SuiteConfiguration Test Runner
org.sonatype.http-testing-harness : junit-runner${project.name}
Последняя версия: 0.11
Дата:
Последняя версия: 0.0.1
Дата:
PowerMock
org.powermock : powermock-classloading-xstreamPerforms classloader deep-cloning using X-Stream.
Последняя версия: 2.0.9
Дата:JUnit Extensions
io.github.glytching : junit-extensionsJUnit Jupiter extensions, providing 'JUnit5 replacements' for some common JUnit4 Rules.
Последняя версия: 2.4.0
Дата:
Arquillian Cube Docker JUnit Rule
org.arquillian.cube : arquillian-cube-docker-junit-ruleArquillian Cube Extension to integrate Arquillian to Docker
Последняя версия: 1.18.2
Дата:junit-quickcheck-generators
com.pholser : junit-quickcheck-generatorsProperty-based testing, JUnit-style: basic generators
Последняя версия: 1.0
Дата:
Quarkus - Test Framework - JUnit 5
io.quarkus : quarkus-junit5Build parent to bring in required dependencies
Последняя версия: 2.1.2.Final
Дата:Последняя версия: 4.1.0
Дата:Последняя версия: 2.0.0-alpha-1
Дата:Последняя версия: 4.6.1
Дата:Последняя версия: 2.0.0-alpha-1
Дата:Apache Sling Testing OSGi Mock JUnit 5
org.apache.sling : org.apache.sling.testing.osgi-mock.junit5Mock implementation of selected OSGi APIs.
Последняя версия: 3.1.2
Дата:
Последняя версия: 2.14.0
Дата:Vert.x JUnit 5 support :: Core
io.vertx : vertx-junit5Sonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Последняя версия: 4.1.2
Дата:
Последняя версия: 1.0.0
Дата:
Allure TestNG Adaptor
ru.yandex.qatools.allure : allure-testng-adaptorSonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Последняя версия: 1.5.4
Дата:
bootique-jetty-junit5: JUnit 5 utilities to start Jetty on a dynamic port
io.bootique.jetty : bootique-jetty-junit5JUnit 5 utilities to start Jetty on a dynamically determined port and provide a client that can be used by the tests
Последняя версия: 2.0.M1
Дата:
jqassistant.plugin.junit
com.buschmais.jqassistant.plugin : jqassistant.plugin.junitFramework for structural analysis of Java applications.
Последняя версия: 1.1.4
Дата:Последняя версия: 6.1.0
Дата:junit-quickcheck-core
com.pholser : junit-quickcheck-coreProperty-based testing, JUnit-style: core functionality
Последняя версия: 1.0
Дата:
Последняя версия: 2.14.0
Дата:Последняя версия: 4.12.4-js-ec
Дата:Последняя версия: 4.10.6
Дата:
Allure jUnit Adaptor
ru.yandex.qatools.allure : allure-junit-adaptorSonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Последняя версия: 1.5.4
Дата:MockServer JUnit Jupiter Integration
org.mock-server : mockserver-junit-jupiterA JUnit5 Extension for MockServer
Последняя версия: 5.11.2
Дата:Junit4OSGi Maven Plugin
org.apache.felix : maven-junit4osgi-pluginApache Felix is an OSGi implementation.
Последняя версия: 1.0.0
Дата:
Arquillian Cube Docker JUnit 5
org.arquillian.cube : arquillian-cube-docker-junit5Arquillian Cube Extension to integrate Arquillian to Docker
Последняя версия: 1.18.2
Дата:
Betamax
software.betamax : betamax-junitBetamax is a tool for mocking external HTTP resources such as web services and REST APIs in your tests.
Последняя версия: 2.0.1
Дата:Junit4Osgi
org.apache.felix : org.apache.felix.ipojo.junit4osgiApache Felix is an OSGi implementation.
Последняя версия: 1.0.0
Дата:Последняя версия: 2.1.25
Дата:Apache Sling JUnit Core
org.apache.sling : org.apache.sling.junit.coreRuns JUnit tests in an OSGi framework and provides the JUnit libraries
Последняя версия: 1.1.6
Дата:Последняя версия: 1.2.59
Дата:Apache Sling Testing OSGi Mock JUnit 4
org.apache.sling : org.apache.sling.testing.osgi-mock.junit4Mock implementation of selected OSGi APIs.
Последняя версия: 3.1.2
Дата:
Последняя версия: 0.2.2
Дата:
JUnit Platform Reporting
org.junit.platform : junit-platform-reportingModule "junit-platform-reporting" of JUnit 5.
Последняя версия: 1.8.0-M1
Дата:maven-junithelper-plugin Maven Mojo
org.junithelper : maven-junithelper-pluginSonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Последняя версия: 1.12
Дата:
bootique-cayenne42-junit5: JUnit 5-based helper classes for unit tests with Cayenne stack
io.bootique.cayenne : bootique-cayenne42-junit5Provides JUnit 5 based helper classes for unit tests with Cayenne stack
Последняя версия: 2.0.M1
Дата:
pact-jvm-provider-junit
au.com.dius : pact-jvm-provider-junit# Pact junit runner ## Overview Library provides ability to play contract tests against a provider service in JUnit fashionable way. Supports: - Out-of-the-box convenient ways to load pacts - Easy way to change assertion strategy - **org.junit.BeforeClass**, **org.junit.AfterClass** and **org.junit.ClassRule** JUnit annotations, that will be run once - before/after whole contract test suite. - **org.junit.Before**, **org.junit.After** and **org.junit.Rule** JUnit annotations, that will be run before/after each test of an interaction. - **au.com.dius.pact.provider.junit.State** custom annotation - before each interaction that requires a state change, all methods annotated by `@State` with appropriate the state listed will be invoked. These methods must either take no parameters or a single Map parameter. ## Example of HTTP test ```java @RunWith(PactRunner.class) // Say JUnit to run tests with custom Runner @Provider("myAwesomeService") // Set up name of tested provider @PactFolder("pacts") // Point where to find pacts (See also section Pacts source in documentation) public class ContractTest { // NOTE: this is just an example of embedded service that listens to requests, you should start here real service @ClassRule //Rule will be applied once: before/after whole contract test suite public static final ClientDriverRule embeddedService = new ClientDriverRule(8332); @BeforeClass //Method will be run once: before whole contract test suite public static void setUpService() { //Run DB, create schema //Run service //... } @Before //Method will be run before each test of interaction public void before() { // Rest data // Mock dependent service responses // ... embeddedService.addExpectation( onRequestTo("/data"), giveEmptyResponse() ); } @State("default", "no-data") // Method will be run before testing interactions that require "default" or "no-data" state public void toDefaultState() { // Prepare service before interaction that require "default" state // ... System.out.println("Now service in default state"); } @State("with-data") // Method will be run before testing interactions that require "with-data" state public void toStateWithData(Map data) { // Prepare service before interaction that require "with-data" state. The provider state data will be passed // in the data parameter // ... System.out.println("Now service in state using data " + data); } @TestTarget // Annotation denotes Target that will be used for tests public final Target target = new HttpTarget(8332); // Out-of-the-box implementation of Target (for more information take a look at Test Target section) } ``` ## Example of AMQP Message test ```java @RunWith(PactRunner.class) // Say JUnit to run tests with custom Runner @Provider("myAwesomeService") // Set up name of tested provider @PactBroker(host="pactbroker", port = "80") public class ConfirmationKafkaContractTest { @TestTarget // Annotation denotes Target that will be used for tests public final Target target = new AmqpTarget(); // Out-of-the-box implementation of Target (for more information take a look at Test Target section) @BeforeClass //Method will be run once: before whole contract test suite public static void setUpService() { //Run DB, create schema //Run service //... } @Before //Method will be run before each test of interaction public void before() { // Message data preparation // ... } @PactVerifyProvider('an order confirmation message') String verifyMessageForOrder() { Order order = new Order() order.setId(10000004) order.setPrice(BigDecimal.TEN) order.setUnits(15) def message = new ConfirmationKafkaMessageBuilder() .withOrder(order) .build() JsonOutput.toJson(message) } } ``` ## Provider state callback methods For the provider states in the pact being verified, you can define methods to be invoked to setup the correct state for each interaction. Just annotate a method with the `au.com.dius.pact.provider.junit.State` annotation and the method will be invoked before the interaction is verified. For example: ```java @State("SomeProviderState") // Must match the state description in the pact file public void someProviderState() { // Do what you need to set the correct state } ``` If there are parameters in the pact file, just add a Map parameter to the method to be able to access those parameters. ```java @State("SomeProviderState") public void someProviderState(Map<String, Object> providerStateParameters) { // Do what you need to set the correct state } ``` ### Provider state teardown methods If you need to tear down your provider state, you can annotate a method with the `@State` annotation with the action set to `StateChangeAction.TEARDOWN` and it will be invoked after the interaction is verified. ```java @State("SomeProviderState", action = StateChangeAction.TEARDOWN) public void someProviderStateCleanup() { // Do what you need to to teardown the state } ``` #### Returning values that can be injected You can have values from the provider state callbacks be injected into most places (paths, query parameters, headers, bodies, etc.). This works by using the V3 spec generators with provider state callbacks that return values. One example of where this would be useful is API calls that require an ID which would be auto-generated by the database on the provider side, so there is no way to know what the ID would be beforehand. There are methods on the consumer DSLs that can provider an expression that contains variables (like '/api/user/au.com.dius:pact-jvm-provider-junit:jar:4.0.10' for the path). The provider state callback can then return a map for values, and the `id` attribute from the map will be expanded in the expression. For this to work, just make your provider state method return a Map of the values. ### Using multiple classes for the state change methods If you have a large number of state change methods, you can split things up by moving them to other classes. There are two ways you can do this: #### Use interfaces You can put the state change methods on interfaces and then have your test class implement those interfaces. See [StateAnnotationsOnInterfaceTest](src/test/java/au/com/dius/pact/provider/junit/StateAnnotationsOnInterfaceTest.java) for an example. #### Specify the additional classes on the test target You can provide the additional classes to the test target with the `withStateHandler` or `setStateHandlers` methods. See [BooksPactProviderTest](pact-jvm-provider-spring/src/test/java/au/com/dius/pact/provider/spring/BooksPactProviderTest.java) for an example. ## Pact source The Pact runner will automatically collect pacts based on annotations on the test class. For this purpose there are 3 out-of-the-box options (files from a directory, files from a set of URLs or a pact broker) or you can easily add your own Pact source. If you need to load a single pact file from the file system, use the `PactUrl` with the URL set to the file path. **Note:** You can only define one source of pacts per test class. ### Download pacts from a pact-broker To use pacts from a Pact Broker, annotate the test class with `@PactBroker(host="host.of.pact.broker.com", port = "80")`. You can also specify the protocol, which defaults to "http". The pact broker will be queried for all pacts with the same name as the provider annotation. For example, test all pacts for the "Activity Service" in the pact broker: ```java @RunWith(PactRunner.class) @Provider("Activity Service") @PactBroker(host = "localhost", port = "80") public class PactJUnitTest { @TestTarget public final Target target = new HttpTarget(5050); } ``` #### Using Java System properties The pact broker loader was updated to allow system properties to be used for the hostname, port or protocol. The port was changed to a string to allow expressions to be set. To use a system property or environment variable, you can place the property name in `${}` expression de-markers: ```java @PactBroker(host="${pactbroker.hostname}", port = "80") ``` You can provide a default value by separating the property name with a colon (`:`): ```java @PactBroker(host="${pactbroker.hostname:localhost}", port = "80") ``` #### More Java System properties The default values of the `@PactBroker` annotation now enable variable interpolation. The following keys may be managed through the environment * `pactbroker.host` * `pactbroker.port` * `pactbroker.scheme` * `pactbroker.tags` (comma separated) * `pactbroker.auth.username` (for basic auth) * `pactbroker.auth.password` (for basic auth) * `pactbroker.auth.token` (for bearer auth) * `pactbroker.consumers` (comma separated list to filter pacts by consumer; if not provided, will fetch all pacts for the provider) #### Using tags with the pact broker The pact broker allows different versions to be tagged. To load all the pacts: ```java @PactBroker(host="pactbroker", port = "80", tags = {"latest", "dev", "prod"}) ``` The default value for tags is `latest` which is not actually a tag but instead corresponds to the latest version ignoring the tags. If there are multiple consumers matching the name specified in the provider annotation then the latest pact for each of the consumers is loaded. For any other value the latest pact tagged with the specified tag is loaded. Specifying multiple tags is an OR operation. For example if you specify `tags = {"dev", "prod"}` then both the latest pact file tagged with `dev` and the latest pact file taggged with `prod` is loaded. #### Using authentication with the with the pact broker You can use basic authentication with the `@PactBroker` annotation by setting the `authentication` value to a `@PactBrokerAuth` annotation. For example: ```java @PactBroker(host = "${pactbroker.url:localhost}", port = "1234", tags = {"latest", "prod", "dev"}, authentication = @PactBrokerAuth(username = "test", password = "test")) ``` Bearer tokens are also supported. For example: ```java @PactBroker(host = "${pactbroker.url:localhost}", port = "1234", tags = {"latest", "prod", "dev"}, authentication = @PactBrokerAuth(token = "test")) ``` The `token`, `username` and `password` values also take Java system property expressions. Preemptive Authentication can be enabled by setting the `pact.pactbroker.httpclient.usePreemptiveAuthentication` Java system property to `true`. ### Allowing just the changed pact specified in a webhook to be verified [4.0.6+] When a consumer publishes a new version of a pact file, the Pact broker can fire off a webhook with the URL of the changed pact file. To allow only the changed pact file to be verified, you can override the URL by adding the annotation `@AllowOverridePactUrl` to your test class and then setting using the `pact.filter.consumers` and `pact.filter.pacturl` values as either Java system properties or environment variables. If you have annotated your test class with `@Consumer` you don't need to provide `pact.filter.consumers`. ### Pact Url To use pacts from urls annotate the test class with ```java @PactUrl(urls = {"http://build.server/zoo_app-animal_service.json"} ) ``` If you need to load a single pact file from the file system, you can use the `PactUrl` with the URL set to the file path. ### Pact folder To use pacts from a resource folder of the project annotate test class with ```java @PactFolder("subfolder/in/resource/directory") ``` ### Custom pacts source It's possible to use a custom Pact source. For this, implement interface `au.com.dius.pact.provider.junit.loader.PactLoader` and annotate the test class with `@PactSource(MyOwnPactLoader.class)`. **Note:** class `MyOwnPactLoader` must have a default empty constructor or a constructor with one argument of class `Class` which at runtime will be the test class so you can get custom annotations of test class. ### Filtering the interactions that are verified By default, the pact runner will verify all pacts for the given provider. You can filter the pacts and interactions by the following methods. #### Filtering by Consumer You can run only those pacts for a particular consumer by adding a `@Consumer` annotation to the test class. For example: ```java @RunWith(PactRunner.class) @Provider("Activity Service") @Consumer("Activity Consumer") @PactBroker(host = "localhost", port = "80") public class PactJUnitTest { @TestTarget public final Target target = new HttpTarget(5050); } ``` #### Interaction Filtering You can filter the interactions that are executed by adding a `@PactFilter` annotation to your test class. The pact filter annotation will then only verify interactions that have a matching value, by default provider state. You can provide multiple values to match with. The filter criteria is defined by the filter property. The filter must implement the `au.com.dius.pact.provider.junit.filter.InteractionFilter` interface. Also check the `InteractionFilter` interface for default filter implementations. For example: ```java @RunWith(PactRunner.class) @PactFilter("Activity 100 exists in the database") public class PactJUnitTest { } ``` You can also use regular expressions with the filter. For example: ```java @RunWith(PactRunner.class) @PactFilter(values = {"^\\/somepath.*"}, filter = InteractionFilter.ByRequestPath.class) public class PactJUnitTest { } ``` ### Setting the test to not fail when no pacts are found By default the pact runner will fail the verification test if no pact files are found to verify. To change the failure into a warning, add a `@IgnoreNoPactsToVerify` annotation to your test class. #### Ignoring IO errors loading pact files You can also set the test to ignore any IO and parser exceptions when loading the pact files by setting the `ignoreIoErrors` attribute on the annotation to `"true"` or setting the JVM system property `pact.verification.ignoreIoErrors` to `true`. ** WARNING! Do not enable this on your CI server, as this could result in your build passing with no providers having been verified due to a configuration error. ** ## Test target The field in test class of type `au.com.dius.pact.provider.junit.target.Target` annotated with `au.com.dius.pact.provider.junit.target.TestTarget` will be used for actual Interaction execution and asserting of contract. **Note:** there must be exactly 1 such field, otherwise an `InitializationException` will be thrown. ### HttpTarget `au.com.dius.pact.provider.junit.target.HttpTarget` - out-of-the-box implementation of `au.com.dius.pact.provider.junit.target.Target` that will play pacts as http request and assert response from service by matching rules from pact. You can also specify the protocol, defaults to "http". ### AmqpTarget `au.com.dius.pact.provider.junit.target.AmqpTarget` - out-of-the-box implementation of `au.com.dius.pact.provider.junit.target.Target` that will play pacts as an AMQP message and assert response from service by matching rules from pact. **Note for Maven users:** If you use Maven to run your tests, you will have to make sure that the Maven Surefire plugin is at least version 2.22.1 uses an isolated classpath. For example, configure it by adding the following to your POM: ```xml <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.22.1</version> <configuration> <useSystemClassLoader>false</useSystemClassLoader> </configuration> </plugin> ``` #### Modifying the requests before they are sent Sometimes you may need to add things to the requests that can't be persisted in a pact file. Examples of these would be authentication tokens, which have a small life span. The HttpTarget supports request filters by annotating methods on the test class with `@TargetRequestFilter`. These methods must be public void methods that take a single HttpRequest parameter. For example: ```java @TargetRequestFilter public void exampleRequestFilter(HttpRequest request) { request.addHeader("Authorization", "OAUTH hdsagasjhgdjashgdah..."); } ``` __*Important Note:*__ You should only use this feature for things that can not be persisted in the pact file. By modifying the request, you are potentially modifying the contract from the consumer tests! #### Turning off URL decoding of the paths in the pact file By default the paths loaded from the pact file will be decoded before the request is sent to the provider. To turn this behaviour off, set the system property `pact.verifier.disableUrlPathDecoding` to `true`. __*Important Note:*__ If you turn off the url path decoding, you need to ensure that the paths in the pact files are correctly encoded. The verifier will not be able to make a request with an invalid encoded path. ### Custom Test Target It's possible to use custom `Target`, for that interface `Target` should be implemented and this class can be used instead of `HttpTarget`. # Verification Reports The default test behaviour is to display the verification being done to the console, and pass or fail the test via the normal JUnit mechanism. Additional reports can be generated from the tests. ## Enabling additional reports via annotations on the test classes A `@VerificationReports` annotation can be added to any pact test class which will control the verification output. The annotation takes a list report types and an optional report directory (defaults to "target/pact/reports"). The currently supported report types are `console`, `markdown` and `json`. For example: ```java @VerificationReports({"console", "markdown"}) public class MyPactTest { ``` will enable the markdown report in addition to the normal console output. And, ```java @VerificationReports(value = {"markdown"}, reportDir = "/myreports") public class MyPactTest { ``` will disable the normal console output and write the markdown reports to "/myreports". ## Enabling additional reports via Java system properties or environment variables The additional reports can also be enabled with Java System properties or environment variables. The following two properties have been introduced: `pact.verification.reports` and `pact.verification.reportDir`. `pact.verification.reports` is the comma separated list of report types to enable (e.g. `console,json,markdown`). `pact.verification.reportDir` is the directory to write reports to (defaults to "target/pact/reports"). ## Additional Reports The following report types are available in addition to console output (`console`, which is enabled by default): `markdown`, `json`. You can also provide a fully qualified classname as report so custom reports are also supported. This class must implement `au.com.dius.pact.provider.reporters.VerifierReporter` interface in order to be correct custom implementation of a report. # Publishing verification results to a Pact Broker For pacts that are loaded from a Pact Broker, the results of running the verification can be published back to the broker against the URL for the pact. You will be able to see the result on the Pact Broker home screen. You need to set the version of the provider that is verified using the `pact.provider.version` system property. To enable publishing of results, set the Java system property or environment variable `pact.verifier.publishResults` to `true`. ## Tagging the provider before verification results are published [4.0.1+] You can have a tag pushed against the provider version before the verification results are published. To do this you need set the `pact.provider.tag` JVM system property to the tag value.
Последняя версия: 4.0.10
Дата:junit-servers-tomcat
com.github.mjeanroy : junit-servers-tomcatAdd Tomcat Embedded Server to your junit tests case.
Последняя версия: 2.0.0
Дата:
Последняя версия: 3.2.0.0-M2
Дата:
Последняя версия: 4.8.0
Дата:Последняя версия: 5.11.2
Дата:
Последняя версия: 1.2.6
Дата:JUnit Hierarchical Context Runner
de.bechte.junit : junit-hierarchicalcontextrunnerThis is a runner implementation that supports context hierarchies in JUnit. For more details please visit: https://github.com/bechte/junit-hierarchicalcontextrunner/wiki
Последняя версия: 4.12.2
Дата:Providence Utils : Testing / Junit 4
net.morimekta.providence : providence-testing-junit4Helper libraries for testing and comparing providence structures using junit 4.12.
Последняя версия: 2.7.0
Дата:
org-netbeans-modules-nbjunit
org.netbeans.api : org-netbeans-modules-nbjunitApache NetBeans is an integrated development environment, tooling platform, and application framework.
Последняя версия: RELEASE124
Дата:
Последняя версия: 2.0.9
Дата:Последняя версия: 20040902.070920
Дата:Последняя версия: 1.4.ga
Дата:
Последняя версия: 1.1.12
Дата:
Burst JUnit 4 Integration
com.squareup.burst : burst-junit4Burst is a unit testing library for varying test data.
Последняя версия: 1.2.0
Дата:Последняя версия: 1.2.1
Дата:
Последняя версия: 1.2.0
Дата:core
com.github.skjolber.mockito-rest-spring : coreREST web-service mocking utility for Spring using JUnit and Mockito
Последняя версия: 1.0.3
Дата:
Последняя версия: 3.0.2
Дата:
Последняя версия: 1.2.0
Дата: