-
Hi there, just started using this library today, and I'm attempting to convert over some code that has been using PactConsumerSwift. The conversion has been pretty straightforward, however my tests don't work because the Mock Server isn't matching the request. PactConsumerSwift was pretty good about explaining this right in an inline code error, basically saying "we expected these requests, but got these instead, here's a diff". Is there something similar with PactSwift? I'm currently at a loss as to why my responses aren't matching up. EDIT: Turns out my problem was related to the Matcher stuff being handled differently than PactConsumerSwift. But I'd still be interested to know if there's a log file written out. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
PactConsumerSwift is not really displaying the log, it is all There's no log file written though. Can/could be put in the backlog to be done. Edit: #75 |
Beta Was this translation helpful? Give feedback.
-
Though there is a |
Beta Was this translation helpful? Give feedback.
PactConsumerSwift is not really displaying the log, it is all
pact-ruby-standalone
that does it.There's no log file written though. Can/could be put in the backlog to be done.
pact_ffi
libraryPactSwiftMockServer
uses does expose aconst char *pactffi_fetch_log_buffer(const char *log_id);
and there'sint pactffi_log_to_file(const char *file_name, LevelFilter level_filter);
. Would need to expose the interface throughPactSwiftMockServer
andPactSwift
. Could be an optionalURL(pathToFile:)
forMockService
initialiser.Edit: #75