Preparing for CI on Travis

@davidchang This changes how the tests are run. I now run them through browserify, this has a couple of advantages: 

1. We use the dependencies from the package.json file, not the bower dependencies.
2. We can run reactify and transform jsx and es6 (I changed the *spec files to use jsx and lambdas)
3. It should be easier to setup ci on travis (https://travis-ci.org/), so we can run the tests on each push.

I wanted to setup a travis build, but I couldn't because I'm not the owner of the repository. So would you like to play with that? Alternatively you can setup a github organization which has me as a member (but I think that requires you to move the repo into that org). 


Good idea. I went with destruction instead though.  

```javascript
var {fname, lname} = this.props;
return <div onClick={this.handleClick}>Hello {fname} {lname}</div>;
```