Add port configuration for MockService and MockServer #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
馃摑 Summary of Changes
The changes in this PR introduce a new
MockService
initializer that accepts theport
number on which to run theMockServer
. This will allow tests to always run on the same port between test runs.Along with the PactSwift enhancements described above, the following has been done:
MockService
testsv0.41.0
aarch64
slices.This means that the script that buildspact_mock_server.a
needs to build foraarch64
andx86_64
and create a fat binary containing both slices. Though thecargo build
fails when even when using Rust nightly toolchain. It fails when building thepact_mock_server.a
binary foraarch64
architecture from Rust code (building onx86_64
machines) due topact_mock_server
's dependencies' fail to build. Please focus oniOS
platform when using Carthage or preferrably use Swift Package Manager to bringPactSwift
into your project.arm64
architecture for macOS has been removed with Exclude arm64 for macos聽#53 until better support is available.MockService
1200
are valid and if port is not available it should fail withMockServerError(code:)
馃馃棐 Reviewer Notes
馃敤 How To Test