Giuseppe Salvatore
04/07/2022, 8:07 AMWill Robinson
04/07/2022, 1:25 PMYousaf Nabi (pactflow.io)
Yousaf Nabi (pactflow.io)
Nathan Deamer
04/11/2022, 9:17 AMCarl Ha
04/11/2022, 9:57 AMThomas K
04/11/2022, 1:34 PMConfigure your consumer build to run the Pact tests and publish its pact to the Broker as part of its main build (consult the documentation for your chosen language). Consumer Pact tests typically run after the unit tests, and before deploying to a test environment.
If I have unit tests and pact tests etc running on every PR build, on different feature or task branches (e.g. feature/PACT-101-do-something-cool
), should I publish it to pact broker as part of this PR build, using commit sha and branch (e.g. HEAD), or do I only do it on PR approval, at which point the feature branch merges into develop
branch? (we follow git flow consumer side)Kendrick B
04/12/2022, 4:18 AMOytun Yüksel
04/12/2022, 1:28 PMpact-broker can-i-deploy --pacticipant $APP_NAME --version $CI_COMMIT_SHORT_SHA --branch=$CI_COMMIT_BRANCH --to-environment $ENVIRONMENT --retry-while-unknown=12 --retry-interval=10 --verbose
Alessandro
04/12/2022, 2:02 PMStefano Lucka
04/12/2022, 4:30 PM.given("product with stock availability")
.given("transport API being down")
.uponReceiving("A request on /product-availability endpoint")
.willRespondWith()
.status(200)
.body(aValidResponseBodyUsingLikeEverywhere())
One part of our group says this is a valid test case, because we've made our verbal contract "On outage of your Transport API dependency we still expect a valid response from you" explicit now. On the other hand the second part of our POC group says, this is an implementation detail and we should not even know, that the provider is using a "transport api" to do its job.
Are there any best practices on such an example?Colin Anderson
04/12/2022, 6:36 PMpact-jvm
. I've had a PR accepted and merged into the master
branch of the pact-jvm
project. We're currently using the 4.1.x line of Pact libraries and really need the change from the PR. I was wondering how we can get the PR merged into the 4.1.x branch? Will this happen as part of a standard process, if so, then when, or should I raise another PR to merge it into 4.1.x?Matt (pactflow.io / pact-js / pact-go)
Édouard Lopez
04/15/2022, 12:19 PMStefano Lucka
04/19/2022, 3:11 PMideally, this should have been done in a feature branch, but for the sake of this example, we'll assume best practice advice was not followed.
https://docs.pact.io/pact_broker/advanced_topics/pending_pactsSo the way I understand it now must be this: Pending Pacts was made for the rare cases in which consumers accidentally or forcefully merge/push their changed PACT even though the PR pipeline wouldn't let them, isn't it? So either bei Administrator's force-merge of a PR even though the PR's quality gate failed, or by directly pushing to the main branch to hotfix something, etc. If in these cases they would at the same time change a PACT that the provider is not supporting, they would fail the providers cicd. Did I get this right?
David Van Couvering (DVC) - eBay
04/19/2022, 4:26 PMyusei ygui
04/20/2022, 8:44 PMYousaf Nabi (pactflow.io)
Slackbot
04/21/2022, 8:53 AMNuno Frias
04/21/2022, 9:54 AMStefano Lucka
04/22/2022, 3:28 PMLewis Cowles
04/24/2022, 11:11 PMHimanshu Pandey
04/25/2022, 4:23 AMWayne Ng
04/25/2022, 2:33 PMJayakannan Jeyapandian
04/28/2022, 12:50 PMstage ('Provider Verification') {
steps {
build job: 'providerVerificationPipeline'
}
David Van Couvering (DVC) - eBay
04/29/2022, 4:14 PMLaura Walsh
05/02/2022, 10:27 PMjithin jacob
05/04/2022, 4:59 AMDamian
05/05/2022, 1:10 PMJayakannan Jeyapandian
05/05/2022, 4:57 PM