Merge branch 'release/0.2.19' into develop
Fixing cypher tests #9
Switching ok for equal, when a comparison makes sense.
Merge pull request #53 from wfreeman/fixcyphertests

“Fixing cypher tests #52”

Thanks @wfreeman!
Switch to using expect.js instead of assert.

Less easy to make test errors like `assert.ok typeof foo, 'bar'`, and also
more convenience functions.
Finally shed light on random test failure.

It's a Neo4j bug -- database transaction error that seems to be random.

But at least we're properly logging that error now. Always fall back to just
throwing the response object! util.adjustError() will handle it just fine.
Remove profiling script; not needed anymore.

It was created when we were making the change from getters/setters on every
created Node/etc. instance to getters/setters on the prototypes only.

Now that that's stabilized, this simple profile isn't giving us any new or
useful information.

It'd still be nice to have some profiling at some point, but this is not it.
Switch test infrastructure to use Mocha!

Much nicer and more robust than the old manual way. =)
Merge branch 'feature/improve-tests' into develop
Document official support of Neo4j 1.7 and 1.8.
Properly relay undocumented Neo4j error responses.

E.g. a blank 500 response when deleting a relationship.
Aha! Support another undocumented Neo4j error.

Neo4j can throw an exception sometimes (e.g. NullPointerException), and the
error response in those cases don't include a message, but *do* include the
exception name and stack trace; transforming to a friendly error message.
Readme: add link to Google Group.
Readme: add link to changelog as well.
Readme: update Neo4j installation instructions.

To use Neo4j 1.8.2, and to symlink and gitignore it.
Simplify build; precompile to JS on publish now.

Fixes #35 also (installing on Heroku with Node 0.10).

I had originally considered this and went with compile-on-install so that
the CoffeeScript and Streamline compiler dependencies could be treated like
other dependencies -- use the best matching version at installation time
instead of effectively "freezing" those dependencies by compiling at publish
time -- but it seems this does simplify things. One less moving part at
deploy time for users. I can dig that.

Thanks @flipside for the nudge!
Bump version to 0.2.20, update changelog, publish.
Merge branch 'release/0.2.20'