Dear community, I am writing my first Pact test, ...
# pact-js
c
Dear community, I am writing my first Pact test, for the consumer side. I am using the experimental V4 version. It seems everything is working untill the response is sent back from the server. It might be caused by thread has not entered Tokio, and therefore the server is shut down. I have no experience with Rust or Tokio, so I am not sure how this error is caused by my setup or my test. @Matt (pactflow.io / pact-js / pact-go) I've found a post by you dated 2022-09-06 that shows a similar error. So I am hoping you know what might be wrong. And more importantly, how to fix it? Thanks for your time, Carmen
y
Can you potentially produce a reproducible example and provide a bit more detail on your setup (os/node version etc) as there probably isn’t enough in there to help with at the moment. Thanks for reaching out though!
☝️ 1
c
I would love to offer a reproducible example. But since I have no idea what is going on, I have no clue how to reproduce it. I did manage to write functional contract tests for the different workshops offered on the Pact website, in case that is useful to know. OS: Windows 11, version 22H2 for x64 Node: 20.9.0 Axios: 1.6.2 Typescript 4.9.5 What else would you like to know?
m
Does your test that produces that error above reliably reproduce the problem? If so, pare back the test (by removing all of your code/IP until the problem goes away - that will either reveal the problem, or give us a repro we can use to debug)
c
Yes the issue is reproduced by my test reliably. I will follow your approach, thanks for the suggestion! πŸ™‚
thankyou 1
Thank you for your suggestion @Matt (pactflow.io / pact-js / pact-go) πŸ™‚ I started making changes to my code, as you suggested, and somehow the issue disappeared. I do not know how it happened, but I am glad that it did πŸ™‚
πŸŽ‰ 1
m
haha well, good to hear!
βœ… 1