Skip to content

Tag: unit-testing

Mock AWS SES using jest in typeorm

Need to test AWS SES using jest unit testing But showing different errors, also tried solutions in another stackoverflow question The actual code to be tested is : the test file is : Its giving error message as: Answer Actually this mock works, the reason behind the error is that , i didn’t mocked the AWS.Credentials.

Vitest mock modules function in only one test and use the actual function in others

The following is an abstraction of my problem and thus does not make too much sense: Given I have a simple utility callMethodIf that’s returning the return of another imported method (blackbox). ~~/utils/call-method-if.js: ~~/utils/blackbox.js: How would I run one test case which calls the actual implementation of blackbox() and another one where I mock the return value of blackbox()? I

Can’t mock the navigator.language

I’m currently adding unit test for some of shard utils functions. I’m kinda new to unit testing. Currently having hard time to mock some global object. Is there any way to mock/update value of navigator.language? It is always returning en-US. I tried the Object.defineProperty and different jest mock objects. Didn’t work. The thing is, if I console.log(navigator.language) in the test,

Module not found even though it is imported

When I run this test: I get this error: Reissue.tsx does import ReissueService. Do I need to mock this and if so how do I do that? In Reissue my import is: and I’m exporting: In ReissueService I export: Answer I changed import { ReissueService } from ‘src/services/ReissueService/ReissueService’; to import { ReissueService } from ‘../../services/ReissueService/ReissueService’;

How to mock instance methods of a class mocked with jest.mock?

How can the instance methods be mocked for a class that is being mocked with jest.mock? For example, a class Logger is mocked: Answer Automatic Mocking Calling jest.mock automatically mocks all the exports from the module being mocked unless a manual mock is specified using the __mocks__ directory. So, this line jest.mock(“./Logger”) has automatically replaced the Logger constructor and all

Debugging jest mocks

I’ve got a library that’s giving me some trouble in my jest tests. This library is included throughout my project, and it has an annoyingFunction that has a console.error in it. So, whenever I run a test, I naturally get unwanted console.error messages all over the place. I don’t want to mock out the whole library, just the annoyingFunction, so

TypeError: Cannot read property ‘navigator’ of undefined

My unit test case started failing when I started running the unit test in mocha from karma, Earlier we were using karma and –browser to run the test case but it was running fine, Package.json test file – It fails for navigator here, TypeError: Cannot read property ‘navigator’ of undefined ReferenceError: navigator is not defined Answer Accessing global.window.navigator is an