-
-
Notifications
You must be signed in to change notification settings - Fork 479
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
39 changed files
with
2,515 additions
and
92 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| name: Pact-JVM Compatibility Suite | ||
|
|
||
| on: | ||
| push: | ||
| branches: [ master, v4.1.x, v4.4.x, v4.5.x ] | ||
| pull_request: | ||
| branches: [ master, v4.1.x, v4.4.x, v4.5.x ] | ||
|
|
||
| jobs: | ||
| v1: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v2 | ||
| - name: Set up JDK 18 | ||
| uses: actions/setup-java@v3 | ||
| with: | ||
| distribution: temurin | ||
| java-version: 18 | ||
| - name: Build with Gradle | ||
| run: ./gradlew --no-daemon :compatibility-suite:v1 | ||
| - name: Archive cucumber results | ||
| uses: actions/upload-artifact@v3 | ||
| with: | ||
| name: cucumber-report | ||
| path: compatibility-suite/build/cucumber-report-v1.html | ||
| if: always() |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| plugins { | ||
| id 'au.com.dius.pact.kotlin-common-conventions' | ||
| } | ||
|
|
||
| configurations { | ||
| cucumberRuntime { | ||
| extendsFrom testImplementation | ||
| } | ||
| } | ||
|
|
||
| dependencies { | ||
| testImplementation 'io.cucumber:cucumber-java:7.12.0' | ||
| testImplementation 'io.cucumber:cucumber-picocontainer:7.12.0' | ||
| testImplementation 'org.apache.groovy:groovy' | ||
| testImplementation 'org.apache.groovy:groovy-json' | ||
| testImplementation project(':core:model') | ||
| testImplementation project(':core:matchers') | ||
| testImplementation project(':consumer') | ||
| testImplementation project(':provider') | ||
| testImplementation('io.pact.plugin.driver:core') { | ||
| exclude group: 'au.com.dius.pact.core' | ||
| } | ||
| testImplementation 'ch.qos.logback:logback-classic' | ||
| implementation 'io.ktor:ktor-http-jvm' | ||
| } | ||
|
|
||
| tasks.register('v1') { | ||
| dependsOn assemble, testClasses | ||
| doLast { | ||
| def cucumberArgs = [ | ||
| '--plugin', 'pretty', | ||
| '--plugin', 'html:build/cucumber-report-v1.html', | ||
| '--glue', 'steps.v1', | ||
| 'pact-compatibility-suite/features/V1' | ||
| ] | ||
| if (project.hasProperty('cucumber.filter.tags')) { | ||
| cucumberArgs.add(0, project.property('cucumber.filter.tags')) | ||
| cucumberArgs.add(0, '-t') | ||
| } | ||
| javaexec { | ||
| main = "io.cucumber.core.cli.Main" | ||
| classpath = configurations.cucumberRuntime + sourceSets.main.output + sourceSets.test.output | ||
| args = cucumberArgs | ||
| systemProperty 'pact_do_not_track', 'true' | ||
| } | ||
| } | ||
| } |
145 changes: 145 additions & 0 deletions
145
compatibility-suite/pact-compatibility-suite/features/V1/HTTP/http_consumer.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,145 @@ | ||
| @consumer | ||
| Feature: Basic HTTP consumer | ||
| Supports basic HTTP consumer interactions | ||
|
|
||
| Background: | ||
| Given the following HTTP interactions have been defined: | ||
| | method | path | query | headers | body | response | response content | response body | | ||
| | GET | /basic | | | | 200 | application/json | basic.json | | ||
| | GET | /with_params | a=1&b=2 | | | 200 | | | | ||
| | GET | /with_headers | | 'X-TEST: Compatibility' | | 200 | | | | ||
| | PUT | /basic | | | basic.json | 200 | | | | ||
|
|
||
| Scenario: When all requests are made to the mock server | ||
| When the mock server is started with interaction {1} | ||
| And request {1} is made to the mock server | ||
| Then a 200 success response is returned | ||
| And the payload will contain the "basic" JSON document | ||
| And the content type will be set as "application/json" | ||
| When the pact test is done | ||
| Then the mock server status will be OK | ||
| And the mock server will write out a Pact file for the interaction when done | ||
| And the pact file will contain {1} interaction | ||
| And the {first} interaction request will be for a "GET" | ||
| And the {first} interaction response will contain the "basic.json" document | ||
|
|
||
| Scenario: When not all requests are made to the mock server | ||
| When the mock server is started with interactions "1, 2" | ||
| And request {1} is made to the mock server | ||
| Then a 200 success response is returned | ||
| When the pact test is done | ||
| Then the mock server status will NOT be OK | ||
| And the mock server will NOT write out a Pact file for the interactions when done | ||
| And the mock server status will be an expected but not received error for interaction {2} | ||
|
|
||
| Scenario: When an unexpected request is made to the mock server | ||
| When the mock server is started with interaction {1} | ||
| And request {2} is made to the mock server | ||
| Then a 500 error response is returned | ||
| When the pact test is done | ||
| Then the mock server status will NOT be OK | ||
| And the mock server will NOT write out a Pact file for the interactions when done | ||
| And the mock server status will be an unexpected "GET" request received error for interaction {2} | ||
|
|
||
| Scenario: Request with query parameters | ||
| When the mock server is started with interaction {2} | ||
| And request {2} is made to the mock server | ||
| Then a 200 success response is returned | ||
| When the pact test is done | ||
| Then the mock server status will be OK | ||
| And the mock server will write out a Pact file for the interaction when done | ||
| And the pact file will contain {1} interaction | ||
| And the {first} interaction request query parameters will be "a=1&b=2" | ||
|
|
||
| Scenario: Request with invalid query parameters | ||
| When the mock server is started with interaction {2} | ||
| And request {2} is made to the mock server with the following changes: | ||
| | query | | ||
| | a=1&c=3 | | ||
| Then a 500 error response is returned | ||
| When the pact test is done | ||
| Then the mock server status will NOT be OK | ||
| And the mock server status will be mismatches | ||
| And the mismatches will contain a "query" mismatch with error "Expected query parameter 'b' but was missing" | ||
| And the mismatches will contain a "query" mismatch with error "Unexpected query parameter 'c' received" | ||
| And the mock server will NOT write out a Pact file for the interaction when done | ||
|
|
||
| Scenario: Request with invalid path | ||
| When the mock server is started with interaction {1} | ||
| And request {1} is made to the mock server with the following changes: | ||
| | path | | ||
| | /path | | ||
| Then a 500 error response is returned | ||
| When the pact test is done | ||
| Then the mock server status will NOT be OK | ||
| And the mock server will NOT write out a Pact file for the interaction when done | ||
| And the mock server status will be an unexpected "GET" request received error for path "/path" | ||
|
|
||
| Scenario: Request with invalid method | ||
| When the mock server is started with interaction {1} | ||
| And request {1} is made to the mock server with the following changes: | ||
| | method | | ||
| | HEAD | | ||
| Then a 500 error response is returned | ||
| When the pact test is done | ||
| Then the mock server status will NOT be OK | ||
| And the mock server will NOT write out a Pact file for the interaction when done | ||
| And the mock server status will be an unexpected "HEAD" request received error for path "/basic" | ||
|
|
||
| Scenario: Request with headers | ||
| When the mock server is started with interaction {3} | ||
| And request {3} is made to the mock server | ||
| Then a 200 success response is returned | ||
| When the pact test is done | ||
| Then the mock server status will be OK | ||
| And the mock server will write out a Pact file for the interaction when done | ||
| And the pact file will contain {1} interaction | ||
| And the {first} interaction request will contain the header "X-TEST" with value "Compatibility" | ||
|
|
||
| Scenario: Request with invalid headers | ||
| When the mock server is started with interaction {3} | ||
| And request {3} is made to the mock server with the following changes: | ||
| | headers | | ||
| | 'X-OTHER: Something' | | ||
| Then a 500 error response is returned | ||
| When the pact test is done | ||
| Then the mock server status will NOT be OK | ||
| And the mock server status will be mismatches | ||
| And the mismatches will contain a "header" mismatch with error "Expected a header 'X-TEST' but was missing" | ||
| And the mock server will NOT write out a Pact file for the interaction when done | ||
|
|
||
| Scenario: Request with body | ||
| When the mock server is started with interaction {4} | ||
| And request {4} is made to the mock server | ||
| Then a 200 success response is returned | ||
| When the pact test is done | ||
| Then the mock server status will be OK | ||
| And the mock server will write out a Pact file for the interaction when done | ||
| And the pact file will contain {1} interaction | ||
| And the {first} interaction request will be for a "PUT" | ||
| And the {first} interaction request content type will be "application/json" | ||
| And the {first} interaction request will contain the "basic.json" document | ||
|
|
||
| Scenario: Request with invalid body | ||
| When the mock server is started with interaction {4} | ||
| And request {4} is made to the mock server with the following changes: | ||
| | body | | ||
| | JSON: {"one": "a", "two": "c"} | | ||
| Then a 500 error response is returned | ||
| When the pact test is done | ||
| Then the mock server status will NOT be OK | ||
| And the mock server status will be mismatches | ||
| And the mismatches will contain a "body" mismatch with path "$.two" with error "Expected 'b' (String) but received 'c' (String)" | ||
| And the mock server will NOT write out a Pact file for the interaction when done | ||
|
|
||
| Scenario: Request with the incorrect type of body contents | ||
| When the mock server is started with interaction {4} | ||
| And request {4} is made to the mock server with the following changes: | ||
| | body | | ||
| | XML: <?xml version="1.0" encoding="UTF-8"?><alligator name="Mary" feet="4"/> | | ||
| Then a 500 error response is returned | ||
| When the pact test is done | ||
| Then the mock server status will NOT be OK | ||
| And the mock server status will be mismatches | ||
| And the mismatches will contain a "body-content-type" mismatch with error "Expected a body of 'application/json' but the actual content type was 'application/xml'" | ||
| And the mock server will NOT write out a Pact file for the interaction when done |
Oops, something went wrong.