Download JAR files tagged by junit4 with all dependencies
junit-benchmarks from group org.scijava (version 0.7.4-scijava)
A framework for writing performance micro-benchmarks using JUnit4 annotations, forked from https://github.com/carrotsearch/junit-benchmarks.
2 downloads
Artifact junit-benchmarks
Group org.scijava
Version 0.7.4-scijava
Last update 22. August 2016
Organization SciJava
URL https://github.com/scijava/junit-benchmarks
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.scijava
Version 0.7.4-scijava
Last update 22. August 2016
Organization SciJava
URL https://github.com/scijava/junit-benchmarks
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
scope-runner-junit4 from group com.undefinedlabs.scope (version 0.15.1-beta.2)
Scope 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.
Group: com.undefinedlabs.scope Artifact: scope-runner-junit4
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact scope-runner-junit4
Group com.undefinedlabs.scope
Version 0.15.1-beta.2
Last update 24. June 2020
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies scope-rule-junit4, scope-runner-core,
There are maybe transitive dependencies!
Group com.undefinedlabs.scope
Version 0.15.1-beta.2
Last update 24. June 2020
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies scope-rule-junit4, scope-runner-core,
There are maybe transitive dependencies!
scope-runner-junit4-powermock from group com.undefinedlabs.scope (version 0.15.1-beta.2)
Scope 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.
Group: com.undefinedlabs.scope Artifact: scope-runner-junit4-powermock
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact scope-runner-junit4-powermock
Group com.undefinedlabs.scope
Version 0.15.1-beta.2
Last update 24. June 2020
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies scope-rule-junit4, scope-runner-core,
There are maybe transitive dependencies!
Group com.undefinedlabs.scope
Version 0.15.1-beta.2
Last update 24. June 2020
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies scope-rule-junit4, scope-runner-core,
There are maybe transitive dependencies!
scope-rule-junit4 from group com.undefinedlabs.scope (version 0.15.1-beta.2)
Scope 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.
Group: com.undefinedlabs.scope Artifact: scope-rule-junit4
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact scope-rule-junit4
Group com.undefinedlabs.scope
Version 0.15.1-beta.2
Last update 24. June 2020
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group com.undefinedlabs.scope
Version 0.15.1-beta.2
Last update 24. June 2020
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
allure-core-module from group com.capgemini.ntc (version 4.12.0.6)
Allure Test Framework Core is responsible for:
* Test report with logs and/or screenshots
* Test groups/tags
* Data Driven (inside test case, external file)
* Test case parallel execution
* BDD - Gherkin – Cucumber approach
* Run on independent OperatingSystem
* Externalize test environment (DEV, QA, PROD)
Based on Junit4.12
Group: com.capgemini.ntc Artifact: allure-core-module
Show all versions Show documentation Show source
Show all versions Show documentation Show source
1 downloads
Artifact allure-core-module
Group com.capgemini.ntc
Version 4.12.0.6
Last update 19. April 2018
Organization Capgemini - Nearshore Test Center - Poland
URL https://github.com/devonfw/devonfw-testing
License The Apache License, Version 2.0
Dependencies amount 18
Dependencies google-analytics-java, commons-csv, junit, JUnitParams, junit-platform-surefire-provider, mockito-core, log4j-api, log4j-core, slf4j-log4j12, allure-junit-adaptor, allure-report-data, allure-maven-plugin, allure-cucumber-jvm-adaptor, aspectjweaver, junit-toolbox, json, guice, jasypt,
There are maybe transitive dependencies!
Group com.capgemini.ntc
Version 4.12.0.6
Last update 19. April 2018
Organization Capgemini - Nearshore Test Center - Poland
URL https://github.com/devonfw/devonfw-testing
License The Apache License, Version 2.0
Dependencies amount 18
Dependencies google-analytics-java, commons-csv, junit, JUnitParams, junit-platform-surefire-provider, mockito-core, log4j-api, log4j-core, slf4j-log4j12, allure-junit-adaptor, allure-report-data, allure-maven-plugin, allure-cucumber-jvm-adaptor, aspectjweaver, junit-toolbox, json, guice, jasypt,
There are maybe transitive dependencies!
pact-jvm-provider-spring from group au.com.dius (version 4.0.10)
# Pact Spring/JUnit runner
## Overview
Library provides ability to play contract tests against a provider using Spring & JUnit.
This library is based on and references the JUnit package, so see the [Pact JUnit 4](../pact-jvm-provider-junit) or [Pact JUnit 5](../pact-jvm-provider-junit5) providers for more details regarding configuration using JUnit.
Supports:
- Standard ways to load pacts from folders and broker
- Easy way to change assertion strategy
- Spring Test MockMVC Controllers and ControllerAdvice using MockMvc standalone setup.
- MockMvc debugger output
- Multiple @State runs to test a particular Provider State multiple times
- **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.
**NOTE:** For publishing provider verification results to a pact broker, make sure the Java system property `pact.provider.version`
is set with the version of your provider.
## Example of MockMvc test
```java
@RunWith(RestPactRunner.class) // Custom pact runner, child of PactRunner which runs only REST tests
@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 {
//Create an instance of your controller. We cannot autowire this as we're not using (and don't want to use) a Spring test runner.
@InjectMocks
private AwesomeController awesomeController = new AwesomeController();
//Mock your service logic class. We'll use this to create scenarios for respective provider states.
@Mock
private AwesomeBusinessLogic awesomeBusinessLogic;
//Create an instance of your controller advice (if you have one). This will be passed to the MockMvcTarget constructor to be wired up with MockMvc.
@InjectMocks
private AwesomeControllerAdvice awesomeControllerAdvice = new AwesomeControllerAdvice();
//Create a new instance of the MockMvcTarget and annotate it as the TestTarget for PactRunner
@TestTarget
public final MockMvcTarget target = new MockMvcTarget();
@Before //Method will be run before each test of interaction
public void before() {
//initialize your mocks using your mocking framework
MockitoAnnotations.initMocks(this);
//configure the MockMvcTarget with your controller and controller advice
target.setControllers(awesomeController);
target.setControllerAdvice(awesomeControllerAdvice);
}
@State("default", "no-data") // Method will be run before testing interactions that require "default" or "no-data" state
public void toDefaultState() {
target.setRunTimes(3); //let's loop through this state a few times for a 3 data variants
when(awesomeBusinessLogic.getById(any(UUID.class)))
.thenReturn(myTestHelper.generateRandomReturnData(UUID.randomUUID(), ExampleEnum.ONE))
.thenReturn(myTestHelper.generateRandomReturnData(UUID.randomUUID(), ExampleEnum.TWO))
.thenReturn(myTestHelper.generateRandomReturnData(UUID.randomUUID(), ExampleEnum.THREE));
}
@State("error-case")
public void SingleUploadExistsState_Success() {
target.setRunTimes(1); //tell the runner to only loop one time for this state
//you might want to throw exceptions to be picked off by your controller advice
when(awesomeBusinessLogic.getById(any(UUID.class)))
.then(i -> { throw new NotCoolException(i.getArgumentAt(0, UUID.class).toString()); });
}
}
```
## Using Spring runners
You can use `SpringRestPactRunner` or `SpringMessagePactRunner` instead of the default Pact runner to use the Spring test annotations. This will
allow you to inject or mock spring beans. `SpringRestPactRunner` is for restful webapps and `SpringMessagePactRunner` is
for async message tests.
For example:
```java
@RunWith(SpringRestPactRunner.class)
@Provider("pricing")
@PactBroker(protocol = "https", host = "${pactBrokerHost}", port = "443",
authentication = @PactBrokerAuth(username = "${pactBrokerUser}", password = "${pactBrokerPassword}"))
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.DEFINED_PORT)
public class PricingServiceProviderPactTest {
@MockBean
private ProductClient productClient; // This will replace the bean with a mock in the application context
@TestTarget
@SuppressWarnings(value = "VisibilityModifier")
public final Target target = new HttpTarget(8091);
@State("Product X010000021 exists")
public void setupProductX010000021() throws IOException {
reset(productClient);
ProductBuilder product = new ProductBuilder()
.withProductCode("X010000021");
when(productClient.fetch((Set<String>) argThat(contains("X010000021")), any())).thenReturn(product);
}
@State("the product code X00001 can be priced")
public void theProductCodeX00001CanBePriced() throws IOException {
reset(productClient);
ProductBuilder product = new ProductBuilder()
.withProductCode("X00001");
when(productClient.find((Set<String>) argThat(contains("X00001")), any())).thenReturn(product);
}
}
```
### Using Spring Context Properties
The SpringRestPactRunner will look up any annotation expressions (like `${pactBrokerHost}`)
above) from the Spring context. For Springboot, this will allow you to define the properties in the application test properties.
For instance, if you create the following `application.yml` in the test resources:
```yaml
pactbroker:
host: "your.broker.local"
port: "443"
protocol: "https"
auth:
username: "<your broker username>"
password: "<your broker password>"
```
Then you can use the defaults on the `@PactBroker` annotation.
```java
@RunWith(SpringRestPactRunner.class)
@Provider("My Service")
@PactBroker(
authentication = @PactBrokerAuth(username = "${pactbroker.auth.username}", password = "${pactbroker.auth.password}")
)
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
public class PactVerificationTest {
```
### Using a random port with a Springboot test
If you use a random port in a springboot test (by setting `SpringBootTest.WebEnvironment.RANDOM_PORT`), you need to set it to the `TestTarget`. How this works is different for JUnit4 and JUnit5.
#### JUnit4
You can use the
`SpringBootHttpTarget` which will get the application port from the spring application context.
For example:
```java
@RunWith(SpringRestPactRunner.class)
@Provider("My Service")
@PactBroker
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
public class PactVerificationTest {
@TestTarget
public final Target target = new SpringBootHttpTarget();
}
```
#### JUnit5
You actually don't need to dependend on `pact-jvm-provider-spring` for this. It's sufficient to depend on `pact-jvm-provider-junit5`.
You can set the port to the `HttpTestTarget` object in the before method.
```java
@Provider("My Service")
@PactBroker
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
public class PactVerificationTest {
@LocalServerPort
private int port;
@BeforeEach
void before(PactVerificationContext context) {
context.setTarget(new HttpTestTarget("localhost", port));
}
}
```
Group: au.com.dius Artifact: pact-jvm-provider-spring
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact pact-jvm-provider-spring
Group au.com.dius
Version 4.0.10
Last update 18. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 5
Dependencies spring-boot-starter-test, spring-webmvc, javax.servlet-api, jackson-datatype-joda, pact-jvm-provider-junit,
There are maybe transitive dependencies!
Group au.com.dius
Version 4.0.10
Last update 18. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 5
Dependencies spring-boot-starter-test, spring-webmvc, javax.servlet-api, jackson-datatype-joda, pact-jvm-provider-junit,
There are maybe transitive dependencies!
Page 15 from 15 (items total 146)
© 2015 - 2025 Weber Informatics LLC | Privacy Policy