(#3179) - Add test
(#3179) - Ensure documents are reported as deleted
(#136) - Test against 1 node CouchDB cluster

When spinning up a CouchDB cluster to test against, just use one node.
This ensures that we're still testing against the clustered interface but
removes any problems with eventual consistency between nodes in the cluster.

I'd suggest reverting this once we have all the tests passing but, for now,
this is useful to remove much of the "noise" in the failures.
(#136) - Fix "changes since old style" test against CouchDB 2.0

CouchDB 2.0 does not use numeric sequence numbers so we cannot predict the
value that will be returned. Change the test to use the sequence number
returned by the database rather than assuming it will be a specific number.
(#3229) - just the fixes for nodewebkit
(#3229) - WIP - test nodewebkit with selenium