Discussion: Framework "Recommendations"

I think it'd be good to have a discussion to build a doc for our "recommendation" for testing framework wrapped components (redux). This comes up a lot. The real answer is that it's not this libraries scope to handle framework specifics. But it comes up a lot so we should have a discussion about how to handle it.

Personally I think there are a couple good options here:
- A seperate library for making library specific connections easier. e.g., `enzyme-redux`, `enzyme-coflux`, `enzyme-mobx`.
- This would provide helper utilities to make it simple (maybe there are already libraries for this?).
- Docs on our recommendations

As far as docs go. It seems like the easiest recommendation that keeps coming up is to suggest exporting the non-framework-wrapped version of a component.

``` js
export class PrivateComp { }

export const Component = frameworkWrapper(PrivateComponent, ...);
// or
export default frameworkWrapper(PrivateComponent, ...);
```

Looking to hear from the community on how they handle testing framework wrapped components. Extra curious in MobX users as it's got a lot of attention lately.

The issue names no files or tests; start by reviewing the 28-comment discussion and the examples for Redux- and MobX-wrapped components. Done would require an agreed recommendation and documentation plan, but the issue does not specify a documentation location or final guidance.

Written by the indexing model from the issue text.