Consistently Behavior between PACT FFI and stub server

[HuiSou]

Everyone,

Can you help us getting over the challanges here?
The teams in my current company are now leveraging PACT for building a provider service for Automated UAT (using BDD) and discovered some friction regarding a mock server

1. Given a big contract files, stub server performs poorly, making tests gettting flaky due to api provider timeout
   
   
   

2. Given a mismatch request, PACT_FFI will throw an error indicate what's wrong while stub server will just return 404 without a clue

I've try migrating the PACT stub server to PACT_FFI on our Automated UAT test and this make thing more easier to debug and understand, and I believe that it would be better if pact mock can does the same thing

[YOU54F]

Could you expand a bit more on your use case and provide a repro

pact-stub-server is for loading precreated pacts, and generating a stub server from them.

pact-ffi allows for a library to create a mock server & verifier programatically but it is exposed as 2 cli's https://github.com/pact-foundation/pact-core-mock-server & https://github.com/pact-foundation/pact-reference/tree/master/rust/pact_verifier_cli

PACT_FFI will throw an error indicate what's wrong while stub server will just return 404 without a clue

that is the expected difference between a mock (in pact ffi) and a stub server