1,114 karma · joined March 12, 2013
www.cenizal.com
Discussion is good (because ideas are surfaced and knowledge is shared) but long discussions are bad (because action is delayed). Action is good because that's how you learn things. By adopting an "Let's try it" attitude, you can move from discussion to action more quickly.
Here's an example of how we used react-test-kit to test a SearchBox component: https://github.com/smaato/ui-framework/blob/develop/src/fram...
Here's the interactive component example: http://smaato.github.io/ui-framework/#/searchbox
This means treating the component as an opaque function with inputs (props) and outputs (the rendered result). Your tests just need to that verify that different prop values result in the DOM changes or callbacks that you expect.
I have such a feeling of empowerment and productivity when I'm working with well-designed tools and APIs, with interfaces that fit into my mind the way the handle of a hammer fits perfectly into my hand.
Instead of saying "no assholes", just list the behaviors that define assholes and just say "don't do these things."
The problem with the original question is that it masks your true question and makes it really difficult to understand what the discussion is about. If someone is used to answering questions succinctly, directly, and usefully (which are valuable traits in a productive engineering environment) then it's really difficult to formulate a clear answer on the spot, regardless of your depth of knowledge. The best response is probably the question, "Exactly which part are you interested in, and in relation to what kinds of problems?"
UI Framework built with React and SCSS. The components are nicely modularized, have unit tests, and we put a lot of emphasis on code readability, clear names for things, a scalable folder structure, and intuitive interfaces.