3 ms·
1. Mock dependency 2. Throw exceptions Don't tell me "No amount of testing" just because you aren't responsible for your own dependencies.
by vsareto 6y ago
1. Mock dependency
2. Throw exceptions
Don't tell me "No amount of testing" just because you aren't responsible for your own dependencies.
- mschuster91 6y agoYou can't mock it, that is the entire point. Simply loading the shared library of the SDK will execute the broken code.
- vsareto 6y agoSo an app (which you control), is told to load a shared library, and there's no way to handle that? Even by delaying the loading to only when it'll be used?
- mschuster91 6y agoIt's not "is told", it is "it is writen in the binary itself that the kernel/libc runtime should load the shared library".
- saagarjha 6y agoTo be fair, you don't have to do it that way. (Library loading is done by dyld, FWIW.)
- adamparsons 6y ago90% of people in this thread think “native code” is a react plugin