Hi Pact Team, I am writing a consumer test in go u...
# pact-gow
Wesley Newcomb
07/13/2023, 4:32 PMHi Pact Team, I am writing a consumer test in go using the new gRPC workflow. I am trying to call (*message.SynchronousPact).AddSynchronousMessage() twice within the same test because my gRPC server has multiple RPCs. When I run the test with just one call to (*message.SynchronousPact).AddSynchronousMessage() the test passes and a valid pact is generated but I still see this log
Copy code
2023-07-13T16:02:55.872397Z ERROR ThreadId(01) pact_mock_server::server_manager: Failed to shutdown plugin mock server with ID 97fa0c1e-3e37-4199-807f-3c16e3c0a94c - transport error Copy code
2023-07-13T16:02:56.418779Z ERROR ThreadId(01) pact_ffi::plugins: Mock server is already startedWesley Newcomb
07/13/2023, 7:33 PMFor context, basically if you have multiple (*message.SynchronousPact).AddSynchronousMessage() calls within the same go test, e.g. func TestConsumer(t *testing.T){…} you will get the above errors.
m
Matt (pactflow.io / pact-js / pact-go)
07/13/2023, 9:45 PM
Perhaps we need to handle that situation better. Could you please raise an issue? This being said do you really need them in the same test? They will be tested separately on the provider aide
w
Wesley Newcomb
07/17/2023, 1:22 PMYes will raise an issue for this. Also yes the separating the calls in to multiple tests works, however, for my use case it would be ideal to call AddSynchronousMessage() twice within the same test to the same *message.SynchronousPact.
Wesley Newcomb
07/17/2023, 2:50 PM