Skip to content

feat: Use content type matching rule for V3 message's binary body #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tienvx wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: Use content type matching rule for V3 message's binary body #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions features/V3/message_provider.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,16 +86,20 @@ Feature: Message provider

Scenario: Message with binary body (positive case)
Given a provider is started that can generate the "image" message with "file: rat.jpg"
And a Pact file for "image":"file: rat.jpg" is to be verified
And a Pact file for "image" is to be verified with the following:
| body | file: spider.jpg |
| matching rules | contenttype-matcher-v3.json |
When the verification is run
Then the verification will be successful

Scenario: Message with binary body (negative case)
Given a provider is started that can generate the "image" message with "file: rat.jpg"
And a Pact file for "image":"file: spider.jpg" is to be verified
And a Pact file for "image" is to be verified with the following:
| body | file: sample.pdf |
| matching rules | contenttype-matcher-v3.json |
When the verification is run
Then the verification will NOT be successful
And the verification results will contain a "Body had differences" error
And the verification results will contain a "Body type had differences" error

Scenario: Supports matching rules for the message metadata (positive case)
Given a provider is started that can generate the "basic" message with "file: basic.json" and the following metadata:
Expand Down