SpringCloud/spring-cloud-contract
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add TestNG support for spring-cloud-contract-verifier (#1101) (#1135)

Browse Source 
fixes #1101
This commit is contained in:
janeisklar
2019-07-12 12:17:12 +02:00
committed by Marcin Grzejszczak
parent 82be516441
commit c55031e094
21 changed files with 511 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/src/main/asciidoc/verifier_introduction.adoc
View File

@@ -12,7 +12,7 @@ produced by Spring Cloud Contract Verifier.
* Messaging routes, if you're using a messaging service. We integrate with Spring
Integration, Spring Cloud Stream, Spring AMQP, and Apache Camel. You can also set your
own integrations.
* Acceptance tests (in JUnit 4, JUnit 5 or Spock) are used to verify if server-side implementation
* Acceptance tests (in JUnit 4, JUnit 5, TestNG or Spock) are used to verify if server-side implementation
of the API is compliant with the contract (__server tests__). A full test is generated by
Spring Cloud Contract Verifier.
@@ -395,8 +395,8 @@ Here is an example of a test generated in `WEBTESTCLIENT` test mode:
}
----
Apart from the default JUnit 4, you can instead use JUnit 5 or Spock tests, by setting the plugin
`testFramework` property to either `JUNIT5` or `Spock`.
Apart from the default JUnit 4, you can instead use JUnit 5, TestNG or Spock tests, by setting the plugin
`testFramework` property to either `JUNIT5`, `TESTNG` or `Spock`.
TIP: You can now also generate WireMock scenarios based on the contracts, by including an
order number followed by an underscore at the beginning of the contract file names.

2
docs/src/main/asciidoc/verifier_messaging.adoc
View File

@@ -70,7 +70,7 @@ messaging configuration, so you only need the one annotation.
Having the `input` or `outputMessage` sections in your DSL results in creation of tests
on the publisher's side. By default, JUnit 4 tests are created. However, there is also a
possibility to create JUnit 5 or Spock tests.
possibility to create JUnit 5, TestNG or Spock tests.
There are 3 main scenarios that we should take into consideration:

2
docs/src/main/asciidoc/verifier_setup.adoc
View File

@@ -249,7 +249,7 @@ from the Groovy DSL should be placed. By default its value is
`$buildDir/generated-test-resources/contracts`.
* *stubsOutputDir*: Specifies the directory where the generated WireMock stubs from
the Groovy DSL should be placed.
* *testFramework*: Specifies the target test framework to be used. Currently, Spock, JUnit 4 (`TestFramework.JUNIT`) and
* *testFramework*: Specifies the target test framework to be used. Currently, Spock, JUnit 4 (`TestFramework.JUNIT`), TestNG and
JUnit 5 are supported with JUnit 4 being the default framework.
* *contractsProperties*: a map containing properties to be passed to Spring Cloud Contract
components. Those properties might be used by e.g. inbuilt or custom Stub Downloaders.