l-mock | The easiest way to mock api data in local project | REST library

I'm mocking negative responses with PayPal API in order to get the responses and handle correctly a critical part of payment when the client has approved the payment via onApprove method.

I'm using GuzzleHttp + Laravel to capture the approval from the client. I get the COMPLETED status within the complete object. So the request is working properly.

Im doing the paypal tutorial server side integration. With PHP. I'm having a problem.

I want to test funding failures,the last part https://developer.paypal.com/docs/business/checkout/server-side-api-calls/handle-funding-failures/

I think I add the mock header in the right place but is doing nothing it keeps saying Transaction completed . Whats the proper way to put it? Paypal says:

Small question regarding how to "force" or "mock" the response of a Webclient http call during unit test phase please.

I have a very straightforward method which does:

I am unable to mock react-router-dom, I am seeing an error because the mock isn't being instansiated. Where am I going wrong?:

I have a monorepo structured as such, apps are created with CRA and use craco at the root:

I have a test that needs to use navigator.mediaDevices but I cannot get any mocks to work correctly.

I am using create-react-app.

Here is my test:

I'm trying to setup my mobile app with amplify, after the first time i run amplify configuration it prompt me that I have missing plugins.

I am testing a class that needs a mock in the constructor, so I usually do this:

I am having problems using Jest manual mocks (the one in a parallel __mocks__ directory) in my project.

I think I understand how to use it and it actually works fine if I remove a single line in a file specified in the Jest setupFiles array.

In that file a global helper is installed (into global.createComp) that uses the vuex store.

This is a vue + vuex project but even running the stripped down spec using only jest gives unexpected results.

Can somebody look at my minimal reproducible example repo at https://github.com/thenoseman/jest-manual-mock-not-working, do a npm i and npm run test:unit and help me understand why the mock is not active?

You can find the line that need to be commented out in test/unit/support/helpers.js. Also the README shows a screenshot and further explains what the problem looks like.

I'm trying to understand when I can just import a mock vs when I need to import the mock and still use jest.mock in the test file. I'm looking at the manual-mocks example from Jest's Github.

One Step Module Mocking

In the Lodash test, Lodash is mocked in the __mocks__ directory using createMockFromModule, exported, and simply imported using the standard module import and used directly in the test (no additional mocking).

Two Step Mocking

In that same project, the User model is exported and there is a separate User mock file. But in the User mocked test, the User is imported but there is an additional step using jest.mock('../models/user');

My Question/Confusion

Why would the Lodash test not require the additional jest.mock in the test file, or why does the User test require it? In the project, it seems like I can test both actual and mocked User implementation, but Lodash will only use the mocked implementation, even though both are created/exported using createMockFromModule in the __mocks__ directories.