Hey @Matt (pactflow.io / pact-js / pact-go) what am I doing wrong here that I'm getting the missing requests errors? I've tried the fixes mentioned in previous posts and no luck 😞 Below are the images for the service making the call, the pact config file, the pact test I'm running, and the error. This is an angular app running on Mac using the jest-pact package.

Not used Angular before, but that looking at the logs, your mock server is started up and listening on the correct port you are expecting to send your request to I thought jest-pact uses a random port now, and you passes the mock server base url that you inject into your api client code. looking at that, mock server log though, it's not getting a request, so is that subscribe method actually calling that line in your hello world program to make the request

So I threw a console log in the service and it does look like the subscribe is calling the service. Here are some more logs. Hoping they look familiar and you know more about how to move forward from here 🙏

looks like there are no interactions loaded in the mock provider

yeah, I'll push the code up now and share link for GH one sec

Can access it, can't install pact, using v3, as it pins peer deps to v24-v26 or jest https://github.com/pact-foundation/jest-pact/blob/a7b39380473e10b6939c89cbf8bd701f85bd513c/package.json#L61

Yeah that works. I ran into that error as well and it was a lot of changing versions around so they would play nice together lol sorry about that

it's okay buddy. quick question, does your unit test work

The unit test does pass but its a false positive. You can change the expected value to anything and it will still be a success. This is a separate issue I'm looking into as I didn't think it was related/affected the pact test.

have you seen this? https://github.com/omermorad/nestjs-pact

So I don't actually need pact for nestJS 😞 I'm not sure what the overlap is but my company needs pact testing on the Frontend - Angular app inside an nx monorepo that uses Jest and Cypress. We don't have any nestJS apps it was more me thinking I needed an API to provide data to get the pact tests to work.

correct, but the pact mock service, will check when it receives the request, was it the type of request you explicitly stated in your test, if so, it will return the prescribed data, for your client code to unmarshall, and for you to test the response of your clients code result (not that of the providing api)

Yup that's exactly how I understood it. So there isn't a need for a providing api which would be the localhost:3333 endpoint you're seeing in the unit test. Is there some overlap between the unit test you ran and the pact test that is run with the "npm run test:pact" command?

so your unit test, effectively is a component integration test, with a mock of the provider. Pact is used within your unit test framework. You wouldn't use Pact in all your test cases, but a select few

I'm not quite sure I follow 😓 The unit test that's currently in there can be disregarded no? We can just delete it if it's causing any confusion. I had only created it thinking it was needed for the Pact test.

Yeah I don't think it's needed. this shows it quite nicely https://github.com/pact-foundation/jest-pact#usage I just started there, to ensure that we were mocking the call in the unit test correctly to whichever endpoint our api client service (in this case HelloWorldService) The non pact test doesn't look right as I can expect the result to be anything, and it passes. (as you said)

Oh I see what you're saying about ensuring we're mocking the call correctly. Yeah I had just thrown a console log in there to make sure the .subscribe() method actually called the service which it did. I'm also assuming the get request in the helloworldservice works correctly as well since if I run the api locally it does indeed return data when I call that service

I don't think you are mocking things out correctly in angular

I push up the new changes to the GH that include what you mentioned. It looks like I'm still getting the same error 😞

message has been deleted

Omg dude you're the best!! Curious if this was an issue with the Url I was stubbing or the versioning? I had moved over to the the beta version due to an error in the console saying v2 wasn't supported for x thing. I can't quite remember off the top of my head.

the only reason you can't use v3 at the moment, is it fixed jest deps to v26 or lower, and if I drop your jest dep, I need to tweak your tests

Dude awesome thank you so much! I'm going to start writing the initial article now that gets angular/jest working with Pact. From there I'll move onto Cypress and then finally tie it all up into a monorepo env. Can't thank you enough for getting me over this initial hill ❤️

Sounds awesome matey, and my pleasure my friend. I have a cypress example with mocks provided by msw and pacts generated with our adapter. Quick start guide is here (hot off the press) https://docs.pactflow.io/docs/bi-directional-contract-testing/tools/msw/ We also have a cypress adapter https://github.com/pactflow/pact-cypress-adapter And an example repo that uses it. https://docs.pactflow.io/docs/examples/bi-directional/consumer/cypress/ Would love to get an angular recipe on the pact docs site at some point https://docs.pact.io/recipes and give this page some general love