I tend to write integration and unit tests for each feature to drive the implementation of user story from the outside in (i.e. BDD). Next, the very goal of integration tests is exercising the expected assumptions of these connected components. The very goal of the unit test is exercising the expected assumptions of the individual component. If either the integration and/or unit test is insufficient for the components or component under test, then it's definitely possible to receive errors when the code is exercised in a context in which it hasn't been tested. In summary, one shouldn't expect an insufficient integration or unit test to catch errors when the code is being exercised outside the context for which has been tested.

I enjoy working with React being that the JSX you write today is much closer to HTML IMO. Also, I found much higher levels of productivity with colocating my components with their associated JSX and styles. Finally, I like the fact that React has its foot on the paddle in regards to using ES6+ and has a clear answer to building native application with the use of React Native.

@mgiambanco My go to application is Transmit which can be found at the following location: https://panic.com/transmit/