@Michael Strasser has left the channel

There's lots of people in this channel and no activity. Is that because Pact for Swift is so easy/clear to use (I wish) or the interest is there but the teams can't necessarily adopt it?

I've spent some time on PactSwift these past weeks and major (breaking) changes are about to happen

More here - https://github.com/surpher/PactSwift/discussions/122

but! the good news is, it's shaping up to be much leaner, cleaner and better for bandwidth going forward.

@Martin Gallauner has left the channel

@Tomer has left the channel

@Taha Shakibania has left the channel

@georgia andrews has left the channel

@PK has left the channel

@Stephen Bell has left the channel

@Amit Wertheimer has left the channel

Hi team, I'm trying to write a basic test using PactConsumerSwift. However it is failing when Pact is trying to connect to the server.

test(): failed - Error setting up pact: Could not connect to the server.

I tried to change the localhost address as indicated in some fixes, but it didn't work. Here is my code, I'd be glad to receive your suggestions:

import Foundation
import PactConsumerSwift
import XCTest
import Hamcrest

class SimulatedSaleIntegration: XCTestCase {
    
    var mockService: MockService?
    let apiClient: SimulatedSaleViewModel = SimulatedSaleViewModel()
    let successfulSale = Sale(amount: 5000.0, vat: 0.19, tip: 0.15, paymentMethod: "", location: "")
    
    
    override func setUp() {
        super.setUp()
        mockService = MockService(provider: "calculator-service", consumer: "Example-app-for-testing")
        apiClient.setServer(url: mockService!.baseUrl)
      }
    
    override func tearDown() {
        super.tearDown()
      }
    
    func testGetSuccessfulSimulatedSale() {
        mockService!
            .uponReceiving("A request to get a simulated sale")
            .withRequest(
                method: .GET,
                path: "/calculator",
                query: [...]
            )
            .willRespondWith(
                status: 200,
                headers: ["Content-Type": "application/json"],
                body: [...]
            )
        
        mockService!.run { (testComplete) -> Void in
            self.apiClient.getSimulatedSale(sale: self.successfulSale)
            assertThat(self.apiClient.simulatedSale?.fee, equalTo(168.34))
            testComplete()
        }
    }
}

In logs, all I can see is

interactions/verification

request could not being performed

Task <5AEFFE81-A9B5-4574-9DFB-EE823F7B83B9>.<2> finished with error [-1004] Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo={_kCFStreamErrorCodeKey=61, NSUnderlyingError=0x6000015ed710 {Error Domain=kCFErrorDomainCFNetwork Code=-1004 "(null)" UserInfo={_NSURLErrorNWPathKey=satisfied (Path is satisfied), interface: en0[802.11], uses wifi, _kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <5AEFFE81-A9B5-4574-9DFB-EE823F7B83B9>.<2>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
  "LocalDataTask <5AEFFE81-A9B5-4574-9DFB-EE823F7B83B9>.<2>"
), NSLocalizedDescription=Could not connect to the server., NSErrorFailingURLStringKey=<https://0.0.0.0:1234/interactions/verification>, NSErrorFailingURLKey=<https://0.0.0.0:1234/interactions/verification>, _kCFStreamErrorDomainKey=1}

Anyone has an idea about this issue? Thanks in advace 😉

This looks like an older version of the swift library that uses the Ruby “core”. There should be some logs somewhere (or you should be able to enable them), could you please share those? Did the test ever work or are these new tests? What OS are you on?

@Jocelyn Lecomte has left the channel

@Inken has left the channel

@Diego Betancur has left the channel

@Megan Honig has left the channel

@Bertold Kolics has left the channel

@Val Kolovos has left the channel

@Marcus Couto has left the channel

Hey, a specific question using pact swift. We are having some trouble configuring the requestbody for our mockserver/contract test. Reason being we are (also) using an encrypted multipart in the request body. Any ideas? We couldnt really find a similar example. The actual request body looks something like this.

@Gianluca Ciccarelli has left the channel

@Shakil Riyad has left the channel

@Pietro Di Bello has left the channel

@Tom Lopez has left the channel

@Romain Létendart has left the channel

@Spencer has left the channel

@Dominik Krichbaum has left the channel

@Martin Mineo has left the channel