Tú Phạm
04/26/2025, 3:54 AMJun Yi
04/28/2025, 3:33 AMverifier = Verifier().set_info(name=PROVIDER_NAME, url=PROVIDER_URL)
verifier.broker_source(url=URL(settings.pact_flow_url), token=settings.pact_broker_token)
verifier.set_state(url=PROVIDER_URL / "_pact" / "callback", teardown=True)
verifier.filter_consumers(consumer_name)
verifier.set_publish_options(version=str(version))
verifier.verify()
Thanks for your help!Alessandro
05/07/2025, 11:39 AMPavanraj Ramisetty
05/07/2025, 9:55 PMPascal
05/08/2025, 2:36 PMPascal
05/08/2025, 2:36 PMPascal
05/08/2025, 2:45 PMPavanraj Ramisetty
05/09/2025, 5:32 AMVignesh
05/12/2025, 1:22 PMTim Vahlbrock
05/14/2025, 12:54 PMAntonio Blandón Torres
05/16/2025, 9:40 PMMartin Konir
05/21/2025, 10:35 AMBACKWARD
compatibility type).
Could you help clarify the main business cases for using both Pact and Schema Registry together? Specifically:
• If we are already using the Schema Registry to enforce message structure and compatibility, does Pact contract testing become redundant?
• Or does Pact provide additional value beyond schema validation?
• If we decided to write contract tests for a Apache Pulsar messaging system, does Pact have any sort of integration - is it ready for that? (I wasn't able to find the necessary materials on this topic - everything is kafka centered 😅).
Thank you very much for your insights!Matt (pactflow.io / pact-js / pact-go)
Jordan Nazemi
06/03/2025, 3:21 PMAPI Base URL
in their OAS. When we try to generate Pacts with Cypress for it on the frontend, the entire path (include that base URL) is provided as the consumer contract. The issue is, Pactflow doesn't seem to match it with the base URL and were having to strip it from the JSON before pushing it up to Pactflow. ie
• Consumer pact states the path is service/v1/endpoint
• Provider states the base url is service/v1
and the endpoint is /endpoint
• Pactflow marks the two as incompatible UNLESS we strip the service/v1
from the JSON generated by the Cypress Pact adapter before we push it to Pactflow
Any ideas of a better solution that stripping?Erich Zimmerman
06/17/2025, 5:46 PMDilip Punna
06/19/2025, 5:00 PMZachary Lysobey
06/20/2025, 12:23 AMhttps://pact.io/it seems like maybe the JS is broken on the page, and doing stuff like clicking
view on Github
doesn't work for meBogdan Barliga
06/23/2025, 1:30 PMDmitry Munda
07/01/2025, 11:49 AMinteractionId
in HAL browser, not user-friendly names. is it something new-ish ?
"testResults": [{
"interactionId": "0eac6b0ba31719c60b6d5d0c1a5a1ceab75943c2",
"mismatches": [{
"attribute": "body",
"description": "Actual map is missing the following keys: reason",
"identifier": "$"
}],
"success": false
},... {
"interactionId": "30ac1652bdc5ce4d8109d0ccabb4b99f6adc0013",
"success": true
}]
Jun Yi
07/02/2025, 8:17 AMcan-i-deploy
fails?
I'm exploring the following workaround — is this a valid approach?
1. create-version
2. publish-pact
/ verify-pact
3. can-i-deploy
(fails)
4. force deploy anyway (with override flag or manual trigger)
5. record-deployment
Are there any risks or better alternatives to this flow?Kevin
07/02/2025, 3:31 PMKinkini Gamage
07/03/2025, 2:24 AMBas Dijkstra
07/07/2025, 12:01 PMLachlan Newman
07/08/2025, 5:35 AMAndrew Marshall
07/08/2025, 8:39 AMlet result = RUNTIME.block_on(async {
let result = load_plugin(&dependency).await;
// Add a small delay to let asynchronous tasks to complete
sleep(Duration::from_millis(500)).await;
result
});
I've tried using a fixture to make the plugin and provider instance persistent across multiple tests, but haven't had much luck (it looks like there's some state not being cleaned up between unit test runs - or maybe ths issue is with our plugin?) - the first test passes but subsequent ones fail due to contract verification failures.
I can probably provide a minimal example but I thought I'd ask first in case you had any ideas.
Many thanks!Priyaranjan Mudliar
07/08/2025, 9:54 PMLachlan Newman
07/09/2025, 4:14 AMFreddie Jiang
07/22/2025, 7:26 AMFreddie Jiang
07/24/2025, 2:07 AMFreddie Jiang
07/24/2025, 5:42 AM