Download JAR files tagged by created with all dependencies
zk-dl from group cz.datalite (version 1.4.5.1)
Multiple loosely coupled modules which extend ZK framework, originally created by DataLite company.
ZKComposer - controll the MVC design with annotations @ZkEvent?, @ZkComponent?, @ZkBinding?, ... (similar to
zkspring or zkcdi projects, however without any framework dependencies).
ZKDLComponents splits ZK data driven components (listbox, combobox) to MVC design, adds support for easy large
data manipulation and contains many pre-built user controls (filter manager, sort manager, visible listbox
columns manager, export to excel, etc.)
HibernateDAO & ZKDLComponentsHibernateExtensions - Hibernate generic DAO design with extensions for
ZKDLComponents to replace all your plumbing code (filter, sort, lazy loading, CRUD).
SpringService? - service layer with spring - generic service which speaks to generic DAO. This is the way we use
our components at DataLite?, but you can use any integration or DAO at your will.
Group: cz.datalite Artifact: zk-dl
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact zk-dl
Group cz.datalite
Version 1.4.5.1
Last update 05. April 2017
Organization DataLite
URL http://zk.datalite.cz
License MIT License
Dependencies amount 1
Dependencies slf4j-api,
There are maybe transitive dependencies!
Group cz.datalite
Version 1.4.5.1
Last update 05. April 2017
Organization DataLite
URL http://zk.datalite.cz
License MIT License
Dependencies amount 1
Dependencies slf4j-api,
There are maybe transitive dependencies!
randoop from group net.sourceforge.javydreamercsw (version 1.3.2)
Randoop is an automatic unit test generator for Java. It automatically creates unit tests for your classes, in JUnit format.
Randoop generates unit tests using feedback-directed random test generation. In a nutshell, this technique randomly, but smartly, generates sequences of methods and constructor invocations for the classes under test, and uses the sequences to create tests. Randoop executes the sequences it creates, using the results of the execution to create assertions that capture the behavior or your program and that catch bugs.
Randoop has created tests that find previously unkwon errors even in widely-used libraries including Sun and IBM's JDKs. A .NET version of Randoop, used internally at Microsoft, has been used successfully by a team of test engineers to find errors in a core .NET component that has been heavily tested for years. Randoop's combination of randomized test generation and test execution results in a highly effective test generation technique.
Artifact randoop
Group net.sourceforge.javydreamercsw
Version 1.3.2
Last update 05. December 2012
Organization not specified
URL https://sourceforge.net/projects/randoopmplugin/
License MIT License
Dependencies amount 2
Dependencies manipulation, plume,
There are maybe transitive dependencies!
Group net.sourceforge.javydreamercsw
Version 1.3.2
Last update 05. December 2012
Organization not specified
URL https://sourceforge.net/projects/randoopmplugin/
License MIT License
Dependencies amount 2
Dependencies manipulation, plume,
There are maybe transitive dependencies!
zoomvideosdk-videoeffects from group us.zoom.videosdk (version 1.11.2)
Group: us.zoom.videosdk Artifact: zoomvideosdk-videoeffects
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
zoomvideosdk-annotation from group us.zoom.videosdk (version 1.11.2)
The Video SDKs are app development kits provided to enrich apps with video collaboration features to connect customers and communities. Use these SDKs to build apps with highly customized user interfaces along with access to raw video and audio data.
Video SDKs are designed to be:
* Easy to use: Import libraries, call required functions, and all video conferencing will be handled for you.
* Lightweight: Video SDKs are streamlined toolkits with an enormous reduction in size compared to Meeting SDKs with all the power of Zoom's video and audio solutions.
* Highly customizable: Raw video and audio data is available to you, allowing your chosen renderer to customize the video experience.
Video sessions created by the Video SDKs are launched instantly, bringing a delightful video communication experience to your users with high-quality video and audio.
Direct access to raw video and audio data allows improved interaction between users and the app video stream. Imagine a gaming video streaming app with direct interaction between the player and viewers based on in-game events or prompts from the community. Or, imagine an AR streaming platform with direct viewer access to the on-screen video.
As with our Meeting SDKs, Video SDKs allow screen-sharing from devices, in-session chat messages, and high-quality video and audio streams similar to Zoom's core capabilities.
The Video SDKs enable the following functionality in your app:
* Launch a video communication session instantly
* Share screen directly from your device
* Send instant chat messages during the session
* Capture and review raw data locally
* Test different rendering schema and enjoy high-quality video and audio streams
* Broadcast the video session to third-party live streaming providers
To know more, see: https://developers.zoom.us/docs/video-sdk/
Group: us.zoom.videosdk Artifact: zoomvideosdk-annotation
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact zoomvideosdk-annotation
Group us.zoom.videosdk
Version 1.11.2
Last update 23. April 2024
Organization not specified
URL https://developers.zoom.us/docs/video-sdk/
License Zoom Video SDK Terms of Service
Dependencies amount 1
Dependencies constraintlayout,
There are maybe transitive dependencies!
Group us.zoom.videosdk
Version 1.11.2
Last update 23. April 2024
Organization not specified
URL https://developers.zoom.us/docs/video-sdk/
License Zoom Video SDK Terms of Service
Dependencies amount 1
Dependencies constraintlayout,
There are maybe transitive dependencies!
zoomvideosdk-core from group us.zoom.videosdk (version 1.11.2)
The Video SDKs are app development kits provided to enrich apps with video collaboration features to connect customers and communities. Use these SDKs to build apps with highly customized user interfaces along with access to raw video and audio data.
Video SDKs are designed to be:
* Easy to use: Import libraries, call required functions, and all video conferencing will be handled for you.
* Lightweight: Video SDKs are streamlined toolkits with an enormous reduction in size compared to Meeting SDKs with all the power of Zoom's video and audio solutions.
* Highly customizable: Raw video and audio data is available to you, allowing your chosen renderer to customize the video experience.
Video sessions created by the Video SDKs are launched instantly, bringing a delightful video communication experience to your users with high-quality video and audio.
Direct access to raw video and audio data allows improved interaction between users and the app video stream. Imagine a gaming video streaming app with direct interaction between the player and viewers based on in-game events or prompts from the community. Or, imagine an AR streaming platform with direct viewer access to the on-screen video.
As with our Meeting SDKs, Video SDKs allow screen-sharing from devices, in-session chat messages, and high-quality video and audio streams similar to Zoom's core capabilities.
The Video SDKs enable the following functionality in your app:
* Launch a video communication session instantly
* Share screen directly from your device
* Send instant chat messages during the session
* Capture and review raw data locally
* Test different rendering schema and enjoy high-quality video and audio streams
* Broadcast the video session to third-party live streaming providers
To know more, see: https://developers.zoom.us/docs/video-sdk/
Group: us.zoom.videosdk Artifact: zoomvideosdk-core
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact zoomvideosdk-core
Group us.zoom.videosdk
Version 1.11.2
Last update 23. April 2024
Organization not specified
URL https://developers.zoom.us/docs/video-sdk/
License Zoom Video SDK Terms of Service
Dependencies amount 3
Dependencies security-crypto, tink-android, appcompat,
There are maybe transitive dependencies!
Group us.zoom.videosdk
Version 1.11.2
Last update 23. April 2024
Organization not specified
URL https://developers.zoom.us/docs/video-sdk/
License Zoom Video SDK Terms of Service
Dependencies amount 3
Dependencies security-crypto, tink-android, appcompat,
There are maybe transitive dependencies!
ZoomVideoSDK from group us.zoom.videosdk (version 1.9.0)
We have deprecated ZoomVideoSDK maven repository. Since Video SDK features have been modularized, we are deprecating this repository and publishing new releases into the following repositories. See the feature libraries documentation for details.
ZoomVideoSDK Core — core Video SDK features: https://mvnrepository.com/artifact/us.zoom.videosdk/zoomvideosdk-core
ZoomVideoSDK Annotation — Screen share annotation feature: https://mvnrepository.com/artifact/us.zoom.videosdk/zoomvideosdk-annotation
ZoomVideoSDK Videoeffects — Virtual background feature: https://mvnrepository.com/artifact/us.zoom.videosdk/zoomvideosdk-videoeffects
The Video SDKs are app development kits provided to enrich apps with video collaboration features to connect customers and communities. Use these SDKs to build apps with highly customized user interfaces along with access to raw video and audio data.
Video SDKs are designed to be:
* Easy to use: Import libraries, call required functions, and all video conferencing will be handled for you.
* Lightweight: Video SDKs are streamlined toolkits with an enormous reduction in size compared to Meeting SDKs with all the power of Zoom's video and audio solutions.
* Highly customizable: Raw video and audio data is available to you, allowing your chosen renderer to customize the video experience.
Video sessions created by the Video SDKs are launched instantly, bringing a delightful video communication experience to your users with high-quality video and audio.
Direct access to raw video and audio data allows improved interaction between users and the app video stream. Imagine a gaming video streaming app with direct interaction between the player and viewers based on in-game events or prompts from the community. Or, imagine an AR streaming platform with direct viewer access to the on-screen video.
As with our Meeting SDKs, Video SDKs allow screen-sharing from devices, in-session chat messages, and high-quality video and audio streams similar to Zoom's core capabilities.
The Video SDKs enable the following functionality in your app:
* Launch a video communication session instantly
* Share screen directly from your device
* Send instant chat messages during the session
* Capture and review raw data locally
* Test different rendering schema and enjoy high-quality video and audio streams
* Broadcast the video session to third-party live streaming providers
To know more, see: https://developers.zoom.us/docs/video-sdk/
Group: us.zoom.videosdk Artifact: ZoomVideoSDK
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact ZoomVideoSDK
Group us.zoom.videosdk
Version 1.9.0
Last update 20. September 2023
Organization not specified
URL https://developers.zoom.us/docs/video-sdk/
License Zoom Video SDK Terms of Service
Dependencies amount 3
Dependencies security-crypto, tink-android, appcompat,
There are maybe transitive dependencies!
Group us.zoom.videosdk
Version 1.9.0
Last update 20. September 2023
Organization not specified
URL https://developers.zoom.us/docs/video-sdk/
License Zoom Video SDK Terms of Service
Dependencies amount 3
Dependencies security-crypto, tink-android, appcompat,
There are maybe transitive dependencies!
tagmycode-netbeans from group com.tagmycode (version 2.3.0)
Provides the support for <a href="https://tagmycode.com">TagMyCode</a>.
This plugin allows you to manage your own snippets.<br/>
<br/>
Features:<br/>
* Add snippets: you can save your code snippets including description, language, and tags<br/>
* List snippets (CRUD): snippets are stored locally and you can filter, sort, create, modify, edit or delete them directly from the IDE<br/>
* Quick search: you can search your snippets and insert them directly into the document<br/>
<br/>
CHANGELOG:<br/>
<br/>
2.3.0 (released 2020-07-26)<br/>
* published plugin into Apache NetBeans Plugin Portal<br/>
* filter snippets by languages<br/>
<br/>
2.2.1 (released 2018-01-10)<br/>
* Quick Search dialog is now resizable</br>
* fixed syntax highlight for PHP and HTML</br>
* if refresh token is not valid user will be automatically logged out</br>
</br>
2.2.0 (released 2017-11-06)<br/>
* snippets management works in offline mode<br/>
* autodetect language on new snippet<br/>
* added settings dialog with editor theme and font size option<br/>
* added title and description to snippet view<br/>
* changed open browser class<br/>
* text can be dragged into table to create a new snippet<br/>
* snippets can be dragged directly into editor and the code are copied<br/>
* added "save as file" feature<br/>
* added "clone snippet" feature<br/>
* added "snippet properties" dialog<br/>
* detect binary file<br/>
<br/>
2.1.0 (released 2017-04-24)<br/>
* moved error messages from dialog to Netbeans Notification Log<br/>
* added welcome panel<br/>
* about dialog shows plugin version and framework version<br/>
* moved storage from JSON to SQL<br/>
<br/>
2.0 (released 2016-07-11)<br/>
* new user interface<br/>
* list of snippets stored locally<br/>
* syntax highlight powered by <a href="http://bobbylight.github.io/RSyntaxTextArea/">RSyntaxTextArea</a><br/>
* snippets are synchronized with server<br/>
* filter snippets<br/>
* quick search feature<br/>
* insert selected snippet at cursor in document<br/>
<br/>
1.1.3 (released 2015-12-18)<br/>
* Fix for NetBeans 8.1<br/>
<br/>
1.1.2 (released 2014-10-03)<br/>
* Switched authentication from OAuth 1.0a to OAuth 2<br/>
* Console write also snippet title when new snippet is created (thanks to bejoy)<br/>
<br/>
1.1 (released 2014-08-19)<br/>
* Added "Search snippets" feature<br/>
* Fixed some minor bugs<br/>
<br/>
1.0 (released 2014-04-14)<br/>
* First release with feature "Create snippet"<br/>
Artifact tagmycode-netbeans
Group com.tagmycode
Version 2.3.0
Last update 06. September 2020
Organization not specified
URL https://tagmycode.com
License Apache License 2.0
Dependencies amount 18
Dependencies commons-lang3, rsyntaxtextarea, guava, org-netbeans-api-annotations-common, org-openide-awt, org-netbeans-modules-settings, org-openide-dialogs, org-netbeans-modules-editor, org-netbeans-modules-keyring, org-openide-nodes, org-openide-util, org-openide-loaders, org-openide-windows, org-openide-util-ui, org-openide-text, org-netbeans-api-progress, log4j, tagmycode-plugin-framework,
There are maybe transitive dependencies!
Group com.tagmycode
Version 2.3.0
Last update 06. September 2020
Organization not specified
URL https://tagmycode.com
License Apache License 2.0
Dependencies amount 18
Dependencies commons-lang3, rsyntaxtextarea, guava, org-netbeans-api-annotations-common, org-openide-awt, org-netbeans-modules-settings, org-openide-dialogs, org-netbeans-modules-editor, org-netbeans-modules-keyring, org-openide-nodes, org-openide-util, org-openide-loaders, org-openide-windows, org-openide-util-ui, org-openide-text, org-netbeans-api-progress, log4j, tagmycode-plugin-framework,
There are maybe transitive dependencies!
jsgen from group com.github.jochenw (version 1.2)
Jsgen is a Java Source Generation Framework: That means, it should be a valuable tool, if you intend to write a custom generator for Java
sources.
As such, it is the successor of a previous framework, called JaxMeJS (http://jaxme.sourceforge.net/JaxMeJS/docs/index.html).
The predecessor came into being as a standalone project. It was incorporated into the bigger JaxMe project, when the latter
was adopted by the Apache Webservices project. And it was buried as part of the bigger project, when the latter was moved to the
Apache Attic (http://svn.apache.org/repos/asf/webservices/archive/jaxme/).
That was fine for quite some time, because the latest released version (JaxMeJS 0.5.2) did its job quite well.
Over the years, however, the Java language has evolved, and the lack of support for features like Generics, or
Annotations, became a burden. Hence the Successor: Jsgen picks up, where JaxMeJS ended. It is, however, a complete
rewrite with several additional features, that the author considers to be important for modern Java applications:
1. It supports Generics.
2. It supports Annotations.
3. The builder pattern has been adopted. Almost all important classes are implemented as builders.
This should make writing the actual source generators much more concise, and maintainable, than
it used to be before.
4. The code style is configurable. Code styles allow you to concentrate on the actual work.
The resulting Jave source will look nicely formatted, anyways. As of this writing, you
can select between two builtin code styles:
- The default code style is basically the authors personal free style, roughly comparable to the default
code style of the Eclipse Java IDE.
- As an alternative, there is also a Maven code style, which is widely used in the Open Source communities.
Compared to the default style, it is less concise, if not even a bit verbose. On the other hand, it is
widely adopted by projects in the vicinity of {{{https://maven.apache.org}Apache Maven}}.
5. Import lists are created, and sorted, automatically.
Artifact jsgen
Group com.github.jochenw
Version 1.2
Last update 10. November 2019
Organization not specified
URL https://jochenw.github.io/jsgen
License Apache License, Version 2.0
Dependencies amount 1
Dependencies jsr305,
There are maybe transitive dependencies!
Group com.github.jochenw
Version 1.2
Last update 10. November 2019
Organization not specified
URL https://jochenw.github.io/jsgen
License Apache License, Version 2.0
Dependencies amount 1
Dependencies jsr305,
There are maybe transitive dependencies!
pact-jvm-server_2.12 from group au.com.dius (version 3.6.15)
Pact server
===========
The pact server is a stand-alone interactions recorder and verifier, aimed at clients that are non-JVM or non-Ruby based.
The pact client for that platform will need to be implemented, but it only be responsible for generating the `JSON`
interactions, running the tests and communicating with the server.
The server implements a `JSON` `REST` Admin API with the following endpoints.
/ -> For diagnostics, currently returns a list of ports of the running mock servers.
/create -> For initialising a test server and submitting the JSON interactions. It returns a port
/complete -> For finalising and verifying the interactions with the server. It writes the `JSON` pact file to disk.
## Running the server
### Versions 2.2.6+
Pact server takes the following parameters:
```
Usage: pact-jvm-server [options] [port]
port
port to run on (defaults to 29999)
--help
prints this usage text
-h <value> | --host <value>
host to bind to (defaults to localhost)
-l <value> | --mock-port-lower <value>
lower bound to allocate mock ports (defaults to 20000)
-u <value> | --mock-port-upper <value>
upper bound to allocate mock ports (defaults to 40000)
-d | --daemon
run as a daemon process
-v <value> | --pact-version <value>
pact version to generate for (2 or 3)
-k <value> | --keystore-path <value>
Path to keystore
-p <value> | --keystore-password <value>
Keystore password
-s <value> | --ssl-port <value>
Ssl port the mock server should run on. lower and upper bounds are ignored
--debug
run with debug logging
```
### Using trust store 3.4.0+
Trust store can be used. However, it is limited to a single port for the time being.
### Prior to version 2.2.6
Pact server takes one optional parameter, the port number to listen on. If not provided, it will listen on 29999.
It requires an active console to run.
### Using a distribution archive
You can download a [distribution from maven central](http://search.maven.org/remotecontent?filepath=au/com/dius/pact-jvm-server_2.11/2.2.4/).
There is both a ZIP and TAR archive. Unpack it to a directory of choice and then run the script in the bin directory.
### Building a distribution bundle
You can build an application bundle with gradle by running (for 2.11 version):
$ ./gradlew :pact-jvm-server_2.11:installdist
This will create an app bundle in `build/2.11/install/pact-jvm-server_2.11`. You can then execute it with:
$ java -jar pact-jvm-server/build/2.10/install/pact-jvm-server_2.11/lib/pact-jvm-server_2.11-3.2.11.jar
or with the generated bundle script file:
$ pact-jvm-server/build/2.11/install/pact-jvm-server_2.11/bin/pact-jvm-server_2.11
By default will run on port `29999` but a port number can be optionally supplied.
### Running it with docker
You can use a docker image to execute the mock server as a docker container.
$ docker run -d -p 8080:8080 -p 20000-20010:20000-20010 uglyog/pact-jvm-server
This will run the main server on port 8080, and each created mock server on ports 20000-20010. You can map the ports to
any you require.
## Life cycle
The following actions are expected to occur
* The client calls `/create` to initialise a server with the expected `JSON` interactions and state
* The admin server will start a mock server on a random port and return the port number in the response
* The client will execute its interaction tests against the mock server with the supplied port
* Once finished, the client will call `/complete' on the Admin API, posting the port number
* The pact server will verify the interactions and write the `JSON` `pact` file to disk under `/target`
* The mock server running on the supplied port will be shutdown.
## Endpoints
### /create
The client will need `POST` to `/create` the generated `JSON` interactions, also providing a state as a query parameter
and a path.
For example:
POST http://localhost:29999/create?state=NoUsers&path=/sub/ref/path '{ "provider": { "name": "Animal_Service"}, ... }'
This will create a new running mock service provider on a randomly generated port. The port will be returned in the
`201` response:
{ "port" : 34423 }
But you can also reference the path from `/sub/ref/path` using the server port. The service will not strip
the prefix path, but instead will use it as a differentiator. If your services do not have differences
in the prefix of their path, then you will have to use the port method.
### /complete
Once the client has finished running its tests against the mock server on the supplied port (in this example port
`34423`) the client will need to `POST` to `/complete` the port number of the mock server that was used.
For example:
POST http://localhost:29999/complete '{ "port" : 34423 }'
This will cause the Pact server to verify the interactions, shutdown the mock server running on that port and writing
the pact `JSON` file to disk under the `target` directory.
### /
The `/` endpoint is for diagnostics and to check that the pact server is running. It will return all the currently
running mock servers port numbers.
For example:
GET http://localhost:29999/
'{ "ports": [23443,43232] }'
2 downloads
Artifact pact-jvm-server_2.12
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 4
Dependencies pact-jvm-consumer_2.12, logback-core, logback-classic, scopt_2.12,
There are maybe transitive dependencies!
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 4
Dependencies pact-jvm-consumer_2.12, logback-core, logback-classic, scopt_2.12,
There are maybe transitive dependencies!
pact-jvm-consumer-junit5_2.12 from group au.com.dius (version 3.6.15)
pact-jvm-consumer-junit5
========================
JUnit 5 support for Pact consumer tests
## Dependency
The library is available on maven central using:
* group-id = `au.com.dius`
* artifact-id = `pact-jvm-consumer-junit5_2.12`
* version-id = `3.6.x`
## Usage
### 1. Add the Pact consumer test extension to the test class.
To write Pact consumer tests with JUnit 5, you need to add `@ExtendWith(PactConsumerTestExt)` to your test class. This
replaces the `PactRunner` used for JUnit 4 tests. The rest of the test follows a similar pattern as for JUnit 4 tests.
```java
@ExtendWith(PactConsumerTestExt.class)
class ExampleJavaConsumerPactTest {
```
### 2. create a method annotated with `@Pact` that returns the interactions for the test
For each test (as with JUnit 4), you need to define a method annotated with the `@Pact` annotation that returns the
interactions for the test.
```java
@Pact(provider="ArticlesProvider", consumer="test_consumer")
public RequestResponsePact createPact(PactDslWithProvider builder) {
return builder
.given("test state")
.uponReceiving("ExampleJavaConsumerPactTest test interaction")
.path("/articles.json")
.method("GET")
.willRespondWith()
.status(200)
.body("{\"responsetest\": true}")
.toPact();
}
```
### 3. Link the mock server with the interactions for the test with `@PactTestFor`
Then the final step is to use the `@PactTestFor` annotation to tell the Pact extension how to setup the Pact test. You
can either put this annotation on the test class, or on the test method. For examples see
[ArticlesTest](src/test/java/au/com/dius/pact/consumer/junit5/ArticlesTest.java) and
[MultiTest](src/test/groovy/au/com/dius/pact/consumer/junit5/MultiTest.groovy).
The `@PactTestFor` annotation allows you to control the mock server in the same way as the JUnit 4 `PactProviderRule`. It
allows you to set the hostname to bind to (default is `localhost`) and the port (default is to use a random port). You
can also set the Pact specification version to use (default is V3).
```java
@ExtendWith(PactConsumerTestExt.class)
@PactTestFor(providerName = "ArticlesProvider")
public class ExampleJavaConsumerPactTest {
```
**NOTE on the hostname**: The mock server runs in the same JVM as the test, so the only valid values for hostname are:
| hostname | result |
| -------- | ------ |
| `localhost` | binds to the address that localhost points to (normally the loopback adapter) |
| `127.0.0.1` or `::1` | binds to the loopback adapter |
| host name | binds to the default interface that the host machines DNS name resolves to |
| `0.0.0.0` or `::` | binds to the all interfaces on the host machine |
#### Matching the interactions by provider name
If you set the `providerName` on the `@PactTestFor` annotation, then the first method with a `@Pact` annotation with the
same provider name will be used. See [ArticlesTest](src/test/java/au/com/dius/pact/consumer/junit5/ArticlesTest.java) for
an example.
#### Matching the interactions by method name
If you set the `pactMethod` on the `@PactTestFor` annotation, then the method with the provided name will be used (it still
needs a `@Pact` annotation). See [MultiTest](src/test/groovy/au/com/dius/pact/consumer/junit5/MultiTest.groovy) for an example.
### Injecting the mock server into the test
You can get the mock server injected into the test method by adding a `MockServer` parameter to the test method.
```java
@Test
void test(MockServer mockServer) throws IOException {
HttpResponse httpResponse = Request.Get(mockServer.getUrl() + "/articles.json").execute().returnResponse();
assertThat(httpResponse.getStatusLine().getStatusCode(), is(equalTo(200)));
}
```
This helps with getting the base URL of the mock server, especially when a random port is used.
## Changing the directory pact files are written to
By default, pact files are written to `target/pacts` (or `build/pacts` if you use Gradle), but this can be overwritten with the `pact.rootDir` system property.
This property needs to be set on the test JVM as most build tools will fork a new JVM to run the tests.
For Gradle, add this to your build.gradle:
```groovy
test {
systemProperties['pact.rootDir'] = "$buildDir/custom-pacts-directory"
}
```
For maven, use the systemPropertyVariables configuration:
```xml
<project>
[...]
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.18</version>
<configuration>
<systemPropertyVariables>
<pact.rootDir>some/other/directory</pact.rootDir>
<buildDirectory>${project.build.directory}</buildDirectory>
[...]
</systemPropertyVariables>
</configuration>
</plugin>
</plugins>
</build>
[...]
</project>
```
For SBT:
```scala
fork in Test := true,
javaOptions in Test := Seq("-Dpact.rootDir=some/other/directory")
```
### Using `@PactFolder` annotation [3.6.2+]
You can override the directory the pacts are written in a test by adding the `@PactFolder` annotation to the test
class.
## Forcing pact files to be overwritten (3.6.5+)
By default, when the pact file is written, it will be merged with any existing pact file. To force the file to be
overwritten, set the Java system property `pact.writer.overwrite` to `true`.
## Unsupported
The current implementation does not support tests with multiple providers. This will be added in a later release.
# Having values injected from provider state callbacks (3.6.11+)
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.
The following DSL methods all you to set an expression that will be parsed with the values returned from the provider states:
For JSON bodies, use `valueFromProviderState`.<br/>
For headers, use `headerFromProviderState`.<br/>
For query parameters, use `queryParameterFromProviderState`.<br/>
For paths, use `pathFromProviderState`.
For example, assume that an API call is made to get the details of a user by ID. A provider state can be defined that
specifies that the user must be exist, but the ID will be created when the user is created. So we can then define an
expression for the path where the ID will be replaced with the value returned from the provider state callback.
```java
.pathFromProviderState("/api/users/${id}", "/api/users/100")
```
You can also just use the key instead of an expression:
```java
.valueFromProviderState('userId', 'userId', 100) // will look value using userId as the key
```
Group: au.com.dius Artifact: pact-jvm-consumer-junit5_2.12
Show all versions Show documentation Show source
Show all versions Show documentation Show source
3 downloads
Artifact pact-jvm-consumer-junit5_2.12
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 2
Dependencies pact-jvm-consumer_2.12, junit-jupiter-api,
There are maybe transitive dependencies!
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 2
Dependencies pact-jvm-consumer_2.12, junit-jupiter-api,
There are maybe transitive dependencies!
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- 79
- 80
- 81
- 82
- 83
- 84
- 85
- 86
- 87
- 88
- 89
- 90
- 91
- 92
- 93
Page 90 from 93 (items total 922)