Jake Howard

Yes, please! I'm surprised it's so simple, I was expecting much worse!

The idea of this library is to use the 'Shallow' render feature of `enzyme`. In an ideal world, everything would render accurate children, and we wouldnt have any issue like...

@dan-manges that looks like great work. Looking through your code i'm not seeing any massively breaking changes, but I may be wrong. I'm currently in the process of doing a...

@talarari no, #120 is a complete rewrite. Rather than using complete mocks as the current version of `react-native-mock` and `react-native-mock-renderer` do. #120 uses the direct `react-native` code when rendering, in...

Short term that's exactly the ideal fix for this! Long term i plan to do a large refactor job on the project in the coming weeks, i'll add this to...

This is normal, and intended. Only versions distributed through npm have the built source. Rather than that babel command, which doesnt look that great, you can do: ```bash cd node_modules/react-native-mock...

There are almost certainly other things the build does rather than just convert to ES5 (I forget off the top of my head). So whilst this isnt advised, it does...

@dannycochran Currently, it can't. The `rewrite` branch is still _Work in Progress_. Hopefully there will be a beta to test soon

I've been working with unit testing a load of custom components, and I've found the best thing to do is render them with shallow. Then you can test prop calls...

This is likely because the mock for `XMLHttpRequest` never returns anything, which is fine. Generally you shouldnt actually need to mock things this far down, and should never actually call...