:bug: BugHelp WantedPinned
Repository-Metriken
- Stars
- (45.361 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 11T 22h) (11 gemergte PRs in 30 T)
Beschreibung
🐛 Bug Report :
let's say we have a module named: Autosuggest. and we want to mock it.
import AutoSuggest from './AutoSuggest' // the filename is Autosuggest.js (lower s)
jest.mock('./AutoSuggest', () => ({get : jest.fn(() => 1000)}));
if we import it with camel cases, like: AutoSuggest, it doesn't throw any error. it just let us to do it, and it allow us to mock it. but the mocking actually doesn't work this way.
Why it's important to fix : After one day of debugging about why mocking doesn't work, i fixed it with fixing the cases. so the problem is : it increases debug time.
Expected bahaviur :
jest.mock('./AutoSuggest') should throw an error when there is a module called ./Autosuggest, but there isn't any module called ./AutoSuggest.