Only test the public API
nhunzaker opened this issue · comments
I want to start experimenting with tools to reduce the build size, like (buble or Google Closure Compiler), and improve execution time (like prepack).
The problem is that, for the sake of test coverage, we directly test private APIs quite a bit. Frankly, I'm really not sure if this is a good or bad thing. However it's definitely a bad thing for tools that change code during the build process.
Ideally, our test suite always runs against the code that hits production.
- action
- compare-tree
- domain
- effect
- history
- key-path
- microcosm
- middleware
- utils